413181 – media-sound/lilypond-2.14.2 fails to find Python.h

Bug 413181 - media-sound/lilypond-2.14.2 fails to find Python.h

Summary: media-sound/lilypond-2.14.2 fails to find Python.h

Status:	RESOLVED DUPLICATE of bug 415793

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Marijn Schouten (RETIRED)

URL:
Whiteboard:
Keywords:	PATCH

Depends on:
Blocks:

Reported:	2012-04-23 01:11 UTC by Reuben Martin
Modified:	2012-08-23 09:42 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Build Log (config.log,117.66 KB, text/plain) 2012-04-24 19:56 UTC, Reuben Martin	Details
emerge --info (emerge.info.txt,5.82 KB, text/plain) 2012-04-24 19:58 UTC, Reuben Martin	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Reuben Martin 2012-04-23 01:11:41 UTC

The config script for lilypond is not finding Python.h.  

Please fix by adding:

--with-python-include="$(python_get_includedir)"

to the econf section of the ebuild.


Reproducible: Always

Comment 1 Tim Harder gentoo-dev

2012-04-24 19:01:28 UTC

Please attach the build log and your emerge --info.

Comment 2 Reuben Martin 2012-04-24 19:56:36 UTC

Created attachment 309953 [details]
Build Log

Comment 3 Reuben Martin 2012-04-24 19:58:26 UTC

Created attachment 309955 [details]
emerge --info

Comment 4 Tim Harder gentoo-dev

2012-04-24 20:02:50 UTC

Your CFLAGS are a bit extreme when building lilypond. In particular, the -floop-strip option is causing the problem since it doesn't exist in the gcc version you're using.

Build lilypond with sane CFLAGS such as the ones in your attached emerge --info and it should work fine.

Comment 5 Tim Harder gentoo-dev

2012-04-24 20:06:50 UTC

(In reply to comment #4)
> Your CFLAGS are a bit extreme when building lilypond. In particular, the
> -floop-strip option is causing the problem since it doesn't exist in the gcc
> version you're using.
> 
> Build lilypond with sane CFLAGS such as the ones in your attached emerge
> --info and it should work fine.

Actually I guess those appear to be getting pulled from somewhere else.

Comment 6 Tim Harder gentoo-dev

2012-04-24 20:08:41 UTC

Namely, what does `python-config --cflags` output on your system?

Comment 7 Reuben Martin 2012-04-24 20:12:04 UTC

I have some flags in /etc/make.conf that are commented out, and that I only uses on a specific package. Perhaps I had those options turned on when I compiled python at some time. That looks to be where it is getting those build flags from.

Although -floop-strip is incorrect. If I built it with those options turned on it would be -floop-strip-mine.

I'll try rebuilding python with correct flags to see if that changes anything.

Comment 8 Reuben Martin 2012-04-24 20:15:14 UTC

Python config is:

-I/usr/include/python2.7 -I/usr/include/python2.7 -fno-strict-aliasing -O2 -march=native -mfpmath=sse -ftree-vectorize -fomit-frame-pointer -pipe -fprefetch-loop-arrays -floop-block -floop-strip-mine -floop-interchange -fwrapv -DNDEBUG

So I did apparently build it with those flags enabled. It would seem then that the flag string from python config is getting truncated somewhere.

Comment 9 Reuben Martin 2012-04-24 20:19:34 UTC

Rebuilding Python fixed it. Feel free to close. Thanks.

Comment 10 Cyprien Nicolas (fulax) 2012-08-23 09:42:08 UTC

This actually was a real bug which has been adressed in bug 415793

*** This bug has been marked as a duplicate of bug 415793 ***