[Pidgin] #5605: Compile fails on MacOS X with error related to the use of -arch and -M in libpurple's Perl support
Pidgin
trac at pidgin.im
Wed Apr 23 09:26:59 EDT 2008
#5605: Compile fails on MacOS X with error related to the use of -arch and -M in
libpurple's Perl support
------------------------+---------------------------------------------------
Reporter: sfisher | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: libpurple | Version: 2.4.1
Resolution: | Keywords:
Pending: 0 |
------------------------+---------------------------------------------------
Old description:
> Pidgin 2.4.1 fails to compile for me on MacOS X 10.5.2 unless I pass
> --disable-perl to the configure script. I was using Pidgin 2.3.0
> originally compiled fine (months ago), but after a make clean and running
> configure again in 2.3.0, it gets the same compile error. The error is
> below:
>
> sfisher at shadow:/usr/local/src/pidgin-2.4.1>make
> make all-recursive
> Making all in libpurple
> make all-recursive
> Making all in plugins
> Making all in perl
> /bin/sh ../../../libtool --silent --tag=CC --mode=compile gcc
> -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../libpurple
> -I../../../libpurple -Wall -D_REENTRANT -I/usr/local/include/glib-2.0
> -I/usr/local/lib/glib-2.0/include -arch i386 -arch ppc -g -pipe -fno-
> common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -Wdeclaration-
> after-statement -I/usr/local/include -I/System/Library/Perl/5.8.8
> /darwin-thread-multi-2level/CORE -g -g -O2 -MT perl.lo -MD -MP -MF
> .deps/perl.Tpo -c -o perl.lo perl.c
> gcc-4.0: -E, -S, -save-temps and -M options are not allowed with multiple
> -arch flags
> make[5]: *** [perl.lo] Error 1
> make[4]: *** [all-recursive] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
> sfisher at shadow:/usr/local/src/pidgin-2.4.1>
New description:
Pidgin 2.4.1 fails to compile for me on MacOS X 10.5.2 unless I pass
--disable-perl to the configure script. I was using Pidgin 2.3.0
originally compiled fine (months ago), but after a make clean and running
configure again in 2.3.0, it gets the same compile error. The error is
below:
{{{
sfisher at shadow:/usr/local/src/pidgin-2.4.1>make
make all-recursive
Making all in libpurple
make all-recursive
Making all in plugins
Making all in perl
/bin/sh ../../../libtool --silent --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../libpurple
-I../../../libpurple -Wall -D_REENTRANT -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include -arch i386 -arch ppc -g -pipe
-fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing
-Wdeclaration-after-statement -I/usr/local/include
-I/System/Library/Perl/5.8.8/darwin-thread-multi-2level/CORE -g -g
-O2 -MT perl.lo -MD -MP -MF .deps/perl.Tpo -c -o perl.lo perl.c
gcc-4.0: -E, -S, -save-temps and -M options are not allowed with multiple
-arch flags
make[5]: *** [perl.lo] Error 1
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
sfisher at shadow:/usr/local/src/pidgin-2.4.1>
}}}
Comment (by rekkanoryo):
This is because gcc is trying to make universal binaries. If you pass
`--host=i686-apple-darwin9` (for an Intel Mac) or `--host=powerpc-apple-
darwin9` (for a PowerPC Mac) to configure and try again, does that make a
difference?
Note: I edited the description so that the error block is easier to read.
--
Ticket URL: <http://developer.pidgin.im/ticket/5605#comment:1>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list