Re: Bug: cannot use i386 in path for libraries or include

Hi David

> I tried over and over to use /usr/lib/gcc/i386-redhat-linux/4.1.1
> and /usr/lib/gcc/i386-redhat-linux/4.1.1/include when answering the
> Configure questions, but that path didn't make it into the
> Makefile. The i386 was replaced by "1". I had to make a link /usr/
> lib/gcc/4.1.1 and use that instead.

The library and include directories specified above are compiler-
specific, and the compiler itself (gcc v4.1.1) knows where to
look them when compiling and linking. NCAR Graphics doesn't need to
know about these directories directly, since they're
compiler-specific.

That said, the odd substitution error you see where a letter 'i'
becomes a numeral '1' was discovered some time ago, and fixed, I
thought. Which version of the NCAR Graphics source code distribution
do you have?

> Anyway, I also wonder what ymake's problem is because I shouldn't
> have to explicitly add default system libraries to the search path.

Indeed, you do not have to. NCAR Graphics does not need to know
about those locations, as they may be different from system
to system.

> The default answer in Configure's question about library and
> include files is misleading because it seems it's just asking for
> the location of X libraries and includes. I was surprised to see
> multiple errors about missing stddef.h and stdarg.h includefiles.
> And I was even more surprised to see that the make completed with
> no error warnings at the end.

Sorry if you find the question about libraries and include files
misleading. The intent of the question is to tell the Configure process
where to look for X libraries/includes, which can and does differ
from system to system.

The messages you see about not finding "stddef.h" and "stdarg.h" and
such are generated by the command 'makedepend.' This
command is an X11 command, and by default, looks in a few standard
places for include files.

When using GNU compilers, "standard" header files such as stddef.h,
stdarg.h etc. "live" in GNU compiler-specific directories,
directories that 'makedepend' does not know about unless told.
Since, from host to host, the location for those files can be different,
and it's not necessary for 'makedepend' to truly create a dependency
on those files (the compiler knows where they are), those
messages are generated. They are annoying and disconcerting but in
no way are they a problem.

> Some relevant information maybe:
>
> Version: 4.4.1
> System : Linux 32bit
> Distro : CentOS5
> Compiler: PGI 7.0 (pgf90 & pgcc)
>
>
> BTW, I had to add -ltr to the compiler flags in LINUX.PGI -> LINUX
> because there were several undefined references to "aio_*"
> functions. And again, I was surprised that this error was buried
> deep in the log file and the make still completed.

I suggest you make sure that, in the LINUX.PGI file, this line:

#define CtoFLibraries -lpgc -lpgf90 -lpgf90_rpm1 -lpgf902 -lpgftnrtl

be replaced by this one:

#define CtoFLibraries -pgf90libs

This will tell the PGI compilers to link in, in the proper order the
C/Fortran compatibility libraries. Be sure to copy LINUX.PGI
to LINUX, and reconfig/remake.

-Rick.
----
Rick Grubin NCAR/TDD/CISL/VETS
Visualization + Enabling Technologies
grubin_at_ucar.edu 303.497.1832

_______________________________________________
ncarg-talk mailing list
ncarg-talk_at_ucar.edu
http://mailman.ucar.edu/mailman/listinfo/ncarg-talk
Received on Thu Jun 21 2007 - 15:48:19 MDT