http://bugzilla.novell.com/show_bug.cgi?id=519192
User dieter.jurzitza@t-online.de added comment
http://bugzilla.novell.com/show_bug.cgi?id=519192#c3
--- Comment #3 from Dieter Jurzitza 2009-07-03 14:55:05 MDT ---
Hi Marcus,
my two cents here:
- all you developers love chroot environments. I don't because it is additional
effort for me being an "in the evening after work linuxian".
- I want my system to be "rpmified" and not "make installified" because the
latter is hard to maintain as there is no package management to check for
collisions and whatsoever.
This is the reason why I only build rpm's and tried to get this going on AMD64,
too.
Moreover I'd suggest to add a rpmbuild32 on top of rpmbuild on AMD64 systems,
containing
rpmbuild32 -> ../lib/rpm/rpmb32
and
/usr/lib/rpm/rpmb32
#!/bin/sh
/usr/bin/linux32 /usr/lib/rpmb $*
in a script. This seems to be more self explanatory when it comes to try to
generate 32bit apps on a 64bit architecture.
What regards my patches:
As a matter of fact something is going wrong with the linker flags (and only
with those) from within rpm when doing a "linux32 rpmbuild -ba wine.spec" as it
is now, because all calls to the linker fail when trying to build the plain
spec file. The linker always breaks (at several locations) saying that he is
told to generate a 64bit app but the object files he gets all are 32bit (what
is the good side of the story).
As I did a lot of guessing to make things work a part of the modifications may
be or may not be neccessary, someone with a better understanding of what
configure does (hopefully you) should be able to fix it.
As long as wine keeps being a i586 app the question arises (to me) whether that
linker flag I added to the configure line in the spec file should not be there
in general as it would not harm on i586 but is definitively a must on AMD64.
Anyway, thank you for your time and for looking into this!
Take care
Dieter
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.