Opened 11 years ago

Closed 11 years ago

#25325 closed defect (worksforme)

gcc44: libltdl: No such file or directory

Reported by: tzvetomir.tzvetanov@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 1.9.0
Keywords: Cc: ryandesign (Ryan Schmidt)
Port: gcc44

Description

When installing octave (command: sudo port install octave), problem is present at building gcc44 (see log file below). My configuration: OSX 10.6.3, Intel Core 2 Duo, macbook pro.

I therefore tried to install gcc44 alone. Same error apears(logic). Installing gcc43 worked out.

Did not find any clue about how to get rid of this libltdl library inclusion, or where to correct the error, or any Ticket on this problem.

possibility, not tried, to fake gcc44 with symblinks (see #22203) but don't want to do not nice work arounds.

My main wish is to install octave. whether it is with gcc44 or another is not so important.

Any help is welcome.

log file ends up with:

:info:build Making all in libltdl
:info:build /bin/sh: line 0: cd: libltdl: No such file or directory
:info:build make[2]: *** [all-recursive] Error 1
:info:build make[1]: *** [all-target-libjava] Error 2
:info:build make: *** [bootstrap] Error 2
:info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/work/build" && /usr/bin/make -j2 bootstrap " returned error 2
:error:build Target org.macports.build returned: shell command failed
:debug:build Backtrace: shell command failed
    while executing
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
:info:build Warning: the following items did not execute (for gcc44): org.macports.activate org.macports.build org.macports.destroot org.macports.install
:notice:build Log for gcc44 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/main.log

Change History (5)

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

Owner: changed from macports-tickets@… to mww@…

comment:2 Changed 11 years ago by tzvetomir.tzvetanov@…

Octave installation worked out with the Variant +gcc43. (command: sudo port -d install octave +gcc43) gcc44 still not building.

comment:3 Changed 11 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added
Summary: gcc44 build failure (because of libltdl) during octave installationgcc44: libltdl: No such file or directory

I've never seen this problem building gcc44. Can you clean gcc44 ("sudo port clean gcc44"), make sure you update to MacPorts 1.9.1 ("sudo port selfupdate") and try again ("sudo port install gcc44"). If it fails again, please attach the main.log. If it doesn't fail, let us know.

comment:4 in reply to:  3 Changed 11 years ago by tzvetomir.tzvetanov@…

Replying to ryandesign@…:

I've never seen this problem building gcc44. Can you clean gcc44 ("sudo port clean gcc44"), make sure you update to MacPorts 1.9.1 ("sudo port selfupdate") and try again ("sudo port install gcc44"). If it fails again, please attach the main.log. If it doesn't fail, let us know.

following your suggestion of cleaning and reinstalling, it worked out.

have no idea what happened before. I swear i already upgraded to macport 1.9.1 before trying to install octave ... or any other ports...

it could be that my mbpro crashed because of overheating... (black window with famous osx small window asking for pressing the start button for long) but still i cleaned and uninstalled everything before redoing... ?!?

thx for help.

comment:5 Changed 11 years ago by ryandesign (Ryan Schmidt)

Resolution: worksforme
Status: newclosed

Glad you got it working. Not sure why it failed the first time.

You should not be receiving kernel panics on Snow Leopard. Such an error possibly indicates a bug in a third-party kernel extension you've installed, or if you haven't installed any, then possibly a hardware problem like bad RAM, bad logic board, or bad processor, any of which could certainly also cause problems compiling software. Overheating could probably cause that too. If you run into other problems with other ports that nobody's seen before either, consider that you may have faulty hardware.

Note: See TracTickets for help on using tickets.