GCC On Solaris 2.4

Question

Hello Gents,
I'm trying to use the gnu c compiler in a Box with Solaris 2.4 but I've got this message when I try to compile something, also I've got a error message when I'm tryin' to generate the make files for specific program, in this case I'm talking about sudo, but this happens with any kind of software that I need to compile.
Can anyone tell me if I'd need to install another kind of patch or library to fix it?
# pkginfo | grep -i gcc
utility GNUgcc GNU gcc 2.95.2 SPARC Solaris 2.4
application SMClibgcc lgcc
# pkginfo | grep -v SUNW
utility GNUaconf GNU autoconf 2.13 SPARC Solaris 2.4
utility GNUamake GNU automake 1.4 SPARC Solaris 2.4
utility GNUgcc GNU gcc 2.95.2 SPARC Solaris 2.4
utility GNUgdb GNU gdb 4.17 SPARC Solaris 2.4
utility GNUgdbm GNU gdbm 1.8.0 SPARC Solaris 2.4
utility GNUmake GNU make 3.78.1 SPARC Solaris 2.4
application SMClibgcc lgcc
# cat nada.c
"nada.c" 11 lines, 97 characters
#include <stdio.h>
main()
for(;;)
printf ("Hello World!\n");
# /usr/local/bin/gcc nada.c -o nada
In file included from nada.c:1:
/usr/local/lib/gcc-lib/sparc-sun-solaris2.4/2.95.2/include/stdio.h:17: sys/featu
# cd /sudo-1.6.9p16
# ./configure
configure: Configuring Sudo version 1.6.9
checking whether to lecture users the first time they run sudo... yes
checking whether sudo should log via syslog or to a file by default... syslog
checking which syslog facility sudo should log with... local2
checking at which syslog priority to log commands... notice
checking at which syslog priority to log failures... alert
checking how long a line in the log file should be... 80
checking whether sudo should ignore '.' or '' in $PATH... no
checking whether to send mail when a user is not in sudoers... yes
checking whether to send mail when user listed but not for this host... no
checking whether to send mail when a user tries a disallowed command... no
checking who should get the mail that sudo sends... root
checking for bad password prompt... Password:
checking for bad password message... Sorry, try again.
checking whether to expect fully qualified hosts in sudoers... no
checking for umask programs should be run with... 0022
checking for default user to run commands as... root
checking for editor that visudo should use... vi
checking whether to obey EDITOR and VISUAL environment variables... no
checking number of tries a user gets to enter their password... 3
checking time in minutes after which sudo will ask for a password again... 5
checking time in minutes after the password prompt will time out... 5
checking whether to use per-tty ticket files... no
checking whether to include insults... no
checking whether to override the user's path... no
checking whether to get ip addresses from the network interfaces... yes
checking whether stow should be used... no
checking whether to do user authentication by default... yes
checking whether to disable running the mailer as root... no
checking whether to disable shadow password support... no
checking whether root should be allowed to use sudo... yes
checking whether to log the hostname in the log file... no
checking whether to invoke a shell if sudo is given no arguments... no
checking whether to set $HOME to target user in shell mode... no
checking whether to disable 'command not found' messages... no
checking for egrep... egrep
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
#

Answer 1

I found the solution myself and will shortly summarize it here to complete the thread.
(1) Use GNU as and non-GNU ld, so add "--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld --with-ld=/usr/ccs/bin/ld" to the configure command line. After I worked this out I found it noted on the build instruction website, RTFM proved to be useful again. :-)
(2) At some point the compilation aborted because directory stage3-gcc could not be found, so I had to do "ln -s stage3-i386-pc-solaris2.10 stage3-gcc". Maybe this can be avoided with some other configure options, but this workaround was fine for me.
(3) In order to use my own versions of gmp and mpfr, I had to add their library directory to the LD_LIBRARY_PATH environment variable (--with-gmp= and --with-mpfr= are not sufficient).
Kind regards,
Christian