Re: Issues with Unix Linking -- Want to modify build command for custom toolchain

Rene Rivera via Boost-build <[email protected]> Tue, 4 Jun 2019 07:09:08 -0500
Newsgroups gmane.comp.lib.boost.build
Message-ID <CAHEh_GjtPW=T4hWxy79vtxYnEVxnE1DWLHpcjk+6a47vYJGgxQ@mail.gmail.com>
First, thank you for using B2 :-) Second, we're going to need a bit more
info to help you out. Can you tell us what version of B2 you are using? Do
you have a minimal sample project that replicates the issue? What's in your
config files? Can you provide that custom toolset? etc.

On Tue, Jun 4, 2019 at 6:31 AM codex653 via Boost-build <
[email protected]> wrote:

> What I am trying (and miserably failing) to do is add the -Wl,--start-group
> flag /before/ all the libraries I just compiled for my project are given to
> the linker. For example, if I use the <link-flags> property, boost.build
> will give me this kind of output:
>
> <my-linker-executable> -o <output-location> <list-of-all-my-libs>
> -Wl,--start-group <other-linked-libs> <rest-of-link-flags> ....and so on.
>

That is rather strange. Since from what I can tell B2 should already be
putting the `-Wl,--start-group` at the front of all libraries (both built
and externally searched) <
https://github.com/boostorg/build/blob/develop/src/tools/gcc.jam#L1094>

What I am trying to do is this:
>
> <my-linker-executable> -o <output-location> -Wl,--start-group
> <list-of-all-my-libs>  <other-linked-libs> <rest-of-link-flags> ....
>

Indeed.


-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build