From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-02-21
Date: Mon, 22 Feb 2016 22:55:20 +0100 [thread overview]
Message-ID: <56CB83C8.3090500@gmail.com> (raw)
In-Reply-To: <CALdGskKUp-GtxeOBWq-5Tzp7b2zBad3=RoRxeN1eaJHPcg5Xww@mail.gmail.com>
Hi Olivier, All,
Le 22/02/2016 20:05, Olivier Schonken a ?crit :
> Hi Thomas, All
>
>
> arm | cups-2.1.2 | NOK
> | http://autobuild.buildroot.net/results/07ccca8f80c56ab0ff48bfee876885b1c8c3916e/
> arc | cups-2.1.2 | NOK
> | http://autobuild.buildroot.net/results/b169b939e38cb761319a92d2871f4f59ddb5c4ac/
>
> Both error cases looks like it has to do with uclibc not behaving as expected at
> link time for the ippserver build (Both builds link statically with position
> independent execution also set). For the arm platform it can't find the Scrt1.o
> file, and for the ARC compiler, __init_array_end is undefined.
Thanks for the investigation!
I don't think it's related to uClibc library but static build only
(BR2_STATIC_LIBS=y).
>
> I haven't considered all the options yet, but two that come to mind are
> disabling cups support for uclibc type compilers, or else to disable the cups
> test-framework.
>
> The missing Scrt1.o has to do with the compiler. In the Configure step,
> autotools checks whether the compiler is capable of generating position
> independent executables.
>
> "checking whether compiler supports -fPIE... yes"
Can you try with LSB_BUILD=y in CUPS_CONF_OPTS ?
This allow to remove -fPIE -pie from CFLAGS.
Maybe something like:
# Remove -fPIE -pie from CFLAGS
ifeq ($(BR2_STATIC_LIBS),y)
CUPS_CONF_OPTS += LSB_BUILD=y
endif
Best regards,
Romain
>
> In the linking stage it then looks for Scrt1.o, which it can't find. This
> breaks the build.
>
> From http://dev.gentoo.org/~vapier/crt.txt
> crt1.o
> Newer style of the initial runtime code. Contains the _start symbol which
> sets up the env with argc/argv/libc _init/libc _fini before jumping to the
> libc main. glibc calls this file 'start.S'.
> Scrt1.o
> Used in place of crt1.o when generating PIEs.
>
> Regards
>
> Olivier Schonken
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2016-02-22 21:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 19:05 [Buildroot] Analysis of build results for 2016-02-21 Olivier Schonken
2016-02-22 21:55 ` Romain Naour [this message]
2016-02-22 22:21 ` Thomas Petazzoni
2016-02-23 7:34 ` Olivier Schonken
2016-02-23 8:11 ` Thomas Petazzoni
2016-02-23 11:13 ` Olivier Schonken
2016-02-24 21:30 ` Waldemar Brodkorb
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 7:30 [Buildroot] [autobuild.buildroot.net] Build " Thomas Petazzoni
2016-02-22 14:05 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-02-23 10:12 ` John Keeping
2016-02-23 10:40 ` Jeroen Roovers
2016-02-23 11:03 ` John Keeping
2016-02-23 12:30 ` Thomas Petazzoni
2016-02-24 11:08 ` Eric Limpens
2016-02-24 20:45 ` Arnout Vandecappelle
2016-02-24 20:59 ` Eric Limpens
2016-02-24 21:42 ` Waldemar Brodkorb
2016-02-24 22:09 ` Arnout Vandecappelle
2016-02-27 15:19 ` Romain Naour
2016-02-27 22:05 ` Bernd Kuhls
2016-03-01 9:38 ` Thomas Petazzoni
2016-02-28 0:17 ` Bernd Kuhls
2016-03-01 9:39 ` Thomas Petazzoni
2016-03-03 13:56 ` Gustavo Zacarias
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=56CB83C8.3090500@gmail.com \
--to=romain.naour@gmail.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