[MacPorts] #27659: wine, wine-devel: winebuild picks the wrong assembler in presence of binutils
MacPorts
noreply at macports.org
Wed Dec 15 07:52:13 PST 2010
#27659: wine, wine-devel: winebuild picks the wrong assembler in presence of
binutils
----------------------------+-----------------------------------------------
Reporter: buffyg@… | Owner: ryandesign@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port: wine, wine-devel
----------------------------+-----------------------------------------------
Comment(by buffyg@…):
I don't see gas in binutils after the upgrade. I took a look at the source
history, and it appears that configure for binutils was modified a while
back to remove gas, ld, and gprof on x86_64-*-darwin targets. Here's the
snippet from configure.ac, excerpted down to include only the darwin
branches:
{{{
case "${target}" in
powerpc-*-darwin*)
noconfigdirs="$noconfigdirs ld gas gdb gprof"
noconfigdirs="$noconfigdirs sim target-rda"
;;
i[[3456789]]86-*-darwin*)
noconfigdirs="$noconfigdirs ld gprof"
noconfigdirs="$noconfigdirs sim target-rda"
;;
x86_64-*-darwin[[912]]*)
noconfigdirs="$noconfigdirs ld gas gprof"
noconfigdirs="$noconfigdirs sim target-rda"
;;
*-*-darwin*)
noconfigdirs="$noconfigdirs ld gas gdb gprof"
noconfigdirs="$noconfigdirs sim target-rda"
noconfigdirs="$noconfigdirs ${libgcj}"
;;
esac
}}}
If I'm reading this correctly, the problem will still manifest on
i?86-*-darwin machines. If this is correct (and one could test it by
building manually and specifying the x86 configuration profile on an
x86_64 machines), I expect there are two options: one would be to create a
new revision of binutils that modifies configure to exclude gas from being
built by default on that system, and the other would be to eliminate any
assumptions about whether gas is present or not by patching wine to avoid
it. I know that there's a standard disclaimer indicating that binutils can
cause problems with other ports, so another option would be to leave it
broken, as the expectation should be that anyone installing it should be
willing and able to deal with collateral damage.
--
Ticket URL: <https://trac.macports.org/ticket/27659#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list