On Fri, 15 Jul 2022, 19:11 Daniel Santos via Gcc-help, <gcc-help@xxxxxxxxxxx>
wrote:
> Hello,
>
> I downloader gcc-4.9.4 sources and did a ./configure just to see what it
> was the output.
>
> bash-2.05$ cd ../gcc-4.9.4
> bash-2.05$ ./configure
> configure: loading cache /dev/null
> ./configure: ./configure:: No such file or directory
> checking build system type... sparc-sun-solaris2.9
> checking host system type... sparc-sun-solaris2.9
> checking target system type... sparc-sun-solaris2.9
> checking for a BSD-compatible install... ./install-sh -c
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for gawk... no
> checking for mawk... no
> checking for nawk... nawk
> checking for libatomic support... yes
> checking for libcilkrts support... no
> checking for libitm support... yes
> checking for libsanitizer support... no
> checking for libvtv support... no
> checking for gcc... gcc
> checking for C compiler default output file name...
> configure: error: in `/export/home/dlsa/code/gcc-4.9.4':
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
>
> In config.log I have the following :
>
> configure:4249: $? = 0
> configure:4238: gcc -v >&5
> Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.6/specs
> Configured with: ../configure --with-as=/usr/ccs/bin/as
> --with-ld=/usr/ccs/bin/ld --enable-shared --enable-languages=c,c++,f77
> Thread model: posix
> gcc version 3.4.6
> configure:4249: $? = 0
> configure:4238: gcc -V >&5
> gcc: `-V' option must have argument
> configure:4249: $? = 1
> configure:4238: gcc -qversion >&5
> gcc: unrecognized option `-qversion'
> gcc: no input files
> configure:4249: $? = 1
> configure:4269: checking for C compiler default output file name
> configure:4291: gcc conftest.c >&5
> gcc: installation problem, cannot exec `cc1': No such file or directory
> configure:4295: $? = 1
> configure:4332: result:
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL ""
> | /* end confdefs.h. */
> |
> | int
> | main ()
> | {
> |
> | ;
> | return 0;
> | }
> configure:4338: error: in `/export/home/dlsa/code/gcc-4.9.4':
> configure:4342: error: C compiler cannot create executables
> See `config.log' for more details.
>
> Most notably I saw the error : gcc: installation problem, cannot exec
> `cc1': No such file or directory
> But isn’t cc1 the SUN C compiler ?
No, you're thinking of cc.
cc1 is GCC's C compiler. Your GCC installation is broken if the 'gcc'
driver cannot find its own 'cc1' executable.
I don’t have it.
>
> Also, to see the documentation I installed tetex on the machine and then
> did a texi2html install.texi and got :
>
> bash-2.05$ export PATH=/usr/local/teTeX/bin/sparc-sun-solaris2.9/:$PATH
> bash-2.05$ pwd
> /export/home/dlsa/code/gcc-4.9.4/gcc/doc
> bash-2.05$ texi2html install.texi
> *** Can't find gcc-common.texi, skipping (l. 10)
> ** empty document
> bash-2.05$
>
> Any help appreciated.
>
> Thanks,
> Regards
> Daniel Santos
>
>
>
> > On 14 Jul 2022, at 19:50, Rainer Orth <ro@xxxxxxxxxxxxxxxxxxxxxxxx>
> wrote:
> >
> > Hi Daniel,
> >
> >> As to switching to gcc 4.9, can my currently installed gcc 3.4.6 build
> it ?
> >
> > as documented in install.texi (you absolute need to check it!), GCC 4.9
> > requires a ISO C++98 compiler, so GC 3.4.6 should be good. If all else
> > fails, you need to take some intermediate step (like GCC 4.7 which only
> > needed an ISO C89 compiler).
> >
> >> While sticking to the 3.4.6 version, I removed the solaris ld out of the
> >
> > Don't mess around with the installed /usr/ccs/bin/ld. Just pass
> > --with-ld=<your desired ld> (and --with-gnu-ld or --without-gnu-ld as
> > needed.
> >
> >> way and am building it with gnu ld.
> >
> > Again: why are you so adamant on using GNU ld here? Solaris ld works
> > way better.
> >
> >> Right now I have the following error :
> >>
> >> rm -f libv3test.a
> >> ar cru libv3test.a testsuite_abi.o testsuite_allocator.o
> testsuite_hooks.o
> >> ranlib libv3test.a
> >> touch testsuite_wchar_t
> >>
> /export/home/dlsa/code/gcc-3.4.6/libstdc++-v3/scripts/create_testsuite_files
> \
> >> /export/home/dlsa/code/gcc-3.4.6/libstdc++-v3/testsuite `${PWDCMD-pwd}`
> >> /bin/ksh:
> >>
> /export/home/dlsa/code/gcc-3.4.6/libstdc++-v3/scripts/create_testsuite_files:
> >> cannot execute
> >
> > That script hardcodes /bin/sh which on Solaris 9 probably isn't able to
> > execute that script. The invocation should be prefixed with $(SHELL)
> > (initialized from $CONFIG_SHELL) instead.
> >
> > I'm pretty certain issues like this have been resolved for GCC 4.9/4.8,
> > so you'd better not bother with GCC 3.4 anymore.
> >
> > Rainer
> >
> > --
> >
> -----------------------------------------------------------------------------
> > Rainer Orth, Center for Biotechnology, Bielefeld University
>
>
