On Wednesday, 3 March 2021 19:20, Marc Espie wrote:
> On Wed, Mar 03, 2021 at 06:10:22PM +, Bob wrote:
>
> > Does that -L/usr/lib really need to be in the leading position???
>
> I have zero idea how to do that purely in specs. Have fun tinkering.
>
> This is probably something we'll adopt but
On Wednesday, 3 March 2021 16:21, Marc Espie wrote:
> Do you have some actual reason to use gcc for that project instead of
> clang ?...
...
> But again: why gcc ?
Hi Marc,
Thank you very much for responding.
I am in a special code project that is centered around unique GCC
features and I can a
On Wed, Mar 03, 2021 at 06:10:22PM +, Bob wrote:
> Does that -L/usr/lib really need to be in the leading position???
I have zero idea how to do that purely in specs. Have fun tinkering.
This is probably something we'll adopt but low priority.
> * Where is GCC's default specs file say fo
Do you have some actual reason to use gcc for that project instead of
clang ?...
as far as -L goes you've got a lot of choices, between linking directly to
the .so, linking with --nostdlib and putting back the pieces manually.
it's been a long time since I've last looked at gcc, we've moved to
Hi Stuart and Marc,
Thanks a lot for responding.
Debugging the problem brought me to realize that GCC (both bundled
gcc/g++ and the egcc/eg++ port) adds a "-L/usr/lib" argument *in the
leading position* to LD.
Example:
$ echo "int main(){}">t.c; gcc -c -o t.o t.c; gcc -o t t.o -LMYDIRTEST -Wl,-
5 matches
Mail list logo
