Opened 8 years ago
Closed 7 years ago
#53016 closed defect (fixed)
octave @4.2.0_1 build failure with libgcc-devel
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.99 |
Keywords: | Cc: | ||
Port: | octave |
Description
Undefined symbols for architecture x86_64: "___addtf3", referenced from: __gfortran_random_r16 in libgfortran.a(random.o) __gfortran_arandom_r16 in libgfortran.a(random.o) "___divtf3", referenced from: _calculate_exp_16 in libgfortran.a(write.o) _write_float in libgfortran.a(write.o) "___eqtf2", referenced from: _write_float in libgfortran.a(write.o) "___floatunditf", referenced from: __gfortran_random_r16 in libgfortran.a(random.o) __gfortran_arandom_r16 in libgfortran.a(random.o) "___getf2", referenced from: _write_float in libgfortran.a(write.o) "___gttf2", referenced from: _write_float in libgfortran.a(write.o) "___lttf2", referenced from: _write_float in libgfortran.a(write.o) "___multf3", referenced from: _calculate_exp_16 in libgfortran.a(write.o) _write_float in libgfortran.a(write.o) __gfortran_random_r16 in libgfortran.a(random.o) __gfortran_arandom_r16 in libgfortran.a(random.o) "___subtf3", referenced from: _write_float in libgfortran.a(write.o) "___unordtf2", referenced from: _write_float in libgfortran.a(write.o) ld: symbol(s) not found for architecture x86_64
Attachments (2)
Change History (7)
Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | main.log.bz2 added |
---|
comment:1 Changed 8 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
comment:2 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Thanks for the pointer. Indeed the config.log says:
dyld: Library not loaded: /opt/local/lib/libgcc/libgfortran.3.dylib Referenced from: /opt/local/lib/libarpack.2.dylib Reason: image not found ./configure: line 3803: 95270 Trace/BPT trap: 5 ./conftest$ac_exeext
I am using libgcc-devel @7-20161204, and it provides libgfortran.4.dylib instead of libgfortran.3.dylib. So I guess once gcc7 becomes stable and libgcc is updated to that version, we'll have to revbump anything linking with libgfortran.3.dylib.
Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | config.log.bz2 added |
---|
comment:3 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | octave @4.2.0_1 build failure → octave @4.2.0_1 build failure with libgcc-devel |
---|
Building octave with libgcc @6.2.0 instead of libgcc-devel @7-20161204 does work.
After discussing with Jeremy Sequoia, I think this is rather a bug in the gcc ports that will need to be solved there.
comment:4 Changed 7 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Since this ticket was opened, the old libgcc-devel has become the new libgcc.
As far as I can tell, everything is working with libgcc 7.x.x.
Can this ticket be closed?
comment:5 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
The first error that occurs is the configure script's inability to find a working arrack:
:info:configure checking whether the arpack library works... no
.This might be a symptom of the same problem that eventually prevents octave from building.
Does the config.log offer any clues as to why arparck can't be found?