port tries to compile with gcc3.4 every time
Ryan Schmidt
ryandesign at macports.org
Tue Nov 7 14:31:23 PST 2006
On Nov 7, 2006, at 03:57, Francisco Moreno Muñoz wrote:
> Every time i try to install something with the ports I get this
> error message:
>
> ---> Configuring gcc34
> Error: Target com.apple.configure returned: configure failure:
> shell command "cd "/opt/local/var/db/dports/build/
> _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_
> dports_lang_gcc34/work/build" && CC=/usr/bin/gcc-3.3 /opt/local/var/
> db/dports/build/
> _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_
> dports_lang_gcc34/work/gcc-3.4.6/configure --prefix=/opt/local --
> enable-languages=c,c++,f77,objc,java --libdir=/opt/local/lib/
> gcc-3.4 --infodir=/opt/local/share/info --mandir=/opt/local/share/
> man --with-system-zlib --disable-nls --program-suffix=-dp-3.4 --
> with-local-prefix=/opt/local --with-gxx-include-dir=/opt/local/
> include/gcc-3.4/c++/" returned error 1
> Command output: loading cache ./config.cache
> checking host system type... i686-apple-darwin8.8.1
> checking target system type... i686-apple-darwin8.8.1
> checking build system type... i686-apple-darwin8.8.1
> checking for a BSD compatible install... /usr/bin/install -c
> *** This configuration is not supported in the following
> subdirectories:
> target-libobjc target-libffi target-boehm-gc target-zlib
> target-libjava
> (Any other directories should still work fine.)
> gcc-3.3: installation problem, cannot exec `cc1': No such file or
> directory
> gcc-3.3: installation problem, cannot exec `cc1': No such file or
> directory
> *** The command '/usr/bin/gcc-3.3 -o conftest -g conftest.c' failed.
> *** You must set the environment variable CC to a working compiler.
>
> Error: Status 1 encountered during processing.
>
> I've already tried to do gcc_select 4.0 or gcc_select 3.3 but it
> still tries to compile with gcc3.4 (which I don't have), and I
> don't know why.
> Is there a way to force ports to compile with gcc4.0? Or do you
> know another solution?
gcc3 is not supported on Intel, so as you've realized, you don't want
to be compiling that. However, only specific ports explicitly depend
on gcc3. Exactly which ports are you trying to use which are doing
this? Most shouldn't.
More information about the macports-users
mailing list