Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] allyespackageconfig build on ARM/Linaro
Date: Tue, 18 Dec 2012 10:40:40 +0100	[thread overview]
Message-ID: <20121218104040.7f5f3c79@skate> (raw)
In-Reply-To: <878v8v7lwq.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Tue, 18 Dec 2012 10:24:37 +0100, Peter Korsgaard wrote:

>  Thomas> Here are my notes:
> 
>  Thomas>  * I've disabled JamVM and Classpath, because my testing chroot does
>  Thomas>    not have javac. So those packages are not tested.
> 
>  Thomas>  * mplayer failed to build, so I had to disable it, and also disable
>  Thomas>    libplayer, which was selecting mplayer. The mplayer build failure is
>  Thomas>    FPU related:
> 
> Sounds related to the mplayer/fpu discussion we had fairly recently.

Indeed.

>  Thomas>  * ltp-testsuite fails to build (build failures already seen with the
>  Thomas>    autobuilders):
> 
>  Thomas> common.c: In function 'create_net_namespace':
>  Thomas> common.c:64:17: error: 'CLONE_NEWNS' undeclared (first use in this function)
>  Thomas> common.c:64:17: note: each undeclared identifier is reported only once for each function it appears in
>  Thomas> common.c: In function 'child_fn':
>  Thomas> common.c:124:11: error: 'CLONE_NEWNS' undeclared (first use in this function)
>  Thomas> common.c:127:11: error: 'CLONE_FS' undeclared (first use in this function)
> 
> Odd, CLONE_NEWNS has existing for many years and common.c seems to
> include sched.h

Yes, I haven't looked at this one yet, but it is strange.

>  Thomas>  * pcmanfm failed to build:
> 
>  Thomas> /home/test/outputs/allpkg/host/opt/ext-toolchain/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: fm-desktop.o: undefined reference to symbol 'XSendEvent'
>  Thomas> /home/test/outputs/allpkg/host/opt/ext-toolchain/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: note: 'XSendEvent' is defined in DSO /home/test/outputs/allpkg/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/libX11.so.6 so try adding it to the linker command line
>  Thomas> /home/test/outputs/allpkg/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/libX11.so.6: could not read symbols: Invalid operation
>  Thomas> collect2: error: ld returned 1 exit status
>  Thomas> make[4]: *** [pcmanfm] Error 1
> 
> Strange about all these linker issues.

No, not really strange. There has been a change in gcc 4.6 with regard
to linking some time ago. See
http://www.gentoo.org/proj/en/qa/asneeded.xml. This is causing build
breakage in some packages that had an incorrect list of libraries to
link with.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-12-18  9:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18  9:09 [Buildroot] allyespackageconfig build on ARM/Linaro Thomas Petazzoni
2012-12-18  9:24 ` Peter Korsgaard
2012-12-18  9:40   ` Thomas Petazzoni [this message]
2012-12-18 10:11     ` Peter Korsgaard

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=20121218104040.7f5f3c79@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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