gmp @6.0.0: Missing operand value assumed absolute 0.

[stephenallen@…]

Hi there,

I'm a couple of days into installing the various ports required for get_iplayer and am having trouble installing ffmpeg as it's dependency "gmp" fails to build.

I've cleaned (sudo port clean gmp) and tried to reinstall (sudo port -t install gmp) but to no avail. Log file attached

[stephenallen@…]

Log file of install failure

[ryandesign (Ryan Carsten Schmidt)]

gmp @6.0.0 builds fine on my Leopard system but your log shows:

:info:build tmp-dive_1.s:156:Missing operand value assumed absolute 0.
:info:build tmp-dive_1.s:156:junk `[.-Lhere]' after expression
:info:build tmp-dive_1.s:158:junk `@GOT' after expression

Your log also shows a couple odd things:

:info:build  /usr/bin/gcc-4.2 -std=gnu99 -c -DHAVE_CONFIG_H -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_dive_1 -I/opt/local/include -m32 -O2 -pedantic -fomit-frame-pointer -mtune=pentium3 -march=pentium3 tmp-dive_1.s -fno-common -DPIC -o .libs/dive_1.o
:info:configure checking build system type... atom-apple-darwin9.4.0
:info:configure checking host system type... atom-apple-darwin9.4.0

The latest version of Leopard is 10.5.8, but this shows you are running 10.5.4. Can you upgrade? It may be a problem that has been fixed in a later version of OS X.

What version of Xcode do you have? The latest for Leopard is 3.1.4; if you have an earlier version, try upgrading to 3.1.4.

The log also shows you have an Atom CPU? Is that accurate, or has gmp misidentified your system? I know of no Macs containing an Atom CPU. gmp contains assembly code, and assembly code varies by CPU. And the build failure occurred in assembly code. There may be a bug in the gmp project's atom assembly code. You could report the problem to developers of gmp.

It could be that there is a bug in Xcode's gcc compiler that makes it unable to compile this Atom assembly code. You could try a different compiler, for example "sudo port clean gmp && sudo port install gmp configure.compiler=macports-clang-3.4"

[ryandesign (Ryan Carsten Schmidt)]

It's also possible that the Atom assembly they've written works fine but is meant for a different compiler, such as fsf gcc. Assembly syntax is often different between OS X and non-OS X systems. If using a newer Xcode or clang doesn't work, you could try using fsf gcc5: "sudo port clean gmp && sudo port install gmp configure.compiler=macports-gcc-5" (though using fsf gcc on OS X for C++ code (which gmp does contain) can be problematic due to mixing of libstdc++ versions).

[stephenallen@…]

Replying to ryandesign@…:

It's also possible that the Atom assembly they've written works fine but is meant for a different compiler, such as fsf gcc. Assembly syntax is often different between OS X and non-OS X systems. If using a newer Xcode or clang doesn't work, you could try using fsf gcc5: "sudo port clean gmp && sudo port install gmp configure.compiler=macports-gcc-5" (though using fsf gcc on OS X for C++ code (which gmp does contain) can be problematic due to mixing of libstdc++ versions).

Yep my system is a dog's breakfast I'm afraid - Long story short I bought it in pre-tablet days for front-end web stuff (text based) and installed OSX 10.5.4. I don't need any horsepower so it was eventually retired and used as my main PC. OS Updates cause KP or things to stop working, so after a few tries I went back to the reliable 10.5.4 base.

Left it on overnight installing clang so will try that approach first. If that fails I'll try the GCC 5 approach.

[stephenallen@…]

failure log gcc5

[stephenallen@…]

Neither approach worked - gcc and clang failure logs attached :(

It seems that gmp is a dependecy of gcc?

I'm using Xcode 3.1.4 which was the final version to support Leopard.

[stephenallen@…]

Hi there,

I've just tried to install another port and have run up against this issue again (I'd forgotten about it) It seems to be an issue with gmp generally - there must be a way to compile gmp on my system - there are loads of 32bit macs out there - and loads of Aton N270 linux machines - this must be possible?

S

[ryandesign (Ryan Carsten Schmidt)]

I'm sorry, I don't know how to help you. You're using an ancient version of Mac OS X on a system it was never meant to run on. We cannot provide support for issues that appear to be unique that unsupported configuration. In any case, it does not sound like a MacPorts-specific problem, so you could try to report it directly to the developers of gmp. If they agree there's a bug, and they can fix it, and they release a new version containing the fix, then we can update the MacPorts gmp port to that version.

[stephenallen@…]

That's fine, thanks for your help. It is a horrible system. I'm going to be migrating to some kind of flavour of nix so I can at least update my OS every few years.

thanks again,

S

Replying to ryandesign@…:

I'm sorry, I don't know how to help you. You're using an ancient version of Mac OS X on a system it was never meant to run on. We cannot provide support for issues that appear to be unique that unsupported configuration. In any case, it does not sound like a MacPorts-specific problem, so you could try to report it directly to the developers of gmp. If they agree there's a bug, and they can fix it, and they release a new version containing the fix, then we can update the MacPorts gmp port to that version.