Skip to contentSkip to conversation

Compiling Apache

Buildroot Michael Burghart 9 participants 25 messages Mar 22, 2011 – Oct 28, 2011 2 messages not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to Michael Burghart

Hi,

Quoted 49 lines · Michael Burghart

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am new to this list. Nevertheless I am really happy about the buildroot tool. Great Work!!

Unfortunately I ran into trouble which I don't understand. I produced a working toolchain and managed to post-install things. Now I need to add a "httpd-2.3.8" package. But it fails to build with the following error:

make[4]: Entering directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre' ./dftables /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c make[4]: ./dftables: Kommando nicht gefunden
make[4]: *** [/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c] Fehler 127
make[4]: Leaving directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre' make[3]: *** [all-recursive] Fehler 1
make[3]: Leaving directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre' make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib' make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17'
make: *** [/LFS/buildroot-2011.02/output/build/httpd-2.2.17/.stamp_built] Fehler 2

("Fehler" =>> "Error" :)))

This is my mk file for httpd

HTTPD_VERSION=2.3.8
HTTPD_SOURCE=httpd-${HTTPD_VERSION}.tar.gz HTTPD_SITE=http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/httpd/ HTTPD_INSTALL_TARGET=YES
HTTPD_AUTORECONF=YES
HTTPD_LIBTOOL_PATCH=YES
HTTPD_AUTORECONF=YES
HTTPD_CONF_OPT= --enable-ldap=no --enable-ssl --with-pcre=/usr
- --with-ssl=/usr ap_cv_void_ptr_lt_long=no
HTTPD_DEPENDENCIES=pcre

Quoted 2 lines

Does anybody know about this problem? What am I doing wrong?

dftables is a tool which should be compiled for your host as it's used to generate pcre_chartables.c . In the present case, it seems dftables can't be executed so either it's compiled for your target (but in that cas you would get a log saying it has a wrong binary format) or it's not present at all.

Moreover you have HTTPD_VERSION=2.3.8 in your .mk and the log says httpd-2.2.17 so there may be something wrong here.

apache is not easy to cross compile, you can check the recipes in OpenEmbedded to see what we do there :
http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apache2/apache2_2.2.17.bb
http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/libpcre/libpcre_8.10.bb
http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apr/apr_1.4.2.bb
http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apr/apr-util_1.3.10.bb

Eric

#4 lore raw
In reply to a message not in the archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Am 22.03.2011 16:56, schrieb Eric BENARD:

Quoted 3 lines

Hi,

please keep list in copy when answering,

sorry. Yes, I will.

Quoted 9 lines
Quoted 9 lines

Am 22.03.2011 15:59, schrieb Eric BENARD:

Quoted 6 lines

http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apache2/apache2_2.2.17.bb

http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/libpcre/libpcre_8.10.bb

http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apr/apr_1.4.2.bb

Quoted 8 lines
Quoted 7 lines
Quoted 2 lines

http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apr/apr-util_1.3.10.bb

thanks for your info. Seems pretty weird and more complex than I thought. But how do you integrate those rules into buildroot? I only saw the "standard" autoconf and cmake Makefiles.in the documentation..

well for that part you will need to ask on the mailing list.

does any on this list know how to implement Eric's knowledge on Apache into an .mk file? Or does anybody already have a .mk file to share? Or am I the only guy who wants to cross compile an Apache? :)

- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNiMk2AAoJEEMkp/gkis19u+EH/3MuAQCNXG2Dz6+5OnBja5+M BDx/OuQjfkSKyNN019PDf+ua/2oWe4OZJ7MiI/VaR/i5UFNCxoKAT+aRMpFR2PZf Pp3BmMBfpHpJLZRHoOjWsgr2pkU4mugD17aV/nRHdPXVt1XavLbue4pUwvXb/9t8 EA9tryKHJ2L/u0ax1hLJZB5jAku2u1LaO7sY6kOGrKOVGi678QnMpQ7t610RCsiX R/vHnSzl3Uy+aqWWbpWK508snYyd/w9tnoEU8A6LJZNGoDFswbxPzS/XciRdwltG HteI9ut+R5UmiAJmdmJ4iV+D+0EQa6839celXJ4YPahyNSMtjaxo653huwgDCE8= =vwSS
-----END PGP SIGNATURE-----

#5 lore raw
In reply to a message not in the archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Am 22.03.2011 16:56, schrieb Eric BENARD:

Quoted 6 lines
Quoted 4 lines

thanks for your info. Seems pretty weird and more complex than I thought. But how do you integrate those rules into buildroot? I only saw the "standard" autoconf and cmake Makefiles.in the documentation..

well for that part you will need to ask on the mailing list.

what I do not understand: I get the following error:

make[4]: Entering directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre' ./dftables /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c make[4]: ./dftables: Kommando nicht gefunden

So I tried it manually and did a cd into the directory:
cd /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/

then I invoked the dftables command manually:
./dftables /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c

got "File not found":
- -bash: ./dftables: Datei oder Verzeichnis nicht gefunden

Did a ls on that file and it exists! So why did it produce an "File not foound" error
mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> ls
- -l ./dftables
- -rwxr-xr-x 1 mb users 8015 22. M?r 15:18 ./dftables

How can that be? I am really puzzled now...

Quoted 3 lines

Regard,
Eric

- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNiPl7AAoJEEMkp/gkis19EbcIAKi6tbjQAzNbf5OLqNh3Js2d 9DSDhnCiGG1DfYkxTKDPEkdiPDXjxQMX4DtKivlnKs8n0MqW84jkbFV1yauFS8x4 zkQ/zWTCRSrToMmCzhnMOpxPibB318hWseAEGECR7XrjdoRKSZiZQKGKzkVJECEM c2hzJOt0RyxTOqs1ZdmUmxZ/ui6O5w5bjb7tqPFh44GNH5JDigG7ghkJrtIuojEE tpL3MI7ZEi2LRQ8CGRvRejuxqiGL+U1gYJqpQ/dO1CmwbUMX7bQNzanN0OB+gqII YO1qbdG0kaONxScDn96qe2WVH98C7dfK4UOw+K2ordjmR98aunrlv7pmCvGAx4A= =kA5n
-----END PGP SIGNATURE-----

#26 lore raw
In reply to a message not in the archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 22.03.2011 16:56, schrieb Eric BENARD:

Quoted 5 lines
Quoted 4 lines

thanks for your info. Seems pretty weird and more complex than I thought. But how do you integrate those rules into buildroot? I only saw the "standard" autoconf and cmake Makefiles.in the documentation..

well for that part you will need to ask on the mailing list.

I forgot. I did an strace on that non existing file:

mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> strace ./dftables
execve("./dftables", ["./dftables"], [/* 73 vars */]) = -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f8fa10dc000
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or di"..., 40strace: exec: No such file or directory
) = 40

close(3)                                = 0
munmap(0x7f8fa10dc000, 4096)            = 0
exit_group(1)                           = ?

Does anybody understand whats happening here?!

- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNiPn9AAoJEEMkp/gkis191/EH/j7MqbQNNrHWim7ZmKfaEHFm hR0nBTurG/9xt19Tjg0zW9BdPnWAgIjP2ao+p2VRoaIwPGqj3rLdfLzHgfsg959K kKYoYprcABEGDDPLMiVDK7PeXCyHbLH6v6oWFf6l6tyStRVvhIlDAUPro5bYAeQD oBnMiq5u/PXRX5SI3P7/d3qnU+2N8fBWx8XM9Qjn+LRWh8RIxyYtMwvYNg3q7bb7 3zSbVxBtxgNHogHCrtt9bl6+eosXAiHnwaA0EH+pimEkMJohchb8Gntq3/2Gm1TF 92a0dEBCLIjpM7WwyCJ1VmYrVyKxs/hGDw2+WHzJWgr49DTdKygfT/FdVAFm3+Q= =zzIK
-----END PGP SIGNATURE-----

#6 lore raw
In reply to Michael Burghart

Hi Michael,

Quoted 19 lines · Michael Burghart

what I do not understand: I get the following error:

make[4]: Entering directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre' ./dftables /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c make[4]: ./dftables: Kommando nicht gefunden

So I tried it manually and did a cd into the directory:
cd /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/

then I invoked the dftables command manually:
./dftables /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c

got "File not found":
- -bash: ./dftables: Datei oder Verzeichnis nicht gefunden

Quoted 8 lines

Did a ls on that file and it exists! So why did it produce an "File not foound" error
mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> ls
- -l ./dftables
- -rwxr-xr-x 1 mb users 8015 22. M?r 15:18 ./dftables

How can that be? I am really puzzled now...

Quoting the execve(2) man page:

ENOENT The file filename or a script or ELF interpreter does not exist, or a
shared library needed for file or interpreter cannot be found.

This means that the format of the executable is wrong. What is the output of 'file dftables'?

baruch

Signature · 3 lines
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
#7 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Baruch,

Am 22.03.2011 20:55, schrieb Baruch Siach:

Quoted 7 lines

Quoting the execve(2) man page:

ENOENT The file filename or a script or ELF interpreter does not exist, or a
shared library needed for file or interpreter cannot be found.

This means that the format of the executable is wrong. What is the output of 'file dftables'?

./dftables: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped

But what is wrong?!

- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNiP/GAAoJEEMkp/gkis19b1kH/R0dw7EVzJzeohj+5sv2MA09 B1ustR+KqY3+gnrPjCZdfWyv3sl9I6RJVcNLB4Eb5g0XUnNMiZ9bgvY/eVbQLvrW yYqFgIXS41z+GUmuSsalClol/mXKWtNG1EekBBUdakLbEzjNX9xGD+0endcGiWgI AvzrWps1guUpRo+OMol1P6R8OOEBeAvrS2kfC+pnfOaXfLybNnnqQOHIqSmDEvVT fB+06226wTQXlv94c9jfiwZ4GWR182WvtBqOu/5+5Lep5yzIitKZdlxYbcDJxu7z 5aiW8ec/spo4WdhyIRXf6U7nz7/Sd4tvHWLDrQFV5mcJJk0tYc0A0ddeh/vX2Lo= =9Tzl
-----END PGP SIGNATURE-----

#8 lore raw

Hi Michael,

Quoted 11 lines · Michael Burghart

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Baruch,

Am 22.03.2011 20:55, schrieb Baruch Siach:

Quoted 5 lines

Quoting the execve(2) man page:

ENOENT The file filename or a script or ELF interpreter does not exist, or a
shared library needed for file or interpreter cannot be found.

Quoted 7 lines
Quoted 2 lines

This means that the format of the executable is wrong. What is the output of 'file dftables'?

./dftables: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped

But what is wrong?!

Another possibility is that one of the shared libraries that this executable depends on is missing. What is the output of 'ldd dftables'?

baruch

Signature · 3 lines
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
#9 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Baruch,

Am 22.03.2011 21:03, schrieb Baruch Siach:

Quoted 2 lines

Another possibility is that one of the shared libraries that this executable depends on is missing. What is the output of 'ldd dftables'?

./dftables: not an ELF file.

puzzles me even more...

Thanks for your help btw!!

- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNiQS/AAoJEEMkp/gkis19gBkH/3RVxIkzovdor4RZsdtbJSKI nabV/7naWobPIS+N5Egj6J8kHCWPmPFFQZVL5A8m9LUpNhYuqeMmFLri7Y97QQus vMcgjQ+XbN1VIgUkq5GtOXBey7yAxFlyWNCkqUZt9TuWdJnuVgfwUdwCcxrOzAzs f9bGZtMJ2dHlNcTWirE4THpDKDns8Y067QhyqLWX4hsoUG2+BXotwpoc1kOGWIIQ oyeiYOIrz9ZzJDohUKMy9Q6RB5j+BSdw/h771oCBM0vSNJmRF88L7L6X/RMDMV/6 3/rZhCS1Up9dvOvhvuMWI3WWOKZ1bY2vrpWXLwKiKQ/UwEIhGBkcOtCOA19NIic= =BMrf
-----END PGP SIGNATURE-----

#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am new to this list. Nevertheless I am really happy about the buildroot tool. Great Work!!

Unfortunately I ran into trouble which I don't understand. I produced a working toolchain and managed to post-install things. Now I need to add a "httpd-2.3.8" package. But it fails to build with the following error:

make[4]: Entering directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre' ./dftables /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c make[4]: ./dftables: Kommando nicht gefunden
make[4]: *** [/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/chartables.c] Fehler 127
make[4]: Leaving directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre' make[3]: *** [all-recursive] Fehler 1
make[3]: Leaving directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre' make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib' make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/LFS/buildroot-2011.02/output/build/httpd-2.2.17'
make: *** [/LFS/buildroot-2011.02/output/build/httpd-2.2.17/.stamp_built] Fehler 2

("Fehler" =>> "Error" :)))

This is my mk file for httpd

HTTPD_VERSION=2.3.8
HTTPD_SOURCE=httpd-${HTTPD_VERSION}.tar.gz HTTPD_SITE=http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/httpd/ HTTPD_INSTALL_TARGET=YES
HTTPD_AUTORECONF=YES
HTTPD_LIBTOOL_PATCH=YES
HTTPD_AUTORECONF=YES
HTTPD_CONF_OPT= --enable-ldap=no --enable-ssl --with-pcre=/usr
- --with-ssl=/usr ap_cv_void_ptr_lt_long=no
HTTPD_DEPENDENCIES=pcre

Does anybody know about this problem? What am I doing wrong?

- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNiRcPAAoJEEMkp/gkis19xZYIAKxeVAiSRLwKRLo5ZLX+qYH4 XlypMma4FKHMAJvU59gm1OkvwRPEDkErqzdLjV/DApNq9Xlvo09YMtFiEogPd0DA gOsZnJGptmzMf8dgdKF89fTf0Jwh7ENfVOqwGLWQvWuH69toE/HjTeQ14Uracn4D 5s2wFXRgt/yC4AgI7LZVEYBl+6YmHnCtFe3p30AflOwMrfOHfKsBgbXBxSG5I7sV xVZMGkB8k6hvSiXFII3tXZZMPd5E7VjmJIGVoDFPOmkmom136ZrwpF8Eerh6I4Ux iMdXlIR4oY2VtQu4lLOHifHkXBB73BM218TsHalULOE2FFABFBEzsT1rnyCv6m0= =k8Vt
-----END PGP SIGNATURE-----

#10 lore raw
In reply to Michael Burghart

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi and good morning...

Am 22.03.2011 21:21, schrieb Michael Burghart:

Quoted 4 lines

Hi Baruch,

Am 22.03.2011 21:03, schrieb Baruch Siach:

Quoted 8 lines
Quoted 2 lines

Another possibility is that one of the shared libraries that this executable depends on is missing. What is the output of 'ldd dftables'?

./dftables: not an ELF file.

puzzles me even more...

Thanks for your help btw!!

mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> /LFS/buildroot-2011.02/output/host/usr/bin/file dftables
dftables: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), not stripped

mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> /LFS/buildroot-2011.02/output/host/usr/bin/ldd dftables
dftables: not an ELF file.

I do not understand. file tells me the info about the file and ldd tells me its not an ELF file whereas file says "ELF 32 bit" (which is correct).

What did I do wrong?
- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNiY88AAoJEEMkp/gkis19XEIH/jpFf6bBph1VeNAEatIWXkcQ yjPV9O8zX3eE5+Y7MVTC8wAYd0XAGMhfBPBSpx+ijl49Osc6u0lCHneZPA+6YiXg hqZK25ua+EB/1fxYioWFBDBNxY/j8Vg4ECcYx4hGEMR4PXoCyi4Lq9NftH4DGcTB iRoRBszXzUynuQQDov0jp9KE7S4Z8b28tVBYaPTsF2xrSY/1Lic52nu9GarYHgjx ys7n6Kk0heCQQhAL3/38pbNG57SW7VWNxtq6HgKrs+8oG/27Qvtm8bK3+G8uRGVP 8NqrZhFGrcRsPe5WXYVi87ZEnl19esE3cD/sZ1Cpb7S+ImE0rw9kyoJYPPzCuyg= =PTKl
-----END PGP SIGNATURE-----

#11 lore raw

Hi Michael,

Quoted 24 lines · Michael Burghart

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi and good morning...

Am 22.03.2011 21:21, schrieb Michael Burghart:

Quoted 4 lines

Hi Baruch,

Am 22.03.2011 21:03, schrieb Baruch Siach:

Quoted 8 lines
Quoted 2 lines

Another possibility is that one of the shared libraries that this executable depends on is missing. What is the output of 'ldd dftables'?

./dftables: not an ELF file.

puzzles me even more...

Thanks for your help btw!!

mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> /LFS/buildroot-2011.02/output/host/usr/bin/file dftables
dftables: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), not stripped

Quoted 8 lines

mb at einstein:/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre> /LFS/buildroot-2011.02/output/host/usr/bin/ldd dftables
dftables: not an ELF file.

I do not understand. file tells me the info about the file and ldd tells me its not an ELF file whereas file says "ELF 32 bit" (which is correct).

What did I do wrong?

Do you have 32bit libraries on your host machine?

What is the output of 'sh -x /usr/bin/ldd dftables'?

baruch

Signature · 3 lines
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
#12 lore raw

[Buildroot] proc not mouning

Hi,

I've done something bad to my Buildroot platform, but I can't figure out what the problem is.

When the initramfs system switches over to the root filesystem on an SD Card created by Buildroot, it can't find /dev/null, and can't mount /proc.

When I login the /proc directory is not mounted, but I can manually mount it however from the command line.

My inittab contains a statement to mount proc as well as another statement to do a 'mount -a'. I verified that fstab contains an entry for proc. I know something is processing inittab because the boot scripts that inittab calls do run.

I even added an entry in inittab to 'mknod' /dev/null.

I'm really stumped by this. I even did a clean rebuild without any luck.

Output below. Appreciate any help.

thanx
/carl h.

mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address aaaa
mmcblk0: mmc0:aaaa SD02G 1.84 GiB
mmcblk0: p1
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p1): using internal journal
EXT3-fs (mmcblk0p1): recovery complete
EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode
Switching to filesystem on SD card....
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
grep: /proc/mounts: No such file or directory
grep: /proc/mounts: No such file or directory
Populating /dev using udev: /etc/init.d/S10udev: line 82: can't create /proc/sys/kernel/hotplug: nonexistent directory done
Starting portmap: done
Initializing random number generator... done.
Starting network...
ifup: interface lo already configured
ifup: interface eth0 already configured
Starting ProFTPD: warning: `proftpd' uses 32-bit capabilities (legacy support in use)
- warning: unable to determine IP address of '_none_'
- error: no valid servers configured
- Fatal: error processing configuration file '/etc/proftpd.conf'
FAILED
Starting sshd: OK

Welcome to Buildroot
(none) login:

#13 lore raw

[Buildroot] proc not mouning

Could it be something you changed in:
<package selection for the target> ------------<tick> show packages provided by busybox --------------System tools ?

This is my attempt to run a "empty but functional" build whilst trouble shooting a python "readline" issue.....dunno if it'll help to compare it.

BR2_HAVE_DOT_CONFIG=y
BR2_arm=y
BR2_arm926t=y
BR2_ARM_TYPE="ARM926T"
BR2_ARM_EABI=y
BR2_ARCH="arm"
BR2_ENDIAN="LITTLE"
BR2_GCC_TARGET_TUNE="arm926ej-s" BR2_GCC_TARGET_ARCH="armv5te" BR2_GCC_TARGET_ABI="aapcs-linux"
BR2_WGET="wget --passive-ftp -nd -t 3"
BR2_SVN="svn"
BR2_BZR="bzr"
BR2_GIT="git"
BR2_ZCAT="gzip -d -c"
BR2_BZCAT="bzcat"
BR2_TAR_OPTIONS=""
BR2_DL_DIR="$(TOPDIR)/dl"
BR2_HOST_DIR="$(BASE_DIR)/host"
BR2_PRIMARY_SITE="" BR2_BACKUP_SITE="http://sources.buildroot.net/" BR2_SOURCEFORGE_MIRROR="kent" BR2_KERNEL_MIRROR="http://www.kernel.org/pub/" BR2_GNU_MIRROR="http://ftp.gnu.org/pub/gnu" BR2_DEBIAN_MIRROR="http://ftp.debian.org"
BR2_JLEVEL=2
BR2_STRIP_strip=y
BR2_OPTIMIZE_0=y
BR2_HAVE_DEVFILES=y
BR2_TOOLCHAIN_BUILDROOT=y
BR2_KERNEL_HEADERS_VERSION=y BR2_DEFAULT_KERNEL_VERSION="2.6.38-rc5" BR2_DEFAULT_KERNEL_HEADERS="2.6.38-rc5" BR2_UCLIBC_VERSION_0_9_31=y BR2_UCLIBC_VERSION_STRING="0.9.31" BR2_UCLIBC_CONFIG="toolchain/uClibc/uClibc-0.9.32.config" BR2_BINUTILS_VERSION_2_21=y
BR2_BINUTILS_VERSION="2.21" BR2_BINUTILS_EXTRA_CONFIG_OPTIONS=""
BR2_GCC_VERSION_4_5_X=y
BR2_GCC_SUPPORTS_FINEGRAINEDMTUNE=y
BR2_GCC_VERSION="4.5.2"
BR2_EXTRA_GCC_CONFIG_OPTIONS=""
BR2_GCC_CROSS_OBJC=y
BR2_INSTALL_OBJC=y
BR2_GCC_SHARED_LIBGCC=y
BR2_PACKAGE_GDB_SERVER=y
BR2_GDB_VERSION_6_8=y
BR2_GDB_VERSION="6.8"
BR2_LARGEFILE=y
BR2_INET_IPV6=y
BR2_INET_RPC=y
BR2_USE_WCHAR=y
BR2_ENABLE_LOCALE=y
BR2_PROGRAM_INVOCATION=y
BR2_INSTALL_LIBSTDCPP=y
BR2_TOOLCHAIN_HAS_THREADS=y
BR2_NEEDS_GETTEXT=y
BR2_NEEDS_GETTEXT_IF_LOCALE=y
BR2_USE_MMU=y
BR2_PREFER_SOFT_FLOAT=y
BR2_SOFT_FLOAT=y
BR2_TARGET_OPTIMIZATION="-pipe" BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y BR2_TOOLCHAIN_BUILDROOT_INET_IPV6=y BR2_TOOLCHAIN_BUILDROOT_INET_RPC=y BR2_TOOLCHAIN_BUILDROOT_WCHAR=y BR2_TOOLCHAIN_BUILDROOT_LOCALE=y BR2_TOOLCHAIN_BUILDROOT_PROGRAM_INVOCATION=y BR2_TOOLCHAIN_BUILDROOT_CXX=y BR2_TOOLCHAIN_BUILDROOT_USE_SSP=y
BR2_PTHREADS_OLD=y
BR2_MKLIBS=y
BR2_TARGET_GENERIC_HOSTNAME="vx-200" BR2_TARGET_GENERIC_ISSUE="Veritrack Fleet Management (2011)" BR2_TARGET_GENERIC_GETTY=y BR2_TARGET_GENERIC_GETTY_PORT="ttyS0" BR2_TARGET_GENERIC_GETTY_BAUDRATE_115200=y BR2_TARGET_GENERIC_GETTY_BAUDRATE="115200" BR2_PACKAGE_BUSYBOX=y
BR2_BUSYBOX_VERSION_1_18_X=y
BR2_BUSYBOX_VERSION="1.18.4" BR2_PACKAGE_BUSYBOX_CONFIG="package/busybox/busybox-1.18.x.config" BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
BR2_PACKAGE_BZIP2=y
BR2_PACKAGE_STRACE=y
BR2_PACKAGE_GETTEXT=y
BR2_PACKAGE_LIBINTL=y
BR2_PACKAGE_GREP=y
BR2_PACKAGE_DBUS=y
BR2_DBUS_EXPAT=y
BR2_PACKAGE_DBUS_GLIB=y
BR2_PACKAGE_E2FSPROGS=y
BR2_PACKAGE_E2FSPROGS_LIBUUID=y BR2_PACKAGE_E2FSPROGS_LIBBLKID=y
BR2_PACKAGE_GPSD=y
BR2_PACKAGE_GPSD_DEVICES="/dev/ttyS4" BR2_PACKAGE_GPSD_NTP_SHM=y
BR2_PACKAGE_GPSD_PPS=y
BR2_PACKAGE_GPSD_PPS_ON_CTS=y
BR2_PACKAGE_GPSD_RECONFIGURE=y BR2_PACKAGE_GPSD_CONTROLSEND=y
BR2_PACKAGE_GPSD_RAW=y
BR2_PACKAGE_GPSD_SQUELCH=y
BR2_PACKAGE_GPSD_NMEA=y
BR2_PACKAGE_GPSD_SIRF=y
BR2_PACKAGE_HWDATA=y
BR2_PACKAGE_I2C_TOOLS=y
BR2_PACKAGE_MTD=y
BR2_PACKAGE_MTD_FLASHCP=y
BR2_PACKAGE_MTD_FLASH_ERASE=y BR2_PACKAGE_MTD_FLASH_ERASEALL=y BR2_PACKAGE_MTD_FLASH_INFO=y
BR2_PACKAGE_MTD_FLASH_LOCK=y
BR2_PACKAGE_MTD_FLASH_UNLOCK=y
BR2_PACKAGE_MTD_MTD_DEBUG=y
BR2_PACKAGE_MTD_NANDDUMP=y
BR2_PACKAGE_MTD_NANDTEST=y
BR2_PACKAGE_MTD_NANDWRITE=y
BR2_PACKAGE_MTD_MTDINFO=y
BR2_PACKAGE_MTD_UBIATTACH=y
BR2_PACKAGE_MTD_UBICRC32=y
BR2_PACKAGE_MTD_UBIDETACH=y
BR2_PACKAGE_MTD_UBIFORMAT=y
BR2_PACKAGE_MTD_UBIMKVOL=y
BR2_PACKAGE_MTD_UBINFO=y
BR2_PACKAGE_MTD_UBINIZE=y
BR2_PACKAGE_MTD_UBIRENAME=y
BR2_PACKAGE_MTD_UBIRMVOL=y
BR2_PACKAGE_MTD_UBIRSVOL=y
BR2_PACKAGE_MTD_UBIUPDATEVOL=y
BR2_PACKAGE_UDEV=y
BR2_PACKAGE_UDEV_UTILS=y
BR2_PACKAGE_UDEV_VOLUME_ID=y
BR2_PACKAGE_PYTHON=y
BR2_PACKAGE_PYTHON_PYC_ONLY=y
BR2_PACKAGE_PYTHON_READLINE=y
BR2_PACKAGE_LZO=y
BR2_PACKAGE_ZLIB=y
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_LIBLOCKFILE=y
BR2_PACKAGE_LIBPCAP=y
BR2_PACKAGE_LIBFFI=y
BR2_PACKAGE_LIBGLIB2=y
BR2_PACKAGE_NCURSES=y
BR2_PACKAGE_POPT=y
BR2_PACKAGE_READLINE=y
BR2_PACKAGE_EXPAT=y
BR2_PACKAGE_OPENSSH=y
BR2_PACKAGE_BASH=y
BR2_PACKAGE_FILE=y
BR2_PACKAGE_LOCKFILE_PROGS=y
BR2_PACKAGE_WHICH=y
BR2_PACKAGE_BOOTUTILS=y
BR2_PACKAGE_MODULE_INIT_TOOLS=y
BR2_PACKAGE_PSMISC=y
BR2_PACKAGE_SYSKLOGD=y
BR2_PACKAGE_SYSVINIT=y
BR2_PACKAGE_UTIL-LINUX=y
BR2_PACKAGE_LESS=y
BR2_ROOTFS_POST_BUILD_SCRIPT="" BR2_ROOTFS_DEVICE_TABLE="target/generic/device_table.txt" BR2_ROOTFS_SKELETON_DEFAULT=y
BR2_TARGET_ROOTFS_TAR=y
BR2_TARGET_ROOTFS_TAR_NONE=y BR2_TARGET_ROOTFS_TAR_OPTIONS=""
BR2_TARGET_ROOTFS_ROMFS=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="2.6.38-rc5" BR2_LINUX_KERNEL_VERSION="2.6.38-rc5" BR2_LINUX_KERNEL_PATCH="linux/kernel-patches/linux-2.6.38-rc5-0001.patch linux/kernel-patches/linux-2.6.38-rc5-0002.patch linux/kernel-patches/linux-2.6.38-rc5-0003.patch linux/kernel-patches/linux-2.6.38-rc5-0004.patch linux/kernel-patches/linux-2.6.38-rc5-0005.patch linux/kernel-patches/linux-2.6.38-rc5-0006.patch linux/kernel-patches/linux-2.6.38-rc5-0007.patch" BR2_LINUX_KERNEL_USE_DEFCONFIG=y BR2_LINUX_KERNEL_DEFCONFIG="telit_ge863" BR2_LINUX_KERNEL_UIMAGE=y

Quoted 64 lines · Carl

Hi,

I've done something bad to my Buildroot platform, but I can't figure out what the problem is.

When the initramfs system switches over to the root filesystem on an SD Card created by Buildroot,
it can't find /dev/null, and can't mount /proc.

When I login the /proc directory is not mounted, but I can manually mount it however from the command
line.

My inittab contains a statement to mount proc as well as another statement to do a 'mount -a'.
I verified that fstab contains an entry for proc. I know something is processing inittab because
the boot scripts that inittab calls do run.

I even added an entry in inittab to 'mknod' /dev/null.

I'm really stumped by this. I even did a clean rebuild without any luck.

Output below. Appreciate any help.

thanx
/carl h.

mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address aaaa
mmcblk0: mmc0:aaaa SD02G 1.84 GiB
mmcblk0: p1
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p1): using internal journal
EXT3-fs (mmcblk0p1): recovery complete
EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode Switching to filesystem on SD card....
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
grep: /proc/mounts: No such file or directory
grep: /proc/mounts: No such file or directory
Populating /dev using udev: /etc/init.d/S10udev: line 82: can't create /proc/sys/kernel/hotplug: nonexistent directory
done
Starting portmap: done
Initializing random number generator... done.
Starting network...
ifup: interface lo already configured
ifup: interface eth0 already configured
Starting ProFTPD: warning: `proftpd' uses 32-bit capabilities (legacy support in use)
- warning: unable to determine IP address of '_none_'
- error: no valid servers configured
- Fatal: error processing configuration file '/etc/proftpd.conf'
FAILED
Starting sshd: OK

Quoted 8 lines

Welcome to Buildroot
(none) login:

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110323/ce0f197e/attachment-0001.html>

#14 lore raw

[Buildroot] proc not mouning

In reply to Heyendal
Quoted 2 lines

-----Original Message-----
From: buildroot-bounces at busybox.net

[mailto:buildroot-bounces at busybox.net] On Behalf Of Heyendal, Carl

Quoted 7 lines

Sent: Wednesday, March 23, 2011 2:03 PM
To: buildroot at busybox.net
Subject: [Buildroot] proc not mouning

Hi,

I've done something bad to my Buildroot platform, but I can't figure

out what the problem is.

Quoted 2 lines

When the initramfs system switches over to the root filesystem on an

SD Card created by Buildroot,

Quoted 3 lines

it can't find /dev/null, and can't mount /proc.

When I login the /proc directory is not mounted, but I can manually

mount it however from the command

Quoted 3 lines

line.

My inittab contains a statement to mount proc as well as another

statement to do a 'mount -a'.

Quoted 1 line

I verified that fstab contains an entry for proc. I know something is

processing inittab because

Quoted 1 line

the boot scripts that inittab calls do run.

Are you mounting proc FIRST in inittab?

Andy

#15 lore raw

[Buildroot] proc not mouning

Quoted 29 lines

-----Original Message-----
From: ANDY KENNEDY [mailto:ANDY.KENNEDY at adtran.com]
Sent: March 23, 2011 3:33 PM
To: Heyendal, Carl; buildroot at busybox.net
Subject: RE: [Buildroot] proc not mouning

Quoted 2 lines

-----Original Message-----
From: buildroot-bounces at busybox.net

[mailto:buildroot-bounces at busybox.net] On Behalf Of Heyendal, Carl

Quoted 7 lines

Sent: Wednesday, March 23, 2011 2:03 PM
To: buildroot at busybox.net
Subject: [Buildroot] proc not mouning

Hi,

I've done something bad to my Buildroot platform, but I can't figure

out what the problem is.

Quoted 2 lines

When the initramfs system switches over to the root filesystem on an

SD Card created by Buildroot,

Quoted 3 lines

it can't find /dev/null, and can't mount /proc.

When I login the /proc directory is not mounted, but I can manually

mount it however from the command

Quoted 3 lines

line.

My inittab contains a statement to mount proc as well as another

Quoted 8 lines

statement to do a 'mount -a'.

Quoted 1 line

I verified that fstab contains an entry for proc. I know something is

processing inittab because

Quoted 1 line

the boot scripts that inittab calls do run.

Are you mounting proc FIRST in inittab?

Andy

Yes.

From inittab:

# Startup the system
null::sysinit:/bin/mount -t proc proc /proc
null::sysinit:/bin/mount -o remount,rw /
null::sysinit:/bin/mkdir -p /dev/pts
null::sysinit:/bin/mount -a
null::sysinit:/bin/hostname -F /etc/hostname

# now run any rc scripts
::sysinit:/etc/init.d/rcS

/carl h.

#18 lore raw

[Buildroot] proc not mouning

In reply to ANDY KENNEDY

My environment is different in that I tftpboot my kernel and mount the OS over NFS (not using sd card)

This is my inittab:

[root at vx-200 ~]# cat /etc/inittab

# /etc/inittab
#
# This inittab is a basic inittab sample for sysvinit, which mimics
# Buildroot's default inittab for Busybox.
id:1:initdefault:

proc::sysinit:/bin/mount -t proc proc /proc
rwmo::sysinit:/bin/mount -o remount,rw /
dpts::sysinit:/bin/mkdir -p /dev/pts
moun::sysinit:/bin/mount -a
host::sysinit:/bin/hostname -F /etc/hostname
init::sysinit:/etc/init.d/rcS

1:1:respawn:/sbin/getty 38400 tty1
2:1:respawn:/sbin/getty 38400 tty2

S0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL

# Logging junk
mess::sysinit:/bin/touch /var/log/messages
sysl:1:respawn:/sbin/syslogd -n -m 0
klog:1:respawn:/sbin/klogd -n

# Stuff to do for the 3-finger salute
rebo::ctrlaltdel:/sbin/reboot

# Stuff to do before rebooting
sklo:6:wait:/usr/bin/killall klogd
ssys:6:wait:/usr/bin/killall syslogd
umou:6:wait:/bin/umount -a -r
swap:6:wait:/sbin/swapoff -a
[root at vx-200 ~]#

Quoted 26 lines · ANDY KENNEDY
Quoted 2 lines

-----Original Message-----
From: buildroot-bounces at busybox.net

[mailto:buildroot-bounces at busybox.net] On Behalf Of Heyendal, Carl

Quoted 7 lines

Sent: Wednesday, March 23, 2011 2:03 PM
To: buildroot at busybox.net
Subject: [Buildroot] proc not mouning

Hi,

I've done something bad to my Buildroot platform, but I can't figure

out what the problem is.

Quoted 2 lines

When the initramfs system switches over to the root filesystem on an

SD Card created by Buildroot,

Quoted 3 lines

it can't find /dev/null, and can't mount /proc.

When I login the /proc directory is not mounted, but I can manually

mount it however from the command

Quoted 3 lines

line.

My inittab contains a statement to mount proc as well as another

statement to do a 'mount -a'.

Quoted 1 line

I verified that fstab contains an entry for proc. I know something is

processing inittab because

Quoted 1 line

the boot scripts that inittab calls do run.

Quoted 8 lines

Are you mounting proc FIRST in inittab?

Andy
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110323/deaedde0/attachment.html>

#16 lore raw

[Buildroot] proc not mouning

In reply to Heyendal
Quoted 14 lines
Quoted 3 lines

Are you mounting proc FIRST in inittab?

Andy

Yes.

From inittab:

# Startup the system
null::sysinit:/bin/mount -t proc proc /proc
null::sysinit:/bin/mount -o remount,rw /
null::sysinit:/bin/mkdir -p /dev/pts
null::sysinit:/bin/mount -a
null::sysinit:/bin/hostname -F /etc/hostname

Quoted 5 lines
# now run any rc scripts
::sysinit:/etc/init.d/rcS

/carl h.

Bummer.

Okay, what does this line do:

Quoted 1 line
Quoted 1 line

Switching to filesystem on SD card....

Do you have a script file for that?

#17 lore raw

[Buildroot] proc not mouning

Quoted 28 lines

-----Original Message-----
From: ANDY KENNEDY [mailto:ANDY.KENNEDY at adtran.com]
Sent: March 23, 2011 3:43 PM
To: Heyendal, Carl; buildroot at busybox.net
Subject: RE: [Buildroot] proc not mouning

Quoted 14 lines
Quoted 3 lines

Are you mounting proc FIRST in inittab?

Andy

Yes.

From inittab:

# Startup the system
null::sysinit:/bin/mount -t proc proc /proc
null::sysinit:/bin/mount -o remount,rw /
null::sysinit:/bin/mkdir -p /dev/pts
null::sysinit:/bin/mount -a
null::sysinit:/bin/hostname -F /etc/hostname

Quoted 5 lines
# now run any rc scripts
::sysinit:/etc/init.d/rcS

/carl h.

Quoted 7 lines

Bummer.

Okay, what does this line do:

Quoted 1 line
Quoted 1 line

Switching to filesystem on SD card....

Do you have a script file for that?

I print that out from my script in initramfs just before I un-mount /sys and /proc and call 'switch_root'.

" echo "Switching to filesystem on SD card...."
exec switch_root /newroot "${init}" "

I use initramfs to mount the driver for the SD card.

/carl

#19 lore raw

[Buildroot] proc not mouning

In reply to Heyendal
Quoted 74 lines

-----Original Message-----
From: buildroot-bounces at busybox.net [mailto:buildroot- bounces at busybox.net] On Behalf Of Heyendal, Carl
Sent: March 23, 2011 3:03 PM
To: buildroot at busybox.net
Subject: [Buildroot] proc not mouning

Hi,

I've done something bad to my Buildroot platform, but I can't figure out what the problem is.

When the initramfs system switches over to the root filesystem on an SD Card created by Buildroot,
it can't find /dev/null, and can't mount /proc.

When I login the /proc directory is not mounted, but I can manually mount it however from the command
line.

My inittab contains a statement to mount proc as well as another statement to do a 'mount -a'.
I verified that fstab contains an entry for proc. I know something is processing inittab because
the boot scripts that inittab calls do run.

I even added an entry in inittab to 'mknod' /dev/null.

I'm really stumped by this. I even did a clean rebuild without any luck.

Output below. Appreciate any help.

thanx
/carl h.

mmc0: host does not support reading read-only switch. assuming write- enable.
mmc0: new SD card at address aaaa
mmcblk0: mmc0:aaaa SD02G 1.84 GiB
mmcblk0: p1
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p1): using internal journal
EXT3-fs (mmcblk0p1): recovery complete
EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode Switching to filesystem on SD card....
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
can't open /dev/null: No such file or directory
grep: /proc/mounts: No such file or directory
grep: /proc/mounts: No such file or directory
Populating /dev using udev: /etc/init.d/S10udev: line 82: can't create /proc/sys/kernel/hotplug: nonexistent directory
done
Starting portmap: done
Initializing random number generator... done.
Starting network...
ifup: interface lo already configured
ifup: interface eth0 already configured
Starting ProFTPD: warning: `proftpd' uses 32-bit capabilities (legacy support in use)
- warning: unable to determine IP address of '_none_'
- error: no valid servers configured
- Fatal: error processing configuration file '/etc/proftpd.conf'
FAILED
Starting sshd: OK

Quoted 7 lines

Welcome to Buildroot
(none) login:

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Interestingly I solved the problem.

I was originally generating the root filesystem as a cpio archive and using that to populate my SD card. Later on, as a build optimization, I disabled generating rootfs.cpio at the top level Buildroot menuconfig. Instead I started copying 'output/target/*' over to my SD card. That's when the trouble began I guess. I switched back to using rootfs.cpio to populate the SD card and I no longer have the problem. :-)

I've been dinged by not using cpio formats before, but had forgotten. What is it about cpio keeping filesystem archives sane when you copy them to other media? Why can't I just 'cp' the entire filesystem over as root?

Thanks Andy for your attention.

/carl

#20 lore raw

[Buildroot] proc not mouning

Quoted 10 lines

Interestingly I solved the problem.

I was originally generating the root filesystem as a cpio archive and using that
to populate my SD card. Later on, as a build optimization, I disabled generating
rootfs.cpio at the top level Buildroot menuconfig. Instead I started copying
'output/target/*' over to my SD card. That's when the trouble began

Which gives you empty /dev/* files -- as these are created in the fakeroot. Perhaps you could just make tarroot and unpack that into your SD card. That _should_ give you real device nodes.

Quoted 5 lines

I guess. I
switched back to using rootfs.cpio to populate the SD card and I no longer have the
problem. :-)

Quoted 7 lines

I've been dinged by not using cpio formats before, but had forgotten. What is it
about cpio keeping filesystem archives sane when you copy them to other media?
Why can't I just 'cp' the entire filesystem over as root?

Thanks Andy for your attention.

Sorry I wasn't more help.

Quoted 2 lines

/carl

Andy

#25 lore raw
In reply to Baruch Siach

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Baruch,

Am 23.03.2011 18:16, schrieb Baruch Siach:

Quoted 3 lines

Do you have 32bit libraries on your host machine?

What is the output of 'sh -x /usr/bin/ldd dftables'?

I paste it below. Says something about 64bit. But my toolchain should only create 32bit files...strange.

+ TEXTDOMAIN=libc
+ TEXTDOMAINDIR=/usr/share/locale
+ RTLDLIST='/lib/ld-linux.so.2 /lib64/ld-linux-x86-64.so.2'
+ warn=
+ bind_now=
+ verbose=
+ test 1 -gt 0
+ case "$1" in
+ break
+ add_env='LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW='
+ add_env='LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out'
+ add_env='LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= LD_LIBRARY_VERSION=$verify_out LD_VERBOSE='
+ test '' = yes
+ set -o pipefail
+ case $# in
+ single_file=t
+ result=0
+ for file in '"$@"'
+ test t = t
+ case $file in
+ :
+ test '!' -e /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/dftables
+ test '!' -f /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/dftables
+ test -r /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/dftables
+ test -x /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/dftables
+ RTLD=
+ ret=1
+ for rtld in '${RTLDLIST}'
+ test -x /lib/ld-linux.so.2
++ /lib/ld-linux.so.2 --verify /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/dftables
+ verify_out=6
+ ret=0
+ case $ret in
+ RTLD=/lib/ld-linux.so.2
+ break
+ case $ret in
+ try_trace /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/dftables
+ eval LD_TRACE_LOADED_OBJECTS=1 LD_WARN= LD_BIND_NOW= 'LD_LIBRARY_VERSION=$verify_out' LD_VERBOSE= '"$@"'
++ LD_TRACE_LOADED_OBJECTS=1
++ LD_WARN=
++ LD_BIND_NOW=
++ LD_LIBRARY_VERSION=6
++ LD_VERBOSE=
++ /LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/dftables
+ cat
/usr/bin/ldd: Zeile 118:
/LFS/buildroot-2011.02/output/build/httpd-2.2.17/srclib/pcre/dftables:
Datei oder Verzeichnis nicht gefunden
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this says "File or Directory not found"
+ rc=127
+ '[' 127 = 5 ']'
+ '[' 127 = 0 ']'
+ result=1
+ exit 1

- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNiufBAAoJEEMkp/gkis19h70IAM4Yehv9vwKem0pNVJfOy+Wt RJokwheDCBajcNrob8XShLU1RNvrZXu6rzFkvPgkZckcz3d9W8gjNXUORhkcXf1p 2hHtdOolpw7A1IAQc/qmpD9fhcHr4dvXVecg8QdC5o83Be22WSjwHYTldZhV6Rx9 VQNyzbhqVbUG9ibHeMC+Rur6a9ZrodbbDSVljaBLsT7akSglhiNvzDBV+AWobVeS llGaP4cvZ16Npw9S5IxQUy7wD5Ko8gGidkVq+NHNdq1IAE0s3/hwWaIUp4CR4dna 0SrRRMO/Hwuie0WC47SH2CKKTJK8P7ewQ+lVzSCIv4DrDTJQBA+mK90By7cvtK0= =Ll3f
-----END PGP SIGNATURE-----

#21 lore raw

[Buildroot] proc not mouning

In reply to Heyendal

Hello,

Quoted 7 lines · Carl

I was originally generating the root filesystem as a cpio archive and using that to populate my SD card. Later on, as a build optimization, I disabled generating rootfs.cpio at the top level Buildroot menuconfig. Instead I started copying 'output/target/*' over to my SD card. That's when the trouble began I guess. I switched back to using rootfs.cpio to populate the SD card and I no longer have the problem. :-)

From the Buildroot documentation at
http://buildroot.org/downloads/buildroot.html :

target/ which contains almost the complete root filesystem for the
target: everything needed is present except the device files in /dev/ (Buildroot can't create them because Buildroot doesn't run as root and doesn't want to run as root). Therefore, this directory should not be used on your target. Instead, you should use one of the images built in the images/ directory. If you need an extracted image of the root filesystem for booting over NFS, then use the tarball image generated in images/ and extract it as root.

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#22 lore raw

[Buildroot] proc not mouning

Quoted 33 lines

-----Original Message-----
From: buildroot-bounces at busybox.net [mailto:buildroot- bounces at busybox.net] On Behalf Of Thomas Petazzoni
Sent: March 24, 2011 2:59 PM
To: buildroot at busybox.net
Subject: Re: [Buildroot] proc not mouning

Hello,

Quoted 9 lines · Carl

I was originally generating the root filesystem as a cpio archive and using that to populate my SD card. Later on, as a build optimization, I disabled generating rootfs.cpio at the top level Buildroot menuconfig. Instead I started copying 'output/target/*' over to my SD card. That's when the trouble began I guess. I switched back to using rootfs.cpio to populate the SD card and I no longer have the problem. :-)

From the Buildroot documentation at

http://buildroot.org/downloads/buildroot.html :

target/ which contains almost the complete root filesystem for the
target: everything needed is present except the device files in /dev/ (Buildroot can't create them because Buildroot doesn't run as root and doesn't want to run as root). Therefore, this directory should not be used on your target. Instead, you should use one of the images built
in
the images/ directory. If you need an extracted image of the root filesystem for booting over NFS, then use the tarball image generated in images/ and extract it as root.

Quoted 10 lines

Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Thanks for the RTFMS. :-)

/carl h.

#23 lore raw

[Buildroot] proc not mouning

Hi,

I am running into a similar issue when trying to run an i386 image with ISO9660. Under qemu, it boots up to the point where it constantly complains about /dev/null and /dev/ttyS0 not being present. I am using the default inittab.

I have tried using udev, mdev and devtmpfs. The kernel config has these options:

CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y

Is there a workaround? Maybe creating them manually in inittab?

Thanks
Vincent

On Thu, Mar 24, 2011 at 12:04 PM, Heyendal, Carl <[email protected]

Quoted 48 lines
Quoted 33 lines · wrote:

-----Original Message-----
From: buildroot-bounces at busybox.net [mailto:buildroot- bounces at busybox.net] On Behalf Of Thomas Petazzoni
Sent: March 24, 2011 2:59 PM
To: buildroot at busybox.net
Subject: Re: [Buildroot] proc not mouning

Hello,

Quoted 9 lines · Carl

I was originally generating the root filesystem as a cpio archive and using that to populate my SD card. Later on, as a build optimization, I disabled generating rootfs.cpio at the top level Buildroot menuconfig. Instead I started copying 'output/target/*' over to my SD card. That's when the trouble began I guess. I switched back to using rootfs.cpio to populate the SD card and I no longer have the problem. :-)

From the Buildroot documentation at

http://buildroot.org/downloads/buildroot.html :

target/ which contains almost the complete root filesystem for the
target: everything needed is present except the device files in /dev/ (Buildroot can't create them because Buildroot doesn't run as root and doesn't want to run as root). Therefore, this directory should not be used on your target. Instead, you should use one of the images built
in
the images/ directory. If you need an extracted image of the root filesystem for booting over NFS, then use the tarball image generated in images/ and extract it as root.

Quoted 10 lines

Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Thanks for the RTFMS. :-)

Quoted 8 lines

/carl h.

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20111021/14b9ff72/attachment-0001.html>

#24 lore raw

[Buildroot] proc not mouning

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"vbr" == vbr vbr <[email protected]> writes:

vbr> Hi,
vbr> I am running into a similar issue when trying to run an i386 image with vbr> ISO9660. Under qemu, it boots up to the point where it constantly complains vbr> about /dev/null and /dev/ttyS0 not being present. I am using the default vbr> inittab.

vbr> I have tried using udev, mdev and devtmpfs. The kernel config has these vbr> options:

vbr> CONFIG_DEVTMPFS=y
vbr> CONFIG_DEVTMPFS_MOUNT=y

vbr> Is there a workaround? Maybe creating them manually in inittab?

It shouldn't be needed. Could you provide a bit more details about what you're doing exactly? Could you run 'make savedefconfig' and post the generated defconfig file?

Signature · 1 line
Bye, Peter Korsgaard