gdc-0.24 problems on Snow Leopard

Ryan Schmidt ryandesign at macports.org
Mon Oct 19 10:05:27 PDT 2009


On Oct 19, 2009, at 04:48, Álvaro Falquina Garrido wrote:

> I have recently installed Snow Leopard and I am now trying to  
> install gdc. When I execute:
>
> $ sudo port -v install gdc
>
> the command fails:
>
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc 
> /work/build/./gcc/xgcc -B/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc 
> /work/build/./gcc/ -B/opt/local/i386-apple-darwin10.0.0/bin/ -B/opt/ 
> local/i386-apple-darwin10.0.0/lib/ -isystem /opt/local/i386-apple- 
> darwin10.0.0/include -isystem /opt/local/i386-apple-darwin10.0.0/sys- 
> include -O2 -O2 -arch x86_64  -DIN_GCC    -W -Wall -Wwrite-strings - 
> Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  - 
> isystem ./include  -I. -I. -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc 
> /work/gcc-4.1.2/gcc -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc 
> /work/gcc-4.1.2/gcc/. -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc 
> /work/gcc-4.1.2/gcc/../include -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc 
> /work/gcc-4.1.2/gcc/../libcpp/include   \
> 	  -c /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc 
> /work/gcc-4.1.2/gcc/config/darwin-crt2.c -o crt2.o
> cc1: error: unrecognized command line option "-arch"
> gnumake[2]: *** [crt2.o] Error 1
> gnumake[1]: *** [all-gcc] Error 2
> gnumake: *** [all] Error 2
> Warning: the following items did not execute (for gdc):  
> org.macports.activate org.macports.build org.macports.destroot  
> org.macports.install
>
> I have been looking for a reference to this error in the archives,  
> to no avail. Any hints? Is it OK to send a .gz file containing the  
> whole output generated by port -v?

The best thing to do would be to file a ticket in the issue tracker  
with this information.




More information about the macports-users mailing list