NetBSD Problem Report #49992

From www@NetBSD.org  Mon Jun 22 05:40:50 2015
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 74EEEA65C8
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 22 Jun 2015 05:40:50 +0000 (UTC)
Message-Id: <20150622054049.42800A65E0@mollari.NetBSD.org>
Date: Mon, 22 Jun 2015 05:40:49 +0000 (UTC)
From: bnjf+netbsd@bnjf.id.au
Reply-To: bnjf+netbsd@bnjf.id.au
To: gnats-bugs@NetBSD.org
Subject: devel/libexecinfo fails to build
X-Send-Pr-Version: www-1.0

>Number:         49992
>Category:       pkg
>Synopsis:       devel/libexecinfo fails to build
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    bsiegert
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 22 05:45:00 +0000 2015
>Closed-Date:    Mon Jul 13 05:06:15 +0000 2015
>Last-Modified:  Mon Jul 13 05:06:15 +0000 2015
>Originator:     Brad Forschinger
>Release:        2015Q1
>Organization:
>Environment:
SunOS x 5.10 Generic_147147-26 sun4v sparc sun4v
>Description:

Will fail using PKGSRC_COMPILER=sunpro due to the package's use of __builtin_frame_address 

After switching to PKGSRC_COMPILER=gcc build fails due to unknown tag


>How-To-Repeat:

cd devel/libexecinfo && bmake
>Fix:

help libtool with a --tag

diff --git a/devel/libexecinfo/Makefile b/devel/libexecinfo/Makefile
index 966ebe0..43eeeb8 100644
--- a/devel/libexecinfo/Makefile
+++ b/devel/libexecinfo/Makefile
@@ -21,9 +21,9 @@ USE_LIBTOOL=          yes
 INSTALLATION_DIRS=     include lib

 do-build:
-   cd ${WRKSRC} && ${LIBTOOL} --mode=compile ${CC} ${CFLAGS} -c execinfo.c
-   cd ${WRKSRC} && ${LIBTOOL} --mode=compile ${CC} ${CFLAGS} -c stacktraverse.c
-   cd ${WRKSRC} && ${LIBTOOL} --mode=link ${CC} ${LDFLAGS} ${LIBS} \
+ cd ${WRKSRC} && ${LIBTOOL} --mode=compile --tag=CC ${CC} ${CFLAGS} -c execinfo.c
+ cd ${WRKSRC} && ${LIBTOOL} --mode=compile --tag=CC ${CC} ${CFLAGS} -c stacktraverse.c
+ cd ${WRKSRC} && ${LIBTOOL} --mode=link --tag=CC ${CC} ${LDFLAGS} ${LIBS}    \
                -o libexecinfo.la execinfo.lo stacktraverse.lo          \
                -version-info 1:0:0 -rpath ${PREFIX}/lib


>Release-Note:

>Audit-Trail:
From: Thomas Klausner <wiz@NetBSD.org>
To: NetBSD bugtracking <gnats-bugs@NetBSD.org>
Cc: 
Subject: Re: pkg/49992: devel/libexecinfo fails to build
Date: Mon, 22 Jun 2015 10:16:32 +0200

 On Mon, Jun 22, 2015 at 05:45:00AM +0000, bnjf+netbsd@bnjf.id.au 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?
  Thomas

From: Brad Forschinger <bnjf@bnjf.id.au>
To: gnats-bugs@netbsd.org
Cc: pkg-manager@netbsd.org, gnats-admin@netbsd.org, pkgsrc-bugs@netbsd.org, 
	bnjf+netbsd@bnjf.id.au
Subject: Re: pkg/49992: devel/libexecinfo fails to build
Date: Mon, 22 Jun 2015 18:42:39 +1000

 On Mon, Jun 22, 2015 at 6:20 PM, Thomas Klausner <wiz@netbsd.org> wrote:
 >  On Mon, Jun 22, 2015 at 05:45:00AM +0000, bnjf+netbsd@bnjf.id.au 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=?

 Brad

Responsible-Changed-From-To: pkg-manager->ober
Responsible-Changed-By: bsiegert@NetBSD.org
Responsible-Changed-When: Sun, 28 Jun 2015 14:52:47 +0000
Responsible-Changed-Why:
Over to maintainer.


Responsible-Changed-From-To: ober->pkg-manager
Responsible-Changed-By: wiz@NetBSD.org
Responsible-Changed-When: Sun, 28 Jun 2015 15:15:49 +0000
Responsible-Changed-Why:
ober has no commit bit.


From: David Holland <dholland-pbugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/49992: devel/libexecinfo fails to build
Date: Sun, 28 Jun 2015 19:58:52 +0000

 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> wrote:
  >  >  On Mon, Jun 22, 2015 at 05:45:00AM +0000, bnjf+netbsd@bnjf.id.au 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.

 -- 
 David A. Holland
 dholland@netbsd.org

From: Brad Forschinger <bnjf@bnjf.id.au>
To: gnats-bugs@netbsd.org
Cc: pkg-manager@netbsd.org, gnats-admin@netbsd.org, pkgsrc-bugs@netbsd.org, 
	bnjf+netbsd@bnjf.id.au
Subject: Re: pkg/49992: devel/libexecinfo fails to build
Date: Mon, 29 Jun 2015 10:01:29 +1000

 On Mon, Jun 29, 2015 at 6:00 AM, David Holland
 <dholland-pbugs@netbsd.org> 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> wrote:
 >   >  >  On Mon, Jun 22, 2015 at 05:45:00AM +0000, bnjf+netbsd@bnjf.id.au 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

From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: gnats-bugs@NetBSD.org
Cc: pkg-manager@netbsd.org, gnats-admin@netbsd.org, pkgsrc-bugs@netbsd.org,
	bnjf+netbsd@bnjf.id.au
Subject: Re: pkg/49992: devel/libexecinfo fails to build
Date: Mon, 29 Jun 2015 14:44:58 +0200

 On Mon, Jun 29, 2015 at 12:05:00AM +0000, Brad Forschinger wrote:
 >  So maybe it's not so bad explicitly giving --tag=?

 There are some cases where it helps, but sunpro and gcc have quite
 different options, so it is really asking for trouble.

 Joerg

From: "Benny Siegert" <bsiegert@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/49992 CVS commit: pkgsrc/devel/libexecinfo
Date: Mon, 13 Jul 2015 04:55:31 +0000

 Module Name:	pkgsrc
 Committed By:	bsiegert
 Date:		Mon Jul 13 04:55:31 UTC 2015

 Modified Files:
 	pkgsrc/devel/libexecinfo: Makefile

 Log Message:
 Add tags to libtool invocation. From Brad Forschinger in PR pkg/49992.


 To generate a diff of this commit:
 cvs rdiff -u -r1.7 -r1.8 pkgsrc/devel/libexecinfo/Makefile

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

Responsible-Changed-From-To: pkg-manager->bsiegert
Responsible-Changed-By: bsiegert@NetBSD.org
Responsible-Changed-When: Mon, 13 Jul 2015 05:06:15 +0000
Responsible-Changed-Why:


State-Changed-From-To: open->closed
State-Changed-By: bsiegert@NetBSD.org
State-Changed-When: Mon, 13 Jul 2015 05:06:15 +0000
State-Changed-Why:
Applied patch.


>Unformatted:

Home	PR Database Search