[MacPorts] #26881: port orc fail to build
MacPorts
noreply at macports.org
Sun Nov 7 17:02:36 PST 2010
#26881: port orc fail to build
-----------------------------------+----------------------------------------
Reporter: develop@… | Owner: rmstonecipher@…
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Resolution: | Keywords:
Port: orc |
-----------------------------------+----------------------------------------
Changes (by neverlunch@…):
* status: closed => reopened
* resolution: fixed =>
Comment:
Universal (i386, x86_64, ppc) succeeded, BUT :
{{{
libtool: compile: /usr/bin/gcc-4.2 -DHAVE_CONFIG_H -I. -I..
-I/opt/local/include -Wall -I.. -DORC_ENABLE_UNSTABLE_API -pipe -O2
-Xarch_i386 -O1 -Xarch_x86_64 -O3 -arch ppc -c orcpowerpc.c -fno-common
-DPIC -o .libs/liborc_0.4_la-orcpowerpc.o
{standard input}:176:Parameter error: r0 not allowed for parameter 1 (code
as 0 not r0)
}}}
This failure led me to search. After some attempts inspired from
[http://gcc.gnu.org/onlinedocs/gcc/Machine-Constraints.html#Machine-
Constraints],
I got a successfully compiled universal orc. So, this
{{{
__asm__ __volatile__ ("dcbst %0,%1" :: "r" (ptr), "r" (i));
}}}
became
{{{
__asm__ __volatile__ ("dcbst %0,%1" :: "b" (ptr), "r" (i));
}}}
I'm waiting for any PowerPC expert to shout on me. ;}
I also looked into the weird "i386 -O2" error... Wouldn't it be a bug in
Apple's gcc ? Does this make sense to someone ?
{{{
leal LC0-"L00000000006$pb"(%ebx), %eax
}}}
--
Ticket URL: <https://trac.macports.org/ticket/26881#comment:26>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list