Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#44094 closed defect (worksforme)

octave @ 3.6.4_13 build failure

Reported by: paultbaker@… Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.3.0
Keywords: Cc: petrrr
Port: octave

Description

build failure for octave-3.6.4_13+atlas+gcc48.darwin_13.x86_64.tbz2 on OS 10.9.3, xcode 5.1.1

error: no such file or directory: '/usr/local/lib/libgfortran.dylib'

I have libgfortran.3.dylib in this directory.

Attachments (2)

octave_main.log.gz (64.0 KB) - added by paultbaker@… 10 years ago.
build log
octave_config_log.txt.gz (132.1 KB) - added by paultbaker@… 10 years ago.

Download all attachments as: .zip

Change History (11)

Changed 10 years ago by paultbaker@…

Attachment: octave_main.log.gz added

build log

comment:1 Changed 10 years ago by mf2k (Frank Schima)

Cc: michaelld@… removed
Keywords: octave mavericks removed
Owner: changed from macports-tickets@… to michaelld@…

Note that Macports does not support having anything in /usr/local/. Instead the gcc48 variant provides the FORTRAN compiler needed here.

comment:2 in reply to:  1 Changed 10 years ago by paultbaker@…

Replying to mf2k@…:

Note that Macports does not support having anything in /usr/local/. Instead the gcc48 variant provides the FORTRAN compiler needed here.

macports is installed in /opt/local/. I have macports gcc48 installed.

comment:3 Changed 10 years ago by michaelld (Michael Dickens)

Can you do:

cp `port work octave`/octave-3.6.4/config.log ~/Desktop/octave_config_log.txt
bzip2 ~/Desktop/octave_config_log.txt

and then post the resulting file to this ticket?

Changed 10 years ago by paultbaker@…

Attachment: octave_config_log.txt.gz added

comment:4 in reply to:  3 Changed 10 years ago by paultbaker@…

Replying to michaelld@…:

Can you do:

cp `port work octave`/octave-3.6.4/config.log ~/Desktop/octave_config_log.txt
bzip2 ~/Desktop/octave_config_log.txt

and then post the resulting file to this ticket?

for some reason I don't have bzip... so gzip.

That log confirms it was using /opt/local/bin/gfortran-mp-4.8. /opt/local/lib/gcc48/ is in my library path and libgfortran.dylib is in that directory. I cannot figure out why it wanted /usr/local/lib/libgfortran.dylib.

I'm going to clean and rebuild again with a reduced $PATH.

comment:5 Changed 10 years ago by paultbaker@…

The cleaned rebuild had the same result.

comment:6 Changed 10 years ago by michaelld (Michael Dickens)

Is there anything in /usr/local (at all)? Try:

sudo port clean octave
sudo mv /usr/local /usr/local_tmp
sudo port install octave

then move /usr/local back:

sudo mv /usr/local_tmp /usr/local

I'm guessing there is something being brought in by libtool during linking from /usr/local, even though the configure script looks like it is finding everything correctly & build is working up until that point.

comment:7 Changed 10 years ago by paultbaker@…

It worked!

The only thing in /usr/local/ was an install of gcc4.9. There was a fortran compiler in there, hence the conflict. I don't understand why libtool was looking there... but since it's fixed I don't care anymore.

I have no idea how gcc4.9 got there! It's not from macports. If my memory serves, /usr/local/ doesn't exist by default on Macs. I should just nuke the directory and never put anything there again...

Thanks for all of your help.

comment:8 Changed 10 years ago by michaelld (Michael Dickens)

Resolution: worksforme
Status: newclosed

Awesome! Let's file this under "stuff happens". And, yes, if I were you I'd just nuke the whole directory. It's not used by OSX, and, obviously by this example, sometimes gets in the way of useful things.

comment:9 Changed 10 years ago by petrrr

Cc: Peter.Danecek@… added

Cc Me!

Note: See TracTickets for help on using tickets.