Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 332017 - sys-apps/groff-1.20.1-r3: cannot update from r2
Summary: sys-apps/groff-1.20.1-r3: cannot update from r2
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Gentoo Prefix
URL:
Whiteboard:
Keywords:
: 332167 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-10 10:56 UTC by Florian CROUZAT (SuperFlo)
Modified: 2010-08-16 20:13 UTC (History)
1 user (show)

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


Attachments
build.log (build.log,80.62 KB, text/plain)
2010-08-10 10:56 UTC, Florian CROUZAT (SuperFlo)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian CROUZAT (SuperFlo) 2010-08-10 10:56:08 UTC
Groff cannot be updated from r2 to r3 on my x64-macos.
Apparently, the bug has been discussed in 2009 at the gnu mailing list, see:http://lists.gnu.org/archive/html/groff/2009-07/msg00016.html
Comment 1 Florian CROUZAT (SuperFlo) 2010-08-10 10:56:45 UTC
Created attachment 242225 [details]
build.log
Comment 2 Fabian Groffen gentoo-dev 2010-08-10 11:00:11 UTC
hmmm, I thought I fixed this yesterday?!?
Comment 3 Fabian Groffen gentoo-dev 2010-08-10 11:01:38 UTC
ah, I did fix, but did not commit ;)
Comment 4 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-08-11 01:25:13 UTC
*** Bug 332167 has been marked as a duplicate of this bug. ***
Comment 5 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2010-08-16 19:10:02 UTC
Ah, it isn't just a darwin problem: http://www.mail-archive.com/groff@gnu.org/msg05057.html

And, I confirmed an issue on ~amd64-linux with gcc-4.2.4 (the one we bootstrap with) so it hurts all users after they emerge --sync because they haven't had a gcc update yet.

Therefore, I unconditionalized the "fix" for darwin.
Comment 6 Fabian Groffen gentoo-dev 2010-08-16 20:13:23 UTC
shouldn't hurt anyone in any case, it's just some stupid destructor that's declared inline...