-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ticcutils fails to build against new libicu 75 because -std=c++14 is too old #29
Comments
Seeing this error for the conda build of ticcutils as well: https://github.com/conda-forge/ticcutils-feedstock/pull/34/checks?check_run_id=27458299416 |
Well, I can update the software stack to generally use -std=c++17 This however leads to problems with the MacOS runners for GitHub actions. (as usual)
I currently have no clue how to solve this, -licuio IS in the build libs nevertheless, it would be nice if you all could test the builds on Arch Linux and Conda |
Well, probably this due to a mixup between libC++ (clang style, default on MacOS) and libstdc++ (Gnu style, deprecated on MacOS)
And the linker searches for :
There seems no easy way to solve this |
see: this test which quick and dirty shows the pain |
Still seeing the error in a new PR conda-forge/ticcutils-feedstock#35. @kosloot in your snippets I see |
@egpbos those snippets were to illustrate why building on MacOS using gcc is failing. |
Ah, that's great (the conda-forge build picked up the previous release still)! Do you plan on making a new versioned release for this soon? |
Well, let's say soonish. a few weeks max |
@egpbos a new version of Ticcutils is released. |
Thanks for the headsup! |
On my system (Arch Linux), ticcutils and everything else in the stack refuses to compile because
-std=c++14
is set (by us? by autotools?) and the icu headers no longer compile with that but require at least-std=c++17
.The work around is to just set
export CXXFLAGS="-std=c++17"
before./configure
, but I guess the autoconf process should have figured this out themselves.The text was updated successfully, but these errors were encountered: