➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mhpruitt
Recipients Alex.Willmer, doko, mhpruitt, pmpp, rbelio, yan12125, zach.ware
Date 2018-08-11.23:10:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1534029028.82.0.56676864532.issue31710@psf.upfronthosting.co.za>
In-reply-to
Content 
Also ran into this issue while building Python in an isolated environment.  Realized that libffi is installing into the $EPREFIX/lib64 directory of our build environment.

Despite pkg-config returning the correct directory for linking libffi, it took explicitly setting LDFLAGS to the correct lib64 directory in my build process for the Python build to succeed.

I noticed from your build.log that you don't explicitly add your lib64 to your LDFLAGS.  Perhaps give that a shot?
History
Date User Action Args
2018-08-11 23:10:28mhpruittsetrecipients: + mhpruitt, doko, pmpp, zach.ware, Alex.Willmer, yan12125, rbelio
2018-08-11 23:10:28mhpruittsetmessageid: <1534029028.82.0.56676864532.issue31710@psf.upfronthosting.co.za>
2018-08-11 23:10:28mhpruittlinkissue31710 messages
2018-08-11 23:10:28mhpruittcreate