Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 19146 - wine-20030408 does not compile
Summary: wine-20030408 does not compile
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: phoen][x
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-11 10:31 UTC by Nick Burtner
Modified: 2003-04-11 16:15 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Burtner 2003-04-11 10:31:37 UTC
As you may have gleaned from the bugzilla description, the current build of wine
doesn't compile, which is mainly do to the new binutils.  However, the version
in wine's CVS builds fine with binutils > 18, thanks to the bugfix in
winebuild's import.c.  Just thought that I should bring this to your attention.

And yes, I have tried to build it from the CVS, and I know that it works fine
when using the wine/tools/wineinstall script.

Thanks for your time.
Comment 1 Robert Cole 2003-04-11 12:09:05 UTC
I didn't try it but I did notice this:

rcole@ws1 rcole $ emerge -p wine

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild  N   ] dev-util/yacc-1.9.1-r1
[ebuild    UD] sys-devel/binutils-2.13.90.0.18-r1 [2.13.90.0.20-r1]
[ebuild  N   ] app-emulation/wine-20030408

rcole@ws1 rcole $

That's why I didn't try. Downgrading binutils in the past has had ugly effects for me.
Comment 2 Martin Holzer (RETIRED) gentoo-dev 2003-04-11 13:22:23 UTC
emerge -U

read emerge --help
Comment 3 phoen][x 2003-04-11 13:37:09 UTC
Well i cant help you then.

Falling back to binutils-2.13.90.0.18 is the only way to get wine-20030408 to work. I might take a cvs snapshot this weekend and see if that works with the new binutils (as said in comment #0).

-phoen][x-
Comment 4 Nick Burtner 2003-04-11 15:32:07 UTC
Maybe you could make a wine-cvs ebuild like the winex-cvs one.  That way, we can just keep up with wine-CURRENT, you know, for occasions like this, when the fix for a build problem came out right after the most recent snapshot. ;)

I think it would probably go over pretty well, especially for people who like really bleeding edge stuff.
Comment 5 phoen][x 2003-04-11 16:15:51 UTC
No sorry, i'll not create a wine-cvs ebuild. I'll better stick to make snapshots and upload them to the gentoo mirrors. The load of -cvs ebuild on the cvs server is quite immense. I don't know what you know about the gaim-cvs issue, but it's enough when i say that we definitely should think about the amount of users who use the cvs-ebuilds. Gentoo was kinda smallish once, but we have load of users now. My opinion is: Use cvs ebuilds where you have to. Do not use them if there is another way.

WineHQ releases a snapshot every month. That's okay with me. If there is a real evil bug (like this one), i'm able to snapshot the cvs tree and create an ebuild for it (takes about 5 minutes). A cvs-ebuild is not needed imnsho. If you want to discuss this, catch me in irc or flood me with mails. :)

I put the new version into the portage tree - it goes by the name wine-20030411 (surprise). Check but #17986 for further informations.

A big thanks to you, Nick. The cvs snapshot was a very good idea indeed.

-phoen][x-