Hi! Julien Lepiller <[email protected]> skribis:
> Le 15 décembre 2022 15:34:02 GMT+01:00, "Ludovic Courtès" <[email protected]> a > écrit : >>> (outputs '("out" ;commands, etc. (60+ MiB) >>> - "lib" ;libgcc_s, libgomp, etc. (15+ >>> MiB) >>> + "shared-lib" ;libgcc_s, libgomp, etc. (5+ >>> MiB) >>> + "static-lib" ;object code libraries and >>> internal data files of GCC. (10+ MiB) >> >>The convention is to use “lib” for shared libraries and “static” for >>static libraries. > > But using lib introduces a --libdir argument which is used to install static > libs… I see. Then maybe we should override the ‘configure’ phase, or repeat ‘--libdir’ in the hope that the second one wins? >>Is libgomp in “lib”? Is it found when linking with ‘-fopenmp’? > > Well, shared-lib should be renaimed into libgcc, because it's the only > library there. OK. > Libgomp amd all other libs are in static-lib (which is not well named either > ^^'). It will be found I think but not tested (it find libstdc++ in the same > directory). Heh. :-) I think it would be great to have all the .a in a separate output. Thanks, Ludo’.
