Opened 12 years ago
Closed 12 years ago
#36207 closed defect (fixed)
R-framework @2.15.1: ld fails to link a test executable in ./configure
Reported by: | elijah.epifanov@… | Owned by: | kjellpk (Kjell Konis) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | Cc: | ||
Port: | R-framework |
Description
less /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_R-framework/R-framework/main.log
:info:configure checking for gcc... /opt/local/bin/llvm-gcc-4.2 :info:configure checking whether the C compiler works... no :info:configure configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_R-framework/R-framework/work/R-2.15.1': :info:configure configure: error: C compiler cannot create executables :info:configure See `config.log' for more details :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_R-framework/R-framework/work/R-2.15.1" && ./configure --prefix=/opt/local/Library/Frameworks --enable-R-framework --enable-R-shlib --enable-BLAS-shlib --enable-openmp --with-readline --with-aqua --with-libpng --with-ICU --with-included-gettext --without-blas --without-lapack --with-x --with-jpeglib --x-include=/opt/local/include/X11 --x-lib=/opt/local/lib --with-cairo --with-recommended-packages --with-tcltk --with-tcl-config=/opt/local/lib/tclConfig.sh --with-tk-config=/opt/local/lib/tkConfig.sh :info:configure Exit code: 77 :error:configure org.macports.configure for port R-framework returned: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed while executing "$procedure $targetname" :info:configure Warning: targets not executed for R-framework: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:configure Please see the log file for port R-framework for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_R-framework/R-framework/main.log
Attachments (1)
Change History (10)
comment:1 Changed 12 years ago by elijah.epifanov@…
Cc: | elijah.epifanov@… added |
---|
comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | elijah.epifanov@… removed |
---|---|
Keywords: | ld universal llvm-gcc removed |
Please attach the config.log.
Changed 12 years ago by elijah.epifanov@…
Attachment: | config.log added |
---|
comment:4 Changed 12 years ago by jmroot (Joshua Root)
Cc: | elijah.epifanov@… removed |
---|---|
Owner: | changed from macports-tickets@… to kjell.konis@… |
Summary: | ld fails to link a test executable in ./configure → R-framework @2.15.1: ld fails to link a test executable in ./configure |
configure:6092: checking whether the C compiler works configure:6114: /opt/local/bin/llvm-gcc-4.2 -pipe -O2 -m64 -I/opt/local/include -L/opt/local/lib -L/opt/local/lib/llvm-gcc42 -lgfortran conftest.c >&5 ld: file is universal (2 slices) but does not contain a(n) x86_64 slice: /usr/lib/crt1.10.6.o for architecture x86_64 collect2: ld returned 1 exit status configure:6118: $? = 1 configure:6156: result: no
What does lipo -info /usr/lib/crt1.10.6.o
say? I don't have 10.8, but on 10.7 I get:
Architectures in the fat file: /usr/lib/crt1.10.6.o are: x86_64 i386
and I would imagine it should have the same archs on 10.8.
comment:5 Changed 12 years ago by kjellpk (Kjell Konis)
Maintainer here: I am unable to reproduce this. My only guess (i.e., jmr's comment) is that /usr/lib/crt1.10.6.o is somehow borked on the affected machine.
Also, on Mountain Lion:
$ lipo -info /usr/lib/crt1.10.6.o
Architectures in the fat file: /usr/lib/crt1.10.6.o are: i386 x86_64
comment:6 follow-up: 7 Changed 12 years ago by egor7@…
I have experienced the same problem. I've done all migration steps, but my result is the same:
:info:configure checking for gcc... /opt/local/bin/llvm-gcc-4.2 :info:configure checking whether the C compiler works... no
comment:7 Changed 12 years ago by larryv (Lawrence Velázquez)
Replying to egor7@…:
I have experienced the same problem. I've done all migration steps, but my result is the same:
:info:configure checking for gcc... /opt/local/bin/llvm-gcc-4.2 :info:configure checking whether the C compiler works... no
Does your config.log
show the same problem as elijah.epifanov’s?
comment:8 Changed 12 years ago by kjellpk (Kjell Konis)
Maintainer here: there's actually a bigger problem now. The llvm-gcc42 port no longer provides a fortran compiler. Bug #37647 has a patch making gcc45 the default compiler and removing the llvm-gcc42 variant (along with fixing a few other minor things). This bug can be closed.
comment:9 Changed 12 years ago by larryv (Lawrence Velázquez)
Resolution: | → fixed |
---|---|
Status: | new → closed |
I’ve removed +llvm_gcc42
in r103614.
Cc Me!