-
Notifications
You must be signed in to change notification settings - Fork 0
GCC package profiles do not set LD_LIBRARY_PATH
#193
Comments
Merged
pmenzel
added a commit
that referenced
this issue
May 14, 2022
The build currently fails with the GCC 11.1.0 package, [as its profile does not set `LD_LIBRARY_PATH`][1]. [1]: #193
I always forget the rules, if editing profiles is allowed or not. |
"The Pirate Code is more what you call guidelines than actual rules" In fact, if all C+ compiled programs will trigger the automount of the gcc package they were build with, we should avoid to have to many of those. So maybe in this case... |
I edited all the profiles besides gcc-5.5.0-1, already containing that line.
|
pmenzel
added a commit
that referenced
this issue
May 23, 2022
C++ programs often need the libraries, so add them to the profile. LLVM/clang already does that. The existing profiles have been updated after the build, so also add the line to the build script of the newest GCC release in the tree, so it’ won’t be forgotten. Resolves: #193
pmenzel
added a commit
that referenced
this issue
May 23, 2022
The build currently fails with the GCC 11.1.0 package, [as its profile does not set `LD_LIBRARY_PATH`][1]. [1]: #193
Sign in
to join this conversation on GitHub.
GCC:
pkg-scripts/gcc-11.1.0-0.build.sh
Lines 27 to 30 in c944797
LLVM:
pkg-scripts/llvm-13.0.1-0.build.sh
Lines 22 to 26 in c944797
The text was updated successfully, but these errors were encountered: