Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 410877 - sys-devel/libtool:2 - some epunt_cxx nitpicking
Summary: sys-devel/libtool:2 - some epunt_cxx nitpicking
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2012-04-05 12:56 UTC by Greg Turner
Modified: 2012-04-09 00:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
epunt better in sys-devel/libtool:2 ebuilds (libtool-epunt-fix.patch,513 bytes, patch)
2012-04-05 12:57 UTC, Greg Turner
Details | Diff
Possible substitute patch for epunt_cxx (libtool-2.4.2-epunt_cxx.patch,7.21 KB, patch)
2012-04-05 14:22 UTC, Greg Turner
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Turner 2012-04-05 12:56:35 UTC
In && ( sys-devel/libtool:2 <sys-devel/libtool-2.4.2), we call epunt_cxx before eautoreconf.  Either epunt_cxx should patch configure.{ac,in} or it should always be called after autoconf (my inner gung-ho-child says to create some qa thingy for this -- but maybe time better spent fixing epunt_cxx to patch {ac,in}).

In =sys-devel/libtool-2.4.2, epunt_cxx is already "too old" and so does nothing but generate a .rej file -- note that arguably that's an epunt_cxx bug that should be fixed, and therefore not a problem with libtool-2.4.2.ebuild.  Here my inner gung-ho-child has some ideas but this is the wrong bug for them, so... judgement call to be made here in the interim

One other note.  tests/tagdemo /does/ contain c++!  That's really gross because epunt_cxx is pretty much an all-or-nothing proposition (it always recurses and patches every configure under "foo" even if we provide a "foo" directory argument).  If I'm not mistaken, this means we should do "use test || epunt_cxx".



-gmt

Reproducible: Always

Steps to Reproduce:
ebuild prepare
Actual Results:  
not punt all of the time

Expected Results:  
do punt some of the time
Comment 1 Greg Turner 2012-04-05 12:57:38 UTC
Created attachment 307887 [details, diff]
epunt better in sys-devel/libtool:2 ebuilds
Comment 2 Greg Turner 2012-04-05 14:22:14 UTC
Created attachment 307905 [details, diff]
Possible substitute patch for epunt_cxx

The attached could in theory be used in lieu of epunt_cxx; however it's probably better to fix epunt_cxx to intelligently handle the new configure gobbledeygook than create patches like this (so I wouldn't use it unless I trusted myself to remember to put epunt_cxx back once it got fixed).
Comment 3 Greg Turner 2012-04-05 16:45:08 UTC
(In reply to comment #2)
> Created attachment 307905 [details, diff] [details, diff]
> Possible substitute patch for epunt_cxx
> 
> The attached could in theory be used in lieu of epunt_cxx; however it's
> probably better to fix epunt_cxx to intelligently handle the new configure
> gobbledeygook than create patches like this (so I wouldn't use it unless I
> trusted myself to remember to put epunt_cxx back once it got fixed).

to be clear, the above only pertains to libtool-2.4.2.ebuild -- epunt_cxx is fine in libtool-2.4-r4.ebuild.
Comment 4 Greg Turner 2012-04-05 16:54:26 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Created attachment 307905 [details, diff] [details, diff] [details, diff]
> > Possible substitute patch for epunt_cxx
> > 
> > The attached could in theory be used in lieu of epunt_cxx; however it's
> > probably better to fix epunt_cxx to intelligently handle the new configure
> > gobbledeygook than create patches like this (so I wouldn't use it unless I
> > trusted myself to remember to put epunt_cxx back once it got fixed).
> 
> to be clear, the above only pertains to libtool-2.4.2.ebuild -- epunt_cxx is
> fine in libtool-2.4-r4.ebuild.

Sorry.  To be even clearer: attachment 307887 [details, diff] applies to all libtool-2.4*.ebuild files including 2.4.2.  Attachment 307905 [details, diff] applies only to libtool-2.4.2 and would serve as a replacement for epunt_cxx in that ebuild, after attachment 307887 [details, diff] was applied to the ebuild, i.e., by replacing "use test || epunt_cxx" with:

use test || epatch "${FILESDIR}"/2.4/${PN}-${PV}-epunt_cxx.patch

at the end of prepare()
Comment 5 Greg Turner 2012-04-06 11:15:17 UTC
It just occurred to me how old my tree is... some or all of this may already be fixed, I'll bite the bullet and sync and close/update this bug as appropriate.  Sorry in advance for the noise :(
Comment 6 Greg Turner 2012-04-06 19:59:00 UTC
(In reply to comment #5)
> It just occurred to me how old my tree is... some or all of this may already
> be fixed, I'll bite the bullet and sync and close/update this bug as
> appropriate.  Sorry in advance for the noise :(

OK, as of the latest prefix-rsync all three problems are still present:

o epunt_cxx before elibtoolize defeats purpose
o epunt_cxx fails against libtool 2.4.2
o epunt_cxx should not be run if test useflag set

So I stand by my bug.
Comment 7 Greg Turner 2012-04-06 20:01:15 UTC
(In reply to comment #6)
> o epunt_cxx before elibtoolize defeats purpose
s/elibtoolize/eautoreconf/
Comment 8 SpanKY gentoo-dev 2012-04-09 00:31:43 UTC
the point of epunt_cxx was to work around old libtool code that would incorrectly require newer C++ compilers when the code didn't actually need it

it doesn't make any sense to patch configure.{ac,in} because there's nothing to patch in those files

i've drop epunt_cxx from the libtool-2.x ebuilds