Skip to content

xmkmf? problem

5 messages · Paul Gilbert, Brian Ripley

#
I am having the  xmkmf  problem below with todays beta, but I also am 
trying to use an new (PGI 6.1),  so lots of other things in my setup may 
be wrong, and the warning may also be important. Any hints would be 
appreciated.

Paul
_____

Red Hat Enterprise Linux AS release 3 (Taroon Update 7)
....
checking whether C runtime needs -D__NO_MATH_INLINES... no
checking for xmkmf... /usr/X11R6/bin/xmkmf
Usage: which [options] [--] programname [...]
Options: --version, -[vV] Print version and exit successfully.
         --help,          Print this help and exit successfully.
         --skip-dot       Skip directories in PATH that start with a dot.
         --skip-tilde     Skip directories in PATH that start with a tilde.
         --show-dot       Don't expand a dot to current directory in output.
         --show-tilde     Output a tilde for HOME directory for non-root.
         --tty-only       Stop processing options on the right if not on 
tty.
         --all, -a        Print all matches in PATH, not just the first
         --read-alias, -i Read list of aliases from stdin.
         --skip-alias     Ignore option --read-alias; don't read stdin.
         --read-functions Read shell functions from stdin.
         --skip-functions Ignore option --read-functions; don't read stdin.
Usage: which [options] [--] programname [...]
Options: --version, -[vV] Print version and exit successfully.
         --help,          Print this help and exit successfully.
         --skip-dot       Skip directories in PATH that start with a dot.
         --skip-tilde     Skip directories in PATH that start with a tilde.
         --show-dot       Don't expand a dot to current directory in output.
         --show-tilde     Output a tilde for HOME directory for non-root.
         --tty-only       Stop processing options on the right if not on 
tty.
         --all, -a        Print all matches in PATH, not just the first
         --read-alias, -i Read list of aliases from stdin.
         --skip-alias     Ignore option --read-alias; don't read stdin.
         --read-functions Read shell functions from stdin.
         --skip-functions Ignore option --read-functions; don't read stdin.
configure: WARNING: I could not determine SHLIB_LDFLAGS.
configure: error: See the file doc/html/R-admin.html for more information.
~/toolchain/R/mfa04559/R-beta:
====================================================================================

La version fran?aise suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential inform...{{dropped}}
#
On Thu, 13 Apr 2006, Paul Gilbert wrote:

            
My guess is that this is from

   cc=`${srcdir}/tools/GETMAKEVAL CC`
   cc=`echo ${cc} | sed "s/ .*//"`
   if test "`which ${cc}`" = "`which ${CC}`"; then
     shlib_ldflags=`${srcdir}/tools/GETMAKEVAL SHLIBLDFLAGS`
     cpicflags=`${srcdir}/tools/GETMAKEVAL PICFLAGS`
   fi
   cxx=`${srcdir}/tools/GETMAKEVAL CXX`
   cxx=`echo ${cxx} | sed "s/ .*//"`
   if test "`which ${cxx}`" = "`which ${CXX}`"; then
     cxxpicflags=`${srcdir}/tools/GETMAKEVAL CXXPICFLAGS`
   fi

in configure and so either your compilers are not set correctly or your 
OS's X11 does not find the compilers used to compile it.

I'd start by inserting debugging code in configure at that point to find 
out what ${cc} and ${CC} are, with the expectation that one is empty.

  
    
#
Brian

Yes cc is empty. Perhaps I should have mentioned that I have set 
CC=pgcc, to find the new compiler. Should I be setting cc too? Is there 
a problem if the compiler used for X11 was different?

Thanks,
Paul
Prof Brian Ripley wrote:
====================================================================================

La version fran?aise suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential inform...{{dropped}}
#
There are two problems here.  The more important one is with your OS, 
which seems not to have its X11 stuff correct, so cc is not being found
(and you cannot set it).  R's configure has no protection against that.

You can investigate that by

blackduck% touch Imakefile
blackduck% xmkmf
imake -DUseInstalled -I/usr/X11R6/lib/X11/config
blackduck% grep CC Makefile
...

which is what R does.  I presume that this will also fail if you compile R 
out-of-the-box with gcc?  If that works and pgcc does not then something 
else in your settings is amiss.

The second is that if you are using a different compiler from that used to 
make X11, you may need to set CPICFLAGS etc.  But we know about pgcc on 
Linux and so these will be set (but not necessarily SHLIB_LDFLAGS: see the 
R-admin manual).
On Thu, 13 Apr 2006, Paul Gilbert wrote:

            

  
    
#
I've added some protection to configure, so you might like to try again 
with tomorrow's beta or later.
On Fri, 14 Apr 2006, Prof Brian Ripley wrote: