Re: pkg/49992: devel/libexecinfo fails to build

[Brad Forschinger <bnjf%bnjf.id.au@localhost>]

On Mon, Jun 29, 2015 at 6:00 AM, David Holland
<dholland-pbugs%netbsd.org@localhost> wrote:
>  On Mon, Jun 22, 2015 at 08:45:00AM +0000, Brad Forschinger wrote:
>   >  On Mon, Jun 22, 2015 at 6:20 PM, Thomas Klausner <wiz%netbsd.org@localhost> wrote:
>   >  >  On Mon, Jun 22, 2015 at 05:45:00AM +0000, bnjf+netbsd%bnjf.id.au@localhost wrote:
>   >  >  > After switching to PKGSRC_COMPILER=gcc build fails due to unknown tag
>   >  >
>   >  >  When you switch, you have to rebuild and reinstall libtool -- I guess
>   >  >  you didn't do that?
>   >
>   >  Yep, I only switched to use gcc to build that package because libexecinfo is
>   >  gcc only.  Does it hurt explicitly having --tag=?
>
>  Not as such, but... who knows what else in libtool might be wired
>  incorrectly if you change the compiler under it.
>
>  I agree that the situation is unsatsifactory, but I'm not sure it's
>  easily fixable.

>From https://www.gnu.org/software/libtool/manual/libtool.html#Tags

"The tag can also be specified using libtool's --tag=tag option (see
Invoking
libtool). It is a good idea to do so in Makefile rules, because that
will allow
users to substitute the compiler without relying on libtool inference
heuristics. When no tag is specified, libtool will default to CC; this
tag
always exists."

So maybe it's not so bad explicitly giving --tag=?

Brad