gperf: configure failed

[rkjones.iii@…]

When trying to install boost universal on 10.7.5 I get the following errors

compiles-imac:growcoin-master compile$ sudo port install boost +no_single+no_static+python27+universal
Password:
--->  Configuring gperf
Error: Failed to configure gperf, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/work/gperf-3.0.4/config.log
Error: org.macports.configure for port gperf returned: configure failure: command execution failed
Please see the log file for port gperf for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/main.log
Error: Unable to upgrade port: 1
Error: Unable to execute port: upgrade zlib failed

I also cannot upgrade zlib as it does not find anything needing upgrading.

[ryandesign (Ryan Carsten Schmidt)]

Please run:

sudo port clean gperf

Then try again. If it fails again, please attach the main.log file.

[rkjones.iii@…]

main.log

[rkjones.iii@…]

i was looking at the main.log and was wondering if this could be my issue?

:info:configure configure: error: C compiler cannot create executables

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

You would get this error if you did not have the command line tools installed (see the ​FAQ entry).
MacPorts should detect this error, however.
Are you running the latest version of MacPorts?
If not, please run

sudo port selfupdate
sudo port clean gperf
sudo port install gperf

If you still get the same error, please have a look at

/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/work/gperf-3.0.4/config.log

for clues as to why your compiler is failing.

[rkjones.iii@…]

i am running the latest version of macports, i have xcode and the command line tools installed and i have also ran xcode so i can agree to the agreement and i did those commands but it didnt try to install gperf until i tried to install boost, also attached is the config.log

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Sorry, but I asked for the wrong file.
Could you please look at

/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/work/gperf-3.0.4/lib/config.log

for clues as to why your compiler is failing.

[rkjones.iii@…]

no problem at all here is the correct one

[rkjones.iii@…]

from the lib folder

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

The library /usr/lib/libunwind.dylib seems to be the problem.
It seems to be the wrong architecture (x86_64?) but your are trying to build a universal binary (x86_64 and i386).

The questions is where /usr/lib/libunwind.dylib came from.
On the systems I checked, libunwind.dylib is in /usr/lib/system and is a universal library.
file /usr/lib/system/libunwind.dylib yields

/usr/lib/system/libunwind.dylib: Mach-O universal binary with 2 architectures
/usr/lib/system/libunwind.dylib (for architecture i386):	Mach-O dynamically linked shared library i386
/usr/lib/system/libunwind.dylib (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64

Do you have some sort of custom setup in which you installed /usr/lib/libunwind.dylib yourself?

[rkjones.iii@…]

Replying to mcalhoun@…:

The library /usr/lib/libunwind.dylib seems to be the problem.
It seems to be the wrong architecture (x86_64?) but your are trying to build a universal binary (x86_64 and i386).

The questions is where /usr/lib/libunwind.dylib came from.
On the systems I checked, libunwind.dylib is in /usr/lib/system and is a universal library.
file /usr/lib/system/libunwind.dylib yields

/usr/lib/system/libunwind.dylib: Mach-O universal binary with 2 architectures
/usr/lib/system/libunwind.dylib (for architecture i386):	Mach-O dynamically linked shared library i386
/usr/lib/system/libunwind.dylib (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64

Do you have some sort of custom setup in which you installed /usr/lib/libunwind.dylib yourself?

to be honest i dont even know what that is, i installed a select few ports to compile qt apps so the only thing i can think of is it came with one of the ports i installed but i dont know for sure

[rkjones.iii@…]

is there a way i can fix this so i can update/install ports and get my compiler working again?

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Replying to rkjones.iii@…:

is there a way i can fix this so i can update/install ports and get my compiler working again?

I am afraid this question is outside my area of expertise.

Perhaps libunwind.dylib is supposed to be in /usr/lib/ on 10.7.5.
I no longer have a machine on which to test.
On my machine (10.11.5), it is located in /usr/lib/system/
MacPorts does not install anything into /usr/lib, so I doubt it came from a previous port installation.

What is the result of running the commands?

file /usr/lib/system/libunwind.dylib
file /usr/lib/libunwind.dylib

You also might also have some luck in asking for help on one of the ​MacPorts Mailing Lists.

[rkjones.iii@…]

here is the output of the command

compiles-imac:~ compile$ file /usr/lib/system/libunwind.dylib

/usr/lib/system/libunwind.dylib: Mach-O universal binary with 2 architectures

/usr/lib/system/libunwind.dylib (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64

/usr/lib/system/libunwind.dylib (for architecture i386):	Mach-O dynamically linked shared library i386

compiles-imac:~ compile$ file /usr/lib/libunwind.dylib

/usr/lib/libunwind.dylib: Mach-O 64-bit dynamically linked shared library x86_64

compiles-imac:~ compile$ 

[rkjones.iii@…]

quick update i copied the libunwind.dylib file from /usr/lib/system and replaced the one in /usr/lib with that one and now it is installing ports again, i will keep this open for now just incase something else comes up

[jmroot (Joshua Root)]

Replying to mcalhoun@…:

Perhaps libunwind.dylib is supposed to be in /usr/lib/ on 10.7.5.

Nope, I checked my 10.7 VM and there is no /usr/lib/libunwind.dylib. Short of an OS reinstall, I guess you could check pkgutil to perhaps see where this file came from and what else came with it:

pkgutil --file-info /usr/lib/libunwind.dylib
pkgutil --files <pkgid from previous command's output>

Anyway, closing this ticket because it is the result of an incorrectly modified OS. If you need more help, please ask on the list.