Re: GCC Tool breaks linker for explicitly named libraries
Bill Deegan <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Message-ID | <CAEyG4CEo5ss6rzD+fnV-mKW9XJZttXV=z+PhAnFATy7HMWSqmQ@mail.gmail.com> |
Steve, When you say add, I'm assuming you mean they added that string to LIBS ? You'll need to provide a bit more info to provide a reasonable solution. Do other libraries in LIBS depend on the contents of libfoo.a? or only the object files also listed? -Bill On Fri, Dec 17, 2021 at 8:03 AM Steve Hill (Wireless) via Scons-users < [email protected]> wrote: > Hi, > > > > We’ve had someone add a library as “:libfoo.a” to force the (GCC) linker > to link against exactly “libfoo.a” and ignore “libfoo.so”. Unfortunately, > when they add this, _stripixes removes the “.a” and passes “-l:libfoo” to > the linker. Since a library with the exact name “libfoo” doesn’t exist, the > link fails. If they add the library as “:libfoo.a.a”, _stipixes removes one > (and only one) “.a”, leaving “-l:libfoo.a” and the link completes > successfully. > > > > Is this a bug or is there a workaround for this use-case? > > > > Thanks, > > > > Steve. > _______________________________________________ > Scons-users mailing list > [email protected] > https://pairlist4.pair.net/mailman/listinfo/scons-users > _______________________________________________ Scons-users mailing list [email protected] https://pairlist4.pair.net/mailman/listinfo/scons-users