From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-05
Date: Tue, 9 Aug 2016 12:03:37 +0200 [thread overview]
Message-ID: <20160809120337.1d10afe4@free-electrons.com> (raw)
In-Reply-To: <20160807114606.GJ22524@waldemar-brodkorb.de>
Hello,
On Sun, 7 Aug 2016 13:46:06 +0200, Waldemar Brodkorb wrote:
> > Waldemar: what about simply disabling C++ support in the Blackfin
> > internal toolchain support for 2016.08 ?
>
> Give me the next week to find a solution, otherwise we should
> disable it.
I see you mailed me about this, asking to disable C++ support for now
in Blackfin.
> > > m68k | cairo-1.14.6 | NOK | http://autobuild.buildroot.net/results/dc6b899e3e502d65b2cf2f6d922a4f63857edf82/
> >
> > relocation truncated to fit: R_68K_GOT16O
> >
> > I guess the mxgot hack could be used here as well? Waldemar?
>
> Yes. I can prepare a patch.
Patch committed.
> > > m68k | gnuplot-4.6.6 | NOK | http://autobuild.buildroot.net/results/d1e030c42f43f49575f36ecc82e9dd9018ca4f73/
> >
> > Again: relocation truncated to fit: R_68K_GOT16O
> >
> > Waldemar, we really have lots of packages that need the -mxgot flag.
> > Should we enable it globally?
>
> No, it will generate not so optimal code for all packages, I would
> rather like to fix all packages which require this workaround and
> might discuss, if this can be automatically used by gcc with the gcc
> developers.
I've committed your patch on gnuplot. Though I believe it would be nice
for gcc to have some kind of -mautoxgot option to tell "please use the
optimized mechanism if possible, and if not, fallback to the mxgot
mechanism".
> > > m68k | php-7.0.9 | NOK | http://autobuild.buildroot.net/results/754959831528764b5ed908b000c1e6d24a151c2c/
> >
> > /tmp/ccnMF6vi.s: Assembler messages:
> > /tmp/ccnMF6vi.s: Fatal error: Tried to convert PC relative branch to absolute jump
> >
> > Waldemar ?
>
> Depends, will php7 be available for BR2_STATIC_LIBS or not? If not I
> will just ignore it for now :)
Sadly for you, I just sent a minute ago a patch that fixes the build of
PHP on BR2_STATIC_LIBS configurations :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-09 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-05 Thomas Petazzoni
2016-08-07 9:26 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-07 11:46 ` Waldemar Brodkorb
2016-08-09 10:03 ` Thomas Petazzoni [this message]
2016-08-07 14:33 ` Frank Hunleth
2016-08-07 15:48 ` Samuel Martin
2016-08-09 14:15 ` Ben Boeckel
2016-08-17 21:18 ` Samuel Martin
2016-08-08 15:56 ` Vlad Zakharov
2016-08-08 20:34 ` Thomas Petazzoni
2016-08-11 10:43 ` Vlad Zakharov
2016-08-09 13:27 ` gwenhael.goavec
2016-08-09 13:41 ` 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=20160809120337.1d10afe4@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.