From: Daniel Santos <daniel.dlds@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Compiling gcc-3.4.6 on sparc Solaris 9
Date: Sat, 16 Jul 2022 19:54:04 +0100 [thread overview]
Message-ID: <D43B90B2-7FB5-41BC-960F-50842841B5FB@gmail.com> (raw)
In-Reply-To: <CAH6eHdQdh8KtqiFSJ-u=Xx4iGk+NDvDjSzUamuUsQh-MFf-upw@mail.gmail.com>
Hello,
So I re-installed the gcc 3.4.6 from sunfkeeware packages. I am now able to do ./configure on the gcc base directory.
I got gmp-4.3.2, mpfr-2.4.2 and mpc-1.0.1 sources because gcc depends on them.
I compiled gmp-4.3.2 and it finished. I then did a ‘make check’ and at the end of the output i got :
make check-TESTS
make[4]: Entering directory `/export/home/dlsa/code/gmp-4.3.2/tests'
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-bswap: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-bswap
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-constants: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-constants
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-count_zeros: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-count_zeros
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-gmpmax: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-gmpmax
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-hightomask: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-hightomask
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-modlinv: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-modlinv
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-popc: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-popc
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-parity: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-parity
ld.so.1: /export/home/dlsa/code/gmp-4.3.2/tests/.libs/t-sub: fatal: /usr/local/lib/libgcc_s.so.1: wrong ELF class: ELFCLASS32
FAIL: t-sub
====================================
9 of 9 tests failed
Please report to gmp-bugs@gmplib.org
====================================
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/export/home/dlsa/code/gmp-4.3.2/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/export/home/dlsa/code/gmp-4.3.2/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/export/home/dlsa/code/gmp-4.3.2/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/export/home/dlsa/code/gmp-4.3.2'
make: *** [check] Error 2
Which probably means that the gcc version I have installed is 32 bit. Am I correct ?
Can it be used to build a 64 bit 4.9.4 gcc ?
Thanks,
Regards
Daniel Santos
> On 15 Jul 2022, at 20:08, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
>
>
> On Fri, 15 Jul 2022, 19:11 Daniel Santos via Gcc-help, <gcc-help@gcc.gnu.org <mailto:gcc-help@gcc.gnu.org>> 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@cebitec.uni-bielefeld.de <mailto:ro@cebitec.uni-bielefeld.de>> 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
>
next prev parent reply other threads:[~2022-07-16 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 18:54 Daniel Santos
2022-07-13 19:47 ` Jonathan Wakely
2022-07-14 8:18 ` Rainer Orth
2022-07-14 18:40 ` Daniel Santos
2022-07-14 18:50 ` Jonathan Wakely
2022-07-14 18:50 ` Rainer Orth
2022-07-15 18:10 ` Daniel Santos
2022-07-15 19:08 ` Jonathan Wakely
2022-07-16 18:54 ` Daniel Santos [this message]
2022-07-17 19:40 ` Daniel Santos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D43B90B2-7FB5-41BC-960F-50842841B5FB@gmail.com \
--to=daniel.dlds@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).