Opened 6 months ago
Last modified 6 months ago
#69864 assigned defect
poppler: Failed to configure poppler: Invalid value for configure.compiler:
Reported by: | rmottola (Riccardo) | Owned by: | dbevans (David B. Evans) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.3 |
Keywords: | snowleopard | Cc: | mascguy (Christopher Nielsen) |
Port: | poppler |
Description
On 10.6 Snow Leopard 386,
:error:configure Failed to configure poppler: Invalid value for configure.compiler: :debug:configure Error code: NONE :debug:configure Backtrace: Invalid value for configure.compiler: :debug:configure while executing
I can't see what value is actually used in the log
Attachments (1)
Change History (10)
Changed 6 months ago by rmottola (Riccardo)
Attachment: | poppler.log added |
---|
comment:1 Changed 6 months ago by rmottola (Riccardo)
comment:2 Changed 6 months ago by rmottola (Riccardo)
forcing gcc12 instead also continues build, but fails with undefined symbols
Undefined symbols for architecture i386: "__ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE6insertEjPKcj", referenced from: __ZN9GooString20prependUnicodeMarkerEv in GooString.cc.o __ZN4Dict16findAvailableKeyERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEE in Dict.cc.o __ZN9FormField21getFullyQualifiedNameEv in Form.cc.o __ZN9GooString6insertEiPKS_.isra.0 in PSOutputDev.cc.o "__ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE6appendEPKcj", referenced from: __ZN9GooString8appendfvEPKcPc in GooString.cc.o __ZNK10FoFiType1C6cvtNumEdbP9GooString.constprop.0 in FoFiType1C.cc.o __ZNK10FoFiType1C6cvtNumEdbP9GooString in FoFiType1C.cc.o __ZN22AnnotAppearanceBuilder11drawListBoxEPK15FormFieldChoicePK11AnnotBorderPK12PDFRectanglePK9GooStringPK12GfxResources20VariableTextQuaddingP4XRefP4Dict in Annot.cc.o __ZL17drawMultiLineTextRK9GooStringdPK4FormRK7GfxFontRKNSt3__112basic_stringIcNS8_11char_traitsIcEENS8_9allocatorIcEEEEd20VariableTextQuaddingd in Annot.cc.o __ZN9GooString6appendERKNSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEE in Annot.cc.o __ZNK5Array9getStringEiP9GooString in Array.cc.o ... "__ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE6resizeEjc", referenced from: __ZNSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE8overflowEi in gbase64.cc.o __Z22timeToStringWithFormatPKlPKc in DateInfo.cc.o __ZNSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE8overflowEi in PDFDoc.cc.o "__ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEE6__initEPKcj", referenced from: __Z9gbasenamePKc in gbasename.cc.o __Z8openFilePKcS0_ in gfile.cc.o __ZN9GooStringC4EPKc in gfile.cc.o __ZN12_GLOBAL__N_114grandom_engineEv in grandom.cc.o __ZNK12FoFiTrueType14convertToType0EPKcPiibS2_PFvPvS1_mES3_ in FoFiTrueType.cc.o __ZNK12FoFiTrueType12mapNameToGIDEPKc in FoFiTrueType.cc.o __ZN12FoFiTrueType13readPostTableEv in FoFiTrueType.cc.o ...
so well, the default compiler selection goes bad.
comment:3 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | mascguy added |
---|---|
Keywords: | i386 removed |
Owner: | set to dbevans |
Status: | new → assigned |
Summary: | poppler fails to configure compiler on 10.6 Snow Leopard → poppler: Failed to configure poppler: Invalid value for configure.compiler: |
Version: | → 2.9.3 |
Replying to rmottola:
:error:configure Failed to configure poppler: Invalid value for configure.compiler:
I can't see what value is actually used in the log
The value actually used was none. The empty string. MacPorts believed that no compiler that satisfied the requirements of the Portfile, specifically C++20 compatibility. According to the code, that should require Apple clang 15 or llvm.org clang 16 or gcc 12 or later. Not sure why it doesn't select clang 16 on Snow Leopard. We see the same failure on the i386 and x86_64 Snow Leopard buildbot machines.
comment:4 follow-up: 5 Changed 6 months ago by rmottola (Riccardo)
Aha, I understand. I have only MP gcc12 but MP clang 11,14,15,16, so it should have been able to select something existing.
then the errors show that it is not enough, but that is not C++20 compatibility perhaps but another issue.. I am unsure about those missing symbols.
comment:5 follow-up: 6 Changed 6 months ago by ryandesign (Ryan Carsten Schmidt)
Replying to rmottola:
Aha, I understand. I have only MP gcc12 but MP clang 11,14,15,16, so it should have been able to select something existing.
MacPorts compiler selection is not based on what ports you already have installed.
comment:6 Changed 6 months ago by rmottola (Riccardo)
Replying to ryandesign:
MacPorts compiler selection is not based on what ports you already have installed.
in case it would just pull-in the missing compiler, right? But it is a proof that on this platform these compilers were available.
comment:7 Changed 6 months ago by kencu (Ken)
comment:8 follow-up: 9 Changed 6 months ago by kencu (Ken)
somebody needs to re-look at what clang compilers can be made available on 10.6.
I’ve been using clang-15 in my ports tree fork, but I can get away with that because I use ld-latest as my (manually-upgraded) linker, I believe.
comment:9 Changed 6 months ago by rmottola (Riccardo)
Replying to kencu:
somebody needs to re-look at what clang compilers can be made available on 10.6.
I’ve been using clang-15 in my ports tree fork, but I can get away with that because I use ld-latest as my (manually-upgraded) linker, I believe.
could I have a linker issue then seen here in my issue above?
If I force clang16:
build fails with linking. I suppose a C++ library issue (minimum libgcc8?), but it proves that with a set compiler things move on.