Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.landwerlin@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain improvements
Date: Fri, 03 Jul 2009 08:01:43 +0200	[thread overview]
Message-ID: <1246600903.8052.8.camel@coalu.atr> (raw)
In-Reply-To: <20090702145011.6b9f3fe9@surf>

Le jeudi 02 juillet 2009 ? 14:50 +0200, Thomas Petazzoni a ?crit :
> Hi,
> 
> Le Wed, 01 Jul 2009 23:43:34 +0200,
> Lionel Landwerlin <lionel.landwerlin@openwide.fr> a ?crit :
> 
> > Ok, I had another look at the ext-tool.mk makefile, and the sysroot
> > dir is not copied because of the locale...
> > 
> > This current command to get the sysroot dir is :
> > 
> > SYSROOT_DIR=`$(TARGET_CC) -v 2>&1 | grep ^Configured | tr " " "\n" |
> > grep -- "--with-sysroot" | cut -f2 -d=`;
> > 
> > which call (in my case) sh4-linux-gcc using the default locale and as
> > my email address could suggest, my current locale is fr_FR.UTF-8. So
> > grep ^Configured just fails.
> > 
> > Please apply the attached patch to your external-toolchain branch.
> 
> Ok, thanks for patch. I should probably add a little bit of error
> checking in this external toolchain thing.
> 
> > >  * Buildroot version
> > 
> > Your external-toolchain branch
> 
> Which doesn't exist anymore since it has been merged in the official
> Buildroot :-)
> 
> But ok, fine, I know what you're using.

I'm now up to date on the last git.

> 
> > >  * Error messages
> > 
> > I will try to retry with the fix on the locale first.
> 
> For sure if Buildroot didn't properly copy the sysroot to the staging
> dir, the rest of the compilation could not work.
> 
> That said, your configuration file enables a relatively large set of
> packages that I haven't tested with the external toolchain
> configuration. Most if not all of the packages using the
> Makefile.autotools.in machinery should build flawlessly, but the
> packages using their own stuff in the .mk might break. Don't hesitate
> to report the breakage with the associated error messages (or the full
> build output), it's usually relatively easy to fix.

Ok, so I just rerun buildroot again with full staging directory copied
from the external toolchain, and I got that when compiling glib2 :


libtool: install: (cd /home/djdeath/src/buildroot/buildroot/build_sh4/libglib2-2.20.1/gmodule; /bin/sh /home/djdeath/src/buildroot/buildroot/build_sh4/libglib2-2.20.1/libtool  --tag CC --mode=relink /opt/STM/STLinux-2.3/devkit/sh4/bin/sh4-linux-gcc -O2 -O2 --sysroot /home/djdeath/src/buildroot/buildroot/build_sh4/staging_dir/ -O2 -O2 --sysroot /home/djdeath/src/buildroot/buildroot/build_sh4/staging_dir/ -Wall -version-info 2000:1:2000 -export-dynamic --sysroot /home/djdeath/src/buildroot/buildroot/build_sh4/staging_dir/ -o libgmodule-2.0.la -rpath /usr/lib gmodule.lo -ldl ../glib/libglib-2.0.la -lintl -inst-prefix-dir /home/djdeath/src/buildroot/buildroot/project_build_sh4/uclibc/root)
libtool: relink: /opt/STM/STLinux-2.3/devkit/sh4/bin/sh4-linux-gcc -O2 -O2  --sysroot /home/djdeath/src/buildroot/buildroot/build_sh4/staging_dir/ -shared  .libs/gmodule.o   -Wl,-rpath -Wl,/home/djdeath/src/buildroot/buildroot/build_sh4/staging_dir/usr/lib -ldl -L/home/djdeath/src/buildroot/buildroot/project_build_sh4/uclibc/root/usr/lib -L/usr/lib -lglib-2.0 -L/home/djdeath/src/buildroot/buildroot/build_sh4/staging_dir/usr/lib -L/home/djdeath/src/buildroot/buildroot/project_build_sh4/uclibc/root/home/djdeath/src/buildroot/buildroot/build_sh4/staging_dir/usr/lib -lintl -lc    -Wl,-soname -Wl,libgmodule-2.0.so.0 -o .libs/libgmodule-2.0.so.0.2000.1
/usr/lib/libdl.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status
libtool: install: error: relink `libgmodule-2.0.la' with the above command before installing it
make[6]: *** [install-libLTLIBRARIES] Erreur 1
make[6]: quittant le r?pertoire ? /home/djdeath/src/buildroot/buildroot/build_sh4/libglib2-2.20.1/gmodule ?
make[5]: *** [install-am] Erreur 2
make[5]: quittant le r?pertoire ? /home/djdeath/src/buildroot/buildroot/build_sh4/libglib2-2.20.1/gmodule ?
make[4]: *** [install] Erreur 2
make[4]: quittant le r?pertoire ? /home/djdeath/src/buildroot/buildroot/build_sh4/libglib2-2.20.1/gmodule ?
make[3]: *** [install-recursive] Erreur 1
make[3]: quittant le r?pertoire ? /home/djdeath/src/buildroot/buildroot/build_sh4/libglib2-2.20.1 ?
make[2]: *** [install] Erreur 2
make[2]: quittant le r?pertoire ? /home/djdeath/src/buildroot/buildroot/build_sh4/libglib2-2.20.1 ?
make[1]: *** [install-strip] Erreur 2
make[1]: quittant le r?pertoire ? /home/djdeath/src/buildroot/buildroot/build_sh4/libglib2-2.20.1 ?
make: *** [/home/djdeath/src/buildroot/buildroot/project_build_sh4/uclibc/autotools-stamps/libglib2_target_installed] Erreur 2

As you can see, there is a -L/usr/lib and -rpath /usr/lib.


-- 
Lionel Landwerlin <lionel.landwerlin@openwide.fr>

  reply	other threads:[~2009-07-03  6:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1246405094.1110.buildroot@busybox.net>
2009-06-30 23:50 ` [Buildroot] External toolchain improvements Lionel Landwerlin
2009-06-30 23:54 ` Lionel Landwerlin
2009-07-01 14:05   ` Thomas Petazzoni
2009-07-01 21:43     ` Lionel Landwerlin
2009-07-02 12:50       ` Thomas Petazzoni
2009-07-03  6:01         ` Lionel Landwerlin [this message]
2009-07-03  8:13           ` Thomas Petazzoni
2009-07-03 21:24             ` Lionel Landwerlin
2009-07-06  0:51             ` Lionel Landwerlin
2009-07-13 19:26         ` Lionel Landwerlin
2009-07-14 14:41           ` Thomas Petazzoni
2009-07-14 19:51             ` Lionel Landwerlin
2009-06-01 16:54 Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1246600903.8052.8.camel@coalu.atr \
    --to=lionel.landwerlin@openwide.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox