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] luajit package fails to build on x86_64 for x86
Date: Fri, 7 Mar 2014 18:49:03 +0100	[thread overview]
Message-ID: <20140307174903.GE3384@free.fr> (raw)
In-Reply-To: <CAHkwnC92VGYqeUSNsAiyuFQgErZtLwYyFJ89qa8bYrAoZ8mRkw@mail.gmail.com>

Fabio, All,

On 2014-03-07 18:32 +0100, Fabio Porcedda spake thusly:
> On Fri, Mar 7, 2014 at 6:21 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Fabio, All,
> >
> > On 2014-03-07 10:59 +0100, Fabio Porcedda spake thusly:
> >> On Thu, Mar 6, 2014 at 10:31 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> >> > On 2014-03-06 11:43 +0100, Fabio Porcedda spake thusly:
> >> >> Hi all,
> >> >> luajit fails to build on a Ubuntu 13.10 x86_64 with the following defconfig:
> >> >>
> >> >> BR2_x86_generic=y
> >> >> BR2_TOOLCHAIN_EXTERNAL=y
> >> >> BR2_PACKAGE_LUAJIT=y
> > [--SNIP--]
> >> > And this can not work on a pure 64-bit system (aka, without the 32-bit
> >> > legacy stuff).
> > [--SNIP--]
> >> > Not sure how we can get away with this...
> >>
> >> I think we have two choices:
> >>  - add a check to test if 32bit compiler is installed and if not print
> >> a clear message about the toolchain requirement
> >
> > I think this would be the first package to add such a check.
> >
> > How would you propose we implement this:
> >   - in a pre-configure hook (but that will catch the failure late in the
> >     build) ?
> >   - in a make ifeq-block (so we can catch it early in the build) ?
> 
> > The second solution is more appealing to me, but might be a bit more
> > complex to implement.
> 
> I think a check to be added like this:
> 
> luakit.mk:
> 
> luajit-dependencies:
>    shell script to check and if it fails it prints an appropriate
> message and stop the building
> 
> dependencies: luajit-dependencies
> 
> So the check it's done early at same time as other dependenies check.

Doing the check in dependencies is not much better than doing it as a
pre-configure hook: it can be delayed quite late in the build process.

> Right now i don't know how to check about the presence of the 32bit
> support on the 64 bit host toolchain.

What about something like this:

    ifeq ($(BR2_PACKAGE_LUAJIT),y)
    ifeq ($(TARGET_32BIT)$(HOST_64BIT),yy)
    ifneq ($(shell echo 'int main() { return 0; }' |gcc -m32 -o foo -x c - >/dev/null 2>&1 && echo y; rm -f foo),y)
    $(error Can't build luajit for 32-bit target on this machine (mising 32-bit development packages))
    endif
    endif
    endif

Not really trivial, but should work with some tweaking...

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:[~2014-03-07 17:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 10:43 [Buildroot] luajit package fails to build on x86_64 for x86 Fabio Porcedda
2014-03-06 20:51 ` François Perrad
2014-03-07 10:19   ` Fabio Porcedda
2014-03-06 21:31 ` Yann E. MORIN
2014-03-07  9:59   ` Fabio Porcedda
2014-03-07 17:21     ` Yann E. MORIN
2014-03-07 17:32       ` Fabio Porcedda
2014-03-07 17:49         ` Yann E. MORIN [this message]
2014-03-07 19:40           ` Thomas Petazzoni
2014-03-07 20:37             ` Fabio Porcedda
2014-03-07 20:46               ` Thomas Petazzoni
2014-03-07 20:51                 ` Fabio Porcedda
2014-03-07 20:58                   ` Thomas Petazzoni
2014-03-07 21:11                     ` Fabio Porcedda
2014-03-07 21:30                       ` Thomas Petazzoni
2014-03-07 21:58                         ` Fabio Porcedda
2014-03-07 22:19                           ` Fabio Porcedda
2014-03-07 21:38             ` Yann E. MORIN

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=20140307174903.GE3384@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