AMBER Archive (2006)

Subject: Re: AMBER: Compiling Leap problem

From: David A. Case (case_at_scripps.edu)
Date: Fri Jul 14 2006 - 17:57:31 CDT

On Fri, Jul 14, 2006, sethl_at_gatech.edu wrote:

>
> I am at a total loss as to why leap will not compile properly under Amber 8 on
> my AMD 64, SUSE 10.1, iFort 9.0xx machine. I did a "./configure -static ifort"
> then a "make serial". Naturally leap doesn't compile,

I don't know why this is "natural". At line 114 of
$AMBERHOME/src/leap/src/leap/Makefile, you need to change -L$(XHOME)/lib to
-L$(XHOME)/lib64, and make sure the bugfixes are applied.

This works fine for me on Suse10 with an Intel EM64T architecture with
gcc 3.3.5 w0050117 (SUSE Linux). It also works with similar verisons of
gcc using RedHat Linux. Of course, all of this may depend on exactly how
your machine is configured. I haven't seen anything that would make me
believe that AMD 64 vs. Intel EM64T should be relevant for this problem.
 
> config.h file out with one to force 32-bit compilation

> gcc -m32 -c -I/usr/X11R6/include -O2 -o MapAg.o MapAg.c
> In file included from /usr/include/features.h:346,
> from /usr/include/stdio.h:28,
> from MapAg.c:18:
> /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory

This is harder to trace down, but it looks like some of the stuff needed for
32-bit compilation are not present on your machine. Of course, you could look
at /usr/include/features.h to track down something, but that probably won't
tell you how to fix it.

If you have any possible access (even just for a short while) to a 32-bit
machine, that might be the easiest way to construct a 32-bit version,
since its libraries are more likely to be set up correctly.

....dac

-----------------------------------------------------------------------
The AMBER Mail Reflector
To post, send mail to amber_at_scripps.edu
To unsubscribe, send "unsubscribe amber" to majordomo_at_scripps.edu