Bug 7268

Created attachment 5486 [details]
buildroot configuration

Created attachment 5492 [details]
Make output

Hi,

if needed, here is the full make output (5MB, but 797MB uncompressed) :
http://dl.free.fr/eMphhZaBN

Thanks for the report, I've just started a build with your configuration to try to reproduce the problem.

The build of your .config works fine here (Debian GNU/Linux 6.0).

Ok, so the problem is due to the fact that for some reason in your case, Python has added "-I/usr/include/x86_64-linux-gnu" to the CFLAGS used when building target modules, which doesn't make sense. I don't have this flag added when building here, which explains why it works.

(In reply to comment #3)
> Hi,
> 
> if needed, here is the full make output (5MB, but 797MB uncompressed) :
> http://dl.free.fr/eMphhZaBN

Unfortunately, I'm not able to download it. Could you put it somewhere else?

Thanks.

Thanks for your reply

Here is the download link :
http://we.tl/vSYk0yUI5r

I forgot to say : my host is a Debian 7.5

I'll try to remove this flag tomorrow morning

Regards

Hi,

A few more details about this issue...

A git bisect identifies 7e960dc9 as the first "bad" commit : I manage to compile python using revision 577e52ac, but I do not using revision 7e960dc9.

7e960dc9da56d4a484b5480746aaf617ca491274 is the first bad commit
commit 7e960dc9da56d4a484b5480746aaf617ca491274
Author: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Date:   Thu Feb 13 21:48:53 2014 +0100

    python: bump to 2.7.6
    
    Even though jumping from 2.7.3 to 2.7.6 looks like a minor version
    bump, it is in fact a fairly significant one, because a good number of
    changes to help cross-compilation have been merged into Python
    upstream. Therefore, most of our patches are affected by this change.
    
    In detail, this commit:
    
     * Renames all the patches to follow the naming convention of patches
       in Buildroot: the patch file names should not have any version
       number.
    
     * The patches numbered above 100, that add configuration options to
       disable certain modules of the Python standard library, are only
       renamed and slightly adapted, they didn't change that much.
    
     * The patches numbered below 100 are almost entirely rewritten: many
       of the cross-compilation problems that used to exist in Python
       2.7.3 no longer exist, and the number of remaining problems is
       smaller, and can be fixed with smaller patches.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
    Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

:040000 040000 8618414254d7998096c5c87b7774cbd50217cb08 ddcec6a08dbe50e52973f7659789200593fe6861 M	package

Hi,

I finally got the bug. Your input about wrong paths really helped me and saved me a lot of time, thanks a lot for this.

In fact, the main setup.py script has a "add_multiarch_paths" function that adapts standard paths to multiarch requirements. For some reason, it adds host /usr/include/x86_64-linux-gnu to include paths for the target python build. 

I add a patch that makes multiarch management process available only if python is not being cross-compiled. I do not know if multiarch really makes sense in the case of buildroot. This patch fixes my compilation issue, but it may break something for a different architecture, so I hope someone with a lot more experience about python and buildroot architectures than me will read this patch.

Thanks a lot again
David

Created attachment 5504 [details]
manage multiarch paths only if not cross-compiling

David,

Your patch is reversed. ;-)

Care to send the patch to the list, please?

Thanks.

Patch for python posted at http://patchwork.ozlabs.org/patch/368000/, and patch for python3 posted at http://patchwork.ozlabs.org/patch/368001/.

Thanks a lot David for your bug report and investigation! Once the patches are merged by Peter, we'll mark this bug as fixed. Of course, it would be good if you could formally test the patches, and give your Tested-by on the patches if their work for you.

Hi Thomas,

I managed to compile python 2.7 and python 3 using your patches.

Please forgive me, I'm not familiar with the "Tested-by" thing... How would you do that ?

Thanks
David

(In reply to comment #14)
> Hi Thomas,
> 
> I managed to compile python 2.7 and python 3 using your patches.
> 
> Please forgive me, I'm not familiar with the "Tested-by" thing... How would you
> do that ?

You would have had to reply to the patches sent to the mailing list, and just add a line like:

Tested-by: John Doe <john.doe@foobar.org>

In the reply.

However, the patches have been committed now, so it's too late :-)

Python 2.x fixed in http://git.buildroot.net/buildroot/commit/?id=5476b7273f0e5e58b59da9bf6403366d08e6b585, and Python 3.x fixed in http://git.buildroot.net/buildroot/commit/?id=5364b22b6c309073d59f593c3b5b1a9b3246e957.

Closing bug.