Opened 11 years ago

Closed 11 years ago

#36723 closed defect (invalid)

metis: revupgrade detected that cmpfillin links with library in destroot

Reported by: tijmentieleman@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: metis

Description

I was trying to install octave. That depends on metis, apparently. Installing metis fails. I uninstalled octave and metis (or whatever was left of it after I interrupted installation after an hour), and then again tried installing metis. It failed in the same way. See the error messages in the attachment.

I'm running Mac OS 10.6.8. I failed to find out what version of Xcode i'm using; if anybody can tell me how to find out then I'll check that.

Attachments (2)

c.txt (11.5 KB) - added by tijmentieleman@… 11 years ago.
main.log (166.6 KB) - added by tijmentieleman@… 11 years ago.
metis log

Download all attachments as: .zip

Change History (9)

Changed 11 years ago by tijmentieleman@…

Attachment: c.txt added

comment:1 in reply to:  description ; Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Summary: metis - build failuremetis: revupgrade detected that cmpfillin links with library in destroot

Replying to tijmentieleman@…:

I was trying to install octave. That depends on metis, apparently. Installing metis fails. I uninstalled octave and metis (or whatever was left of it after I interrupted installation after an hour), and then again tried installing metis. It failed in the same way. See the error messages in the attachment.

The transcript you attached doesn't show metis failing to build; rather, it shows metis being installed successfully, and then revupgrade declaring that it is broken because:

Could not open /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_metis/metis/work/metis-5.0.2/build/Darwin-i386/libmetis/libmetis.dylib: Error opening or reading file (referenced from /opt/local/bin/cmpfillin)

That seems to be a valid complaint. On my Mountain Lion system, I don't see that problem. cmpfillin is linked with /opt/local/lib/libmetis.dylib as it should be. I can test on Snow Leopard later.

You could try rebuilding again, running the destroot phase explicitly, which will build and destroot but stop short of installing. This will also keep the log file. (MacPorts normally deletes logs of successful builds.)

sudo port clean metis
sudo port -s destroot metis build.jobs=1
port logfile metis

This last command will show you where the logfile is. Please attach it to this ticket. If it's large, compress it first.

Building with 1 job instead of the default of multiple jobs makes the log easier to compare with others.

I'm running Mac OS 10.6.8. I failed to find out what version of Xcode i'm using; if anybody can tell me how to find out then I'll check that.

Find Xcode.app in /Developer/Applications or /Applications, click it, go to the File menu, select Get Info.

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

I have now tested on Snow Leopard and cannot reproduce the problem there either. So please attach the log requested above.

Changed 11 years ago by tijmentieleman@…

Attachment: main.log added

metis log

comment:3 in reply to:  1 Changed 11 years ago by tijmentieleman@…

Thanks. I followed your instructions. My Xcode version is 3.2.5, 64-bit. The metis log file is now attached to this ticket.

Cheers,

Tijmen

Replying to ryandesign@…:

Replying to tijmentieleman@…:

I was trying to install octave. That depends on metis, apparently. Installing metis fails. I uninstalled octave and metis (or whatever was left of it after I interrupted installation after an hour), and then again tried installing metis. It failed in the same way. See the error messages in the attachment.

The transcript you attached doesn't show metis failing to build; rather, it shows metis being installed successfully, and then revupgrade declaring that it is broken because:

Could not open /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_metis/metis/work/metis-5.0.2/build/Darwin-i386/libmetis/libmetis.dylib: Error opening or reading file (referenced from /opt/local/bin/cmpfillin)

That seems to be a valid complaint. On my Mountain Lion system, I don't see that problem. cmpfillin is linked with /opt/local/lib/libmetis.dylib as it should be. I can test on Snow Leopard later.

You could try rebuilding again, running the destroot phase explicitly, which will build and destroot but stop short of installing. This will also keep the log file. (MacPorts normally deletes logs of successful builds.)

sudo port clean metis
sudo port -s destroot metis build.jobs=1
port logfile metis

This last command will show you where the logfile is. Please attach it to this ticket. If it's large, compress it first.

Building with 1 job instead of the default of multiple jobs makes the log easier to compare with others.

I'm running Mac OS 10.6.8. I failed to find out what version of Xcode i'm using; if anybody can tell me how to find out then I'll check that.

Find Xcode.app in /Developer/Applications or /Applications, click it, go to the File menu, select Get Info.

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

The log contains this telling line:

/usr/bin/install_name_tool: object: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_metis/metis/work/destroot/opt/local/bin/cmpfillin malformed object (unknown load command 4)

This tells us that your install_name_tool command is too old to read this type of compiled object. This should not happen, but I've seen it happen to other users who have somehow inadvertently replaced their install_name_tool command with one from an older version of Xcode. The solution would be to reinstall Xcode. Consider taking this opportunity to upgrade to Xcode 3.2.6 since that's the last free version for Snow Leopard.

comment:5 Changed 11 years ago by tijmentieleman@…

OK, I'm trying to reinstall Xcode. It's a 4GB download; may take a while. Thanks for the advice.

comment:6 Changed 11 years ago by tijmentieleman@…

I reinstalled Xcode as recommended, and the problem appears to be fixed now. Thanks a lot!

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

Resolution: invalid
Status: newclosed

Great, glad you got it working.

Note: See TracTickets for help on using tickets.