[mercury-users] Problems building Mercury 0.13.0 on Mac OS X 10.4.7 Tiger

Julien Fischer juliensf at csse.unimelb.edu.au
Tue Sep 26 15:31:06 AEST 2006

On Thu, 21 Sep 2006, Markus Morawitz wrote:

> Hello,
> I have compiled the new Mercury release 0.13.0 on a G4 running Mac OS X 
> 10.4.7 Tiger.
> Although using gcc version 3.3 as recommended (gcc 4.0 indeed do not work at 
> all) I have run into problems. Luckily I was able to find a workaround 
> changing two files after running configure and the build of Mercury 
> succeeded.
> In the following I will shortly describe all the necessary steps to compile 
> and install Mercury on Mac OS X including the problem I have encountered.
> Step 1:
> Run the configuration script as follows:
> ./configure --with-cc=/usr/bin/gcc-3.3
> Step 2:
> The problem occurs by linking against libgcc.a.
> The configuration mechanism uses the command `/usr/bin/gcc-3.3 -print- 
> libgcc-file-name` to link against the library. But unfortunately this command 
> only results in the string "libgcc.a" and not the full path of the library 
> (which gcc-4.0 does!). The linker cannot find libgcc.a and fails.

The configure script uses that mechanism because that's what the
gcc documentation says you should do to link against libgcc.  It looks
like the version of gcc-3.3 supplied with 10.4.7 (note that on 10.3.9 
gcc-3.3 works fine.)


> Perhaps the configuration process can be investigated and changed somehow to 
> cope with the strange behaviour of the argument "-print-libgcc-file-name" for 
> gcc on Mac OS X.

I think the configuration process is correct in that it follows the
documented behaviour of gcc.  I take it that the gcc 3.3 in question was
one of the Apple builds?

mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au

More information about the users mailing list