| Summary: | media-libs/fontconfig-2.11.1-r1 - checking for scandir... configure: error: *** No scandir function available. // conftest.c:1:0: error: SSE instruction set disabled, using 387 arithmetics [-Werror] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | deterenkelt <deterenkelt.github> |
| Component: | Current packages | Assignee: | Gentoo Fonts Team <fonts> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | fonts, multilib+disabled |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
output of emerge --info =media-libs/fontconfig-2.11.1-r1::gentoo ebuild environment config.log |
||
Created attachment 391458 [details]
output of emerge --info =media-libs/fontconfig-2.11.1-r1::gentoo
Created attachment 391460 [details]
ebuild environment
...config.log is still missing. Created attachment 391470 [details]
config.log
Actually, the problem here is twofolds. It's a mix of quirky test and quirky CFLAGS. The test the upstream uses is a bit fragile and user's CFLAGS trigger a false negative, due to causing "warning: SSE instruction set disabled, using 387 arithmetics". No idea about why upstream appends -Werror on purpose after this change: http://cgit.freedesktop.org/fontconfig/commit/?id=8daa863c6d84ea56cc2f568a89316690e784a277 Looks like there is a reference at: http://comments.gmane.org/gmane.comp.fonts.fontconfig/4826 (In reply to Pacho Ramos from comment #6) > No idea about why upstream appends -Werror on purpose after this change: > http://cgit.freedesktop.org/fontconfig/commit/ > ?id=8daa863c6d84ea56cc2f568a89316690e784a277 > > Looks like there is a reference at: > http://comments.gmane.org/gmane.comp.fonts.fontconfig/4826 I can't tell about that particular commit, but as for the failing check that's quite obvious - incompatible function type in C is at most a warning and just about all standard autoconf C compiler warning checks are done via -Werror. I had this same error when building with- CFLAGS="-march=native -O2 -pipe -Wall -fpic -D_FORTIFY_SOURCE=1" removed -D_FORTIFY_SOURCE=1 and it builds and installs. (In reply to David J Cozatt from comment #8) using -fpic in global CFLAGS is a terrible idea and 100% not supported. it also makes no sense at all. |
Created attachment 391456 [details] build.log On configuring stage autoconf fails with the following error. checking for scandir... configure: error: *** No scandir function available.