Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-08-16
Date: Tue, 20 Aug 2013 00:06:44 +0200	[thread overview]
Message-ID: <20130819220644.GA3595@free.fr> (raw)
In-Reply-To: <20130818200133.4046034b@skate>

Thomas, All,

On 2013-08-18 20:01 +0200, Thomas Petazzoni spake thusly:
> On Sat, 17 Aug 2013 08:30:05 +0200 (CEST), Thomas Petazzoni wrote:
> 
> >        arm |                   libbsd-0.4.2 | NOK | http://autobuild.buildroot.net/results/40f3be947e5d686bb4e016db1b3bf59503237e62/
> >        arm |                   libbsd-0.4.2 | NOK | http://autobuild.buildroot.net/results/ad9d92bef3655ca279bfd6184dca0457ee6c94a0/
> 
> Could you have a look at those two? In commit
> 29b071077f66de1d9a257e7c5c6983dcce1fc65d, you've added "depends on" to
> make sure libbsd only gets built on architectures that provide a.out.h.
> However, here, we are on ARM, and apparently, a.out.h is not available.

This Buildroot .config uses Linux 3.10.7 for the headers.

Support for a.out on ARM has been removed in acfdd4b, but this is
scheduled for 3.11. 3.10 still had support for a.out.

Currently the only archs that still have support for a.out in Linux
are: um, m68k, x86 and alpha. Of those, only x86 is meaningfull to
Buildroot.

So, I think I won't even try to fix this, and simply depend on
i386 || x86_64.

As far as I am concerned, I use it in my qemu-on-target patchset, and I
only expect to run this on x86_64 anyway.

We could patch-away the single user of a.out: src/nlist.c .
It seems it would be relatively easy to remove a.out support from
nlist.c, since there is conditional code guarded by:
    #ifdef  _NLIST_DO_AOUT
    blabla
    #endif

which is defined by:
    #if !defined(__NO_A_OUT_SUPPORT)
    #define _NLIST_DO_AOUT
    #endif

But nothing sets __NO_A_OUT_SUPPORT.

The only thing that is properly guarded by _NLIST_DO_AOUT is the
inclusion of a.out.h, but is easy to do.

So, maybe we should pass __NO_A_OUT_SUPPORT in CPPFLAGS to ./configure

Is it really important that this be buildable on !x86 at all?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-08-19 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-08-16 Thomas Petazzoni
2013-08-18 18:01 ` Thomas Petazzoni
2013-08-19 22:06   ` Yann E. MORIN [this message]
2013-08-19 22:21     ` 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=20130819220644.GA3595@free.fr \
    --to=yann.morin.1998@free.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