[m-dev.] Two problems building/installing user-defined libraries, Mac OS-X

[doug.auclair at logicaltypes.com]

Dear all,

On the ROTD-2006-03-15, I am unable to build or to install libraries
I am creating on powerpc.apple.darwin8.3.  This is NOT an issue on
other platforms (specifically, I am able to build, to install, and to use
libraries that I create on sparc.sun.solaris2.8).

The first problem the compiler complains about is that it cannot build
the dynamic library because it is unable to find libgcc.a.  Actually, this
has been a recurrent problem in my builds.  What I do to build a compiler
distribution is to remove from Mmake.common and scripts/ml the
`/usr/bin/gcc-3.3 --print-libgcc-file-name` command, because on my
architecture, this causes the system to error out (as on Macs, apparently,
libgcc.a is called something else, like libgcc_s_1.0.dylib, etc -- this may
actually be a bug with gcc).  Somehow, ./configure may be making the
wrong assumption to be putting this in in the first place).  Apparently this
directive is actually embedded into building dynamic libraries.  Can
./configure be modified not to insert this part of @SHARED_LIBS@ into the
build process for this architecture? (The other parts of @SHARED_LIBS@,
e.g. $MATH_LIB and -lc work fine)

The way I temporarily fix this problem is to direct that the dynamic version
not be built, as you see in the attached error log.  But this really isn't
necessary, as the build system is able to create dynamic libraries just fine
when installing the compiler itself (as the 'wc' on my 'find ... 
"*.dylib"' in the
error log shows).

-----

The other problem is that when I go to install this finally build 
static library,
the install process dies on the first implementation, saying that it cannot
find array.mih (by the way, I do not import the array module anywhere in my
code) ... when I 'ls -l' where it's looking for this .mih file, the path goes
into infinite recursion.  Is this part of the problem, or do I need 
to set some
environmental variable to assist the install process along?  The error log
shows the dump on the install process and my (truncated) infinite 'ls -l'

I'm hoping both problems are very easy and quick to fix!  Any
recommendations and help?  Help-help-help!

Sincerely,
Doug Auclair

-------------- next part --------------
A non-text attachment was scrubbed...
Name: MAKE-ERR.LOG
Type: application/octet-stream
Size: 3981 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/developers/attachments/20060317/f5e70900/attachment.obj>