Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Problem with buildroot and external toolchain
@ 2008-06-17 17:41 hartleys
  2008-06-17 18:38 ` sjhill at realitydiluted.com
  0 siblings, 1 reply; 8+ messages in thread
From: hartleys @ 2008-06-17 17:41 UTC (permalink / raw)
  To: buildroot

Hello all,

Sorry if this is sent to the wrong list.

I am trying to use buildroot with an external toolchain. I was able to
get everything setup and the Linux zImage and root filesystem are both
built. But when the kernel boots I get a kernel panic no init found.

I think I worked the problem down to the external toolchain libraries
not getting copied to the root filesystem. The copy_toolchain_lib_root
in ext-tool.mk does locate the libraries to copy but I don't get the
messages about the libraries being copied.

The only thing I can figure is the find in:

	for FILE in `find $${LIB_DIR} -maxdepth 1 -type l -name
"$${LIB}*"`; do { \

Is failing for some reason. Can anyone please offer any help on this?

Thanks,
Hartley

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] Problem with buildroot and external toolchain
  2008-06-17 17:41 [Buildroot] Problem with buildroot and external toolchain hartleys
@ 2008-06-17 18:38 ` sjhill at realitydiluted.com
  2008-06-17 18:57   ` hartleys
  0 siblings, 1 reply; 8+ messages in thread
From: sjhill at realitydiluted.com @ 2008-06-17 18:38 UTC (permalink / raw)
  To: buildroot

> I think I worked the problem down to the external toolchain libraries
> not getting copied to the root filesystem. The copy_toolchain_lib_root
> in ext-tool.mk does locate the libraries to copy but I don't get the
> messages about the libraries being copied.
> 
> The only thing I can figure is the find in:
> 
> 	for FILE in `find $${LIB_DIR} -maxdepth 1 -type l -name
> "$${LIB}*"`; do { \
> 
> Is failing for some reason. Can anyone please offer any help on this?
> 
Here is what I have for an external glibc-based toolchain:

BR2_TOOLCHAIN_EXTERNAL_LIB_C="libc.so.6"
BR2_TOOLCHAIN_EXTERNAL_LIBS="ld.so.1 libcrypt.so libdl.so libgcc_s.so libm.so libnsl.so libnss_dns.so libnss_files.so libpthread.so libresolv.so librt.so libstdc++.so libutil.so"

BR2_TOOLCHAIN_EXTERNAL_PATH="/opt/toolchains/gcc-3.4.5-glibc-2.3.6/powerpc-7450-linux-gnu"
BR2_TOOLCHAIN_EXTERNAL_PREFIX="powerpc-7450-linux-gnu"

The libraries will be copied from:

  $(BR2_TOOLCHAIN_EXTERNAL_PATH)/$(BR2_TOOLCHAIN_EXTERNAL_PREFIX)/lib

Hope that helps.

-Steve

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] Problem with buildroot and external toolchain
  2008-06-17 18:38 ` sjhill at realitydiluted.com
@ 2008-06-17 18:57   ` hartleys
  2008-06-17 19:04     ` Peter Korsgaard
  0 siblings, 1 reply; 8+ messages in thread
From: hartleys @ 2008-06-17 18:57 UTC (permalink / raw)
  To: buildroot

> > I think I worked the problem down to the external toolchain
libraries 
> > not getting copied to the root filesystem. The
copy_toolchain_lib_root 
> > in ext-tool.mk does locate the libraries to copy but I don't get the

> > messages about the libraries being copied.
> > 
> > The only thing I can figure is the find in:
> > 
> > 	for FILE in `find $${LIB_DIR} -maxdepth 1 -type l -name
"$${LIB}*"`; 
> > do { \
> > 
> > Is failing for some reason. Can anyone please offer any help on
this?
> > 
> Here is what I have for an external glibc-based toolchain:
>
> BR2_TOOLCHAIN_EXTERNAL_LIB_C="libc.so.6"
> BR2_TOOLCHAIN_EXTERNAL_LIBS="ld.so.1 libcrypt.so libdl.so libgcc_s.so
libm.so
> libnsl.so libnss_dns.so libnss_files.so libpthread.so libresolv.so
librt.so
> libstdc++.so libutil.so"
>
>
BR2_TOOLCHAIN_EXTERNAL_PATH="/opt/toolchains/gcc-3.4.5-glibc-2.3.6/power
pc-7450-linux-gnu"
> BR2_TOOLCHAIN_EXTERNAL_PREFIX="powerpc-7450-linux-gnu"
>
> The libraries will be copied from:
>
>  $(BR2_TOOLCHAIN_EXTERNAL_PATH)/$(BR2_TOOLCHAIN_EXTERNAL_PREFIX)/lib
>
> Hope that helps.

Thanks for the quick reply.

My setup is for an external uclibc-based toolchain:

BR2_TOOLCHAIN_EXTERNAL_LIB_C="libc.so.0"
BR2_TOOLCHAIN_EXTERNAL_LIBS="ld-uClibc.so.0 libcrypt.so.0 libdl.so.0
libm.so.0 ... (others)"

BR2_TOOLCHAIN_EXTERNAL_PATH="/usr/local/arm/4.1.1-920t"
BR2_TOOLCHAIN_EXTERNAL_PREFIX="arm-linux"

My library files are in the
$(BR2_TOOLCHAIN_EXTERNAL_PATH)/$(BR2_TOOLCHAIN_EXTERNAL_PREFIX)/lib
directory.

But, like I said, the copy_toolchain_lib_root is locating the files but
not actually copying them. If I manually copy the files to the root file
system everything works fine.

Any other ideas?

Hartley

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] Problem with buildroot and external toolchain
  2008-06-17 18:57   ` hartleys
@ 2008-06-17 19:04     ` Peter Korsgaard
  2008-06-17 19:13       ` hartleys
  2008-06-17 20:15       ` hartleys
  0 siblings, 2 replies; 8+ messages in thread
From: Peter Korsgaard @ 2008-06-17 19:04 UTC (permalink / raw)
  To: buildroot

>>>>> "hartleys" == hartleys  <hartleys@visionengravers.com> writes:

Hi,

 hartleys> But, like I said, the copy_toolchain_lib_root is locating
 hartleys> the files but not actually copying them. If I manually copy
 hartleys> the files to the root file system everything works fine.

Does <cross>-gcc -printf-file-name=<lib> give the right path? Have you
seen the new defaults I added to those settings lately? Those work for
me with a uclibc toolchain.

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] Problem with buildroot and external toolchain
  2008-06-17 19:04     ` Peter Korsgaard
@ 2008-06-17 19:13       ` hartleys
  2008-06-17 20:15       ` hartleys
  1 sibling, 0 replies; 8+ messages in thread
From: hartleys @ 2008-06-17 19:13 UTC (permalink / raw)
  To: buildroot

Peter Korsgaard write:
> Hi,
>
> Does <cross>-gcc -printf-file-name=<lib> give the right path? Have 
> you seen the new defaults I added to those settings lately? Those
> work for me with a uclibc toolchain.

$ arm-linux-gcc -print-file-name=libc.so.0
/usr/local/arm/4.1.1-920t/lib/gcc/arm-linux-uclibc/4.1.1/../../../../arm
-linux-uclibc/lib/libc.so.0

Yes the path is correct. That directory has all the library files.

What defaults are you referring to? If it's the
BR2_TOOLCHAIN_EXTERNASL_LIBS then I have not modified it from the
default.

Hartley 

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] Problem with buildroot and external toolchain
  2008-06-17 19:04     ` Peter Korsgaard
  2008-06-17 19:13       ` hartleys
@ 2008-06-17 20:15       ` hartleys
  2008-06-18  6:46         ` Peter Korsgaard
  1 sibling, 1 reply; 8+ messages in thread
From: hartleys @ 2008-06-17 20:15 UTC (permalink / raw)
  To: buildroot

Could the problem I am having with ext-tool.mk not copying my external
toolchain library files be related to the version of find installed on
my system?

I'm running Debian etch which has the following find version:

$ find --version
GNU find version 4.2.28
Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION

I see on the GNU site that the latest version is 4.4.0 and the one
buildroot pulls in is 4.2.31.

Thanks
Hartley

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] Problem with buildroot and external toolchain
  2008-06-17 20:15       ` hartleys
@ 2008-06-18  6:46         ` Peter Korsgaard
  2008-06-18 18:28           ` hartleys
  0 siblings, 1 reply; 8+ messages in thread
From: Peter Korsgaard @ 2008-06-18  6:46 UTC (permalink / raw)
  To: buildroot

>>>>> "hartleys" == hartleys  <hartleys@visionengravers.com> writes:

Hi,

 hartleys> Could the problem I am having with ext-tool.mk not copying
 hartleys> my external toolchain library files be related to the
 hartleys> version of find installed on my system?

 hartleys> I'm running Debian etch which has the following find version:

 hartleys> $ find --version
 hartleys> GNU find version 4.2.28

I doubt it. I'm using 4.2.31 (on Debian as well).

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] Problem with buildroot and external toolchain
  2008-06-18  6:46         ` Peter Korsgaard
@ 2008-06-18 18:28           ` hartleys
  0 siblings, 0 replies; 8+ messages in thread
From: hartleys @ 2008-06-18 18:28 UTC (permalink / raw)
  To: buildroot

Peter Korsgaard writes:
> I doubt it. I'm using 4.2.31 (on Debian as well).

Hello Peter,

I've been messing with the ext-tool.mk trying to figure out why the
external libraries are not getting copied to the root filesystem.

I added some echo statements in copy_toolchain_lib_root and verified
that the LIB, DEST, and STRIP values are getting set correctly. The
LIB_DIR is getting set correctly to the path of the external library.

It still appears that the find statement in the for loop is not working
right. I added a

	echo "FILE=$${FILE}"; \

Right after the "for FILE in ..." stuff and never get an echo statement.

Any other ideas what might be the problem?

Thanks,
Hartley

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2008-06-18 18:28 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-17 17:41 [Buildroot] Problem with buildroot and external toolchain hartleys
2008-06-17 18:38 ` sjhill at realitydiluted.com
2008-06-17 18:57   ` hartleys
2008-06-17 19:04     ` Peter Korsgaard
2008-06-17 19:13       ` hartleys
2008-06-17 20:15       ` hartleys
2008-06-18  6:46         ` Peter Korsgaard
2008-06-18 18:28           ` hartleys

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox