Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 321] New: alsa-lib uses host include files for python which breaks builds on 64 bit Linux
Date: Thu,  7 May 2009 08:36:14 +0000 (UTC)	[thread overview]
Message-ID: <bug-321-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=321

              Host: OpenSuse 11.1 64 bit on Core i7 processor
            Target: at91sam9261ek_defconfig
           Summary: alsa-lib uses host include files for python which breaks
                    builds on 64 bit Linux
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: ulf.samuelsson at atmel.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


at91sam9261ek_defconfig was updated to use the latest 
binutils, gcc, kernel headers etc, and this is yet
to be committed.

When you build alsa-lib, with python enabled, it tries to include some python
headers.
These are included from the host machine and not the target machine.

/home/ulf/projects/Buildroot/20090506/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc
-Os -pipe -Os 
-I/home/ulf/projects/Buildroot/20090506/buildroot/build_arm/staging_dir/usr/include
-I/home/ulf/projects/Buildroot/20090506/buildroot/build_arm/staging_dir/include
--sysroot=/home/ulf/projects/Buildroot/20090506/buildroot/build_arm/staging_dir/
-isysroot /home/ulf/projects/Buildroot/20090506/buildroot/build_arm/staging_dir
-mabi=apcs-gnu -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-shared  .libs/sbase.o  -Wl,--rpath
-Wl,/home/ulf/projects/Buildroot/20090506/buildroot/build_arm/alsa-lib-1.0.18/src/.libs
-L/home/ulf/projects/Buildroot/20090506/buildroot/build_arm/staging_dir/lib
-L/home/ulf/projects/Buildroot/20090506/buildroot/build_arm/staging_dir/usr/lib
-lm ../../../src/.libs/libasound.so  -mabi=apcs-gnu -mabi=apcs-gnu -Wl,-soname
-Wl,smixer-sbase.so -o .libs/smixer-sbase.so
In file included from /usr/include/python2.6/Python.h:58,
                 from python.c:22:
/usr/include/python2.6/pyport.h:685:2: error: #error "LONG_BIT definition
appears wrong for platform (bad gcc/glibc config?)."


Since the host is 64 bit and the target is 32 bit, the check fails.
It would not fail the test if the host is running 32 bit Linux.
The real problem (using host includes) still exist and can cause subtle bugs


This was also reported to the mailing list by Matt Wood 
Dec 19, 2008; 07:48pm.


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-05-07  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  8:36 bugzilla at busybox.net [this message]
2009-07-26  7:15 ` [Buildroot] [Bug 321] alsa-lib uses host include files for python which breaks builds on 64 bit Linux bugzilla at busybox.net
2010-02-21 18:51 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-07-19  7:02 ` bugzilla at busybox.net

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=bug-321-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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