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] [autobuild.buildroot.net] Build results for 2014-04-07
Date: Thu, 10 Apr 2014 23:41:14 +0200	[thread overview]
Message-ID: <20140410234114.6c1c72cd@skate> (raw)
In-Reply-To: <CAMo8BfLKSdQnr2+a-WDCj9zJAPgXyitcM42fMDYhvDkzPfeR2Q@mail.gmail.com>

Dear Max Filippov,

On Wed, 9 Apr 2014 01:51:08 +0400, Max Filippov wrote:

> >> >     xtensa |                     php-5.5.11 | NOK | http://autobuild.buildroot.net/results/959b77fa2c1f13b1958b234803437e09734e882e/
> >>
> >> Couldn't reproduce. But I had to disable BR2_PACKAGE_HOST_SAM_BA,
> >> otherwise it refused to build with the following message:
> >>
> >> Your Buildroot configuration uses pre-built tools for the x86 architecture,
> >> but your build machine uses the x86-64 architecture without the 32
> >> bits compatibility library.
> >
> > I think we can safely assume that the problem is not due to
> > BR2_PACKAGE_HOST_SAM_BA. I'll try to reproduce the same build failure
> > on the autobuilder, and gather the config.log file of php. I'll let you
> > know.
> 
> The tail of the failing build log:
> 
> ...
> checking for MySQL support... yes
> checking for specified location of the MySQL UNIX socket... no
> checking for mysql_close in -lmysqlclient... no
> checking for mysql_error in -lmysqlclient... no
> configure: error: mysql configure failed. Please check config.log for
> more information.
> make: *** [/home/test/test/2/output/build/php-5.5.11/.stamp_configured] Error 1

Ok, I reproduced the problem. The config.log of php contains the
following problem:

configure:58794: result: no
configure:59004: checking for mysql_error in -lmysqlclient
configure:59029: /home/test/outputs/959b77fa2c1f13b1958b234803437e09734e882e/output/host/usr/bin/xtensa-buildroot-linux-uclibc-gcc -o conftest -I/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURC
E -D_FILE_OFFSET_BITS=64 -mlongcalls -mtext-section-literals -pipe -Os  -fvisibility=hidden -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -L/home/test/outputs/959b77fa2c1f13b1
958b234803437e09734e882e/output/host/usr/xtensa-buildroot-linux-uclibc/sysroot/usr/lib/mysql -L/home/test/outputs/959b77fa2c1f13b1958b234803437e09734e882e/output/host/usr/xtensa-buildroot-linux-
uclibc/sysroot/usr/lib -L/lib  -L/home/test/outputs/959b77fa2c1f13b1958b234803437e09734e882e/output/host/usr/xtensa-buildroot-linux-uclibc/sysroot/usr/lib -L/home/test/outputs/959b77fa2c1f13b195
8b234803437e09734e882e/output/host/usr/xtensa-buildroot-linux-uclibc/sysroot/usr conftest.c -lmysqlclient  -lz -lintl -lcrypto -lssl -lcrypto -lcurl -lz -lcrypto -lssl -lcrypto -lm  -lxml2 -lz -
lm -ldl -lcurl >&5
/lib/libgcc_s.so.1: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status

The problem is due to the compilation command line containing -L/lib,
which is wrong when cross-compiling.

See also
https://gist.github.com/anonymous/10425853#file-gistfile1-txt-L8083 for
the full config.log file. I'm keeping the build output directory
around, in case additional informations are needed.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-04-10 21:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-07 Thomas Petazzoni
2014-04-08 21:00 ` Max Filippov
2014-04-08 21:41   ` Thomas Petazzoni
2014-04-08 21:51     ` Max Filippov
2014-04-10 21:41       ` Thomas Petazzoni [this message]
2014-04-11  6:01         ` Max Filippov
2014-04-11  7:51           ` Thomas Petazzoni
2014-04-11  8:08             ` Max Filippov

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=20140410234114.6c1c72cd@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