RE: GCC 3.2.3 on Solaris 2.7

RE: GCC 3.2.3 on Solaris 2.7

[Balaji Srinivasa]

> No, I don't think so, these are common and well-tested 
> options.  I'd tend to 
> think of a shell problem if you used /bin/sh, such problems are very 
> frequent on Solaris.
How do I tell it to use 'bash' or 'ksh'?

thx! 

Re: GCC 3.2.3 on Solaris 2.7

[Toon Moene]

Eric Botcazou wrote:

> I think we can't do much better than:
> 
> The Solaris 2 /bin/sh will often fail to configure libstdc++-v3, boehm-gc or 
> libjava. We therefore recommend to use the following sequence of commands to 
> bootstrap and install GCC:
> 
>         % CONFIG_SHELL=/bin/ksh
>         % export CONFIG_SHELL

Indeed - the fact that I'm on this mailing list saved my employer 
several man-days of debugging shell scripts again this time (same thing 
2 years ago).

Solaris 2.9's shell just doesn't like:

      [ "$AAP" ] && ! echo "$AAP" | grep XY

(it complained about "!: not found").

I knew I had to try to change the #!/bin/sh on the first line to 
#!/bin/ksh and - bingo, it worked !

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://gcc.gnu.org/fortran/ (under construction)

Re: GCC 3.2.3 on Solaris 2.7

[Eric Botcazou]

> I think the shell was the problem. In fact, the documentation
> should state that CONFIG_SHELL should always be exported, or,
> configure should take the SHELL value from the env.

I think we can't do much better than:

The Solaris 2 /bin/sh will often fail to configure libstdc++-v3, boehm-gc or 
libjava. We therefore recommend to use the following sequence of commands to 
bootstrap and install GCC:

        % CONFIG_SHELL=/bin/ksh
        % export CONFIG_SHELL
     
> After that was set, a complete rebuild was successful.

Nice.

> However, config.status still shows #!/bin/sh whatever is set.

Weird.  Good to know anyway.

-- 
Eric Botcazou

RE: GCC 3.2.3 on Solaris 2.7

[Balaji Srinivasa]

> 
> > 4. I built Python 2.1 for a 32 bit sample
> > 5. I built lsof 4.70 for a 64 bit sample
> > 6. They both built successfully and ran successfully.
> 
> Nice!
> 
> > I am thinking that these failures might be due to
> > (a) me setting --disable-libgcj
> > (b) me setting --enable-languages=c,c++,objc
> > and the building of the sparcv9 dirs.
> 
> No, I don't think so, these are common and well-tested 
> options.  I'd tend to 
> think of a shell problem if you used /bin/sh, such problems are very 
> frequent on Solaris.
> 
> > This did not happen on 2 other 32 bit builds.
> > 1. Solaris 2.6
> > 2. Linux 2.4
> 
> Sure, sparc-sun-solaris2.6 is not multilibed.
I think the shell was the problem. In fact, the documentation
should state that CONFIG_SHELL should always be exported, or,
configure should take the SHELL value from the env.

After that was set, a complete rebuild was successful.

However, config.status still shows #!/bin/sh whatever is set.

thx to Eric,
balaji

RE: GCC 3.2.3 on Solaris 2.7

[Balaji Srinivasa]

never mind. got it.

> -----Original Message-----
> From: Balaji Srinivasa 
> Sent: Friday, March 19, 2004 5:06 PM
> To: 'Eric Botcazou'
> Cc: gcc@gcc.gnu.org
> Subject: RE: GCC 3.2.3 on Solaris 2.7
> 
> 
> 
> > No, I don't think so, these are common and well-tested 
> > options.  I'd tend to 
> > think of a shell problem if you used /bin/sh, such problems 
> are very 
> > frequent on Solaris.
> How do I tell it to use 'bash' or 'ksh'?
> 
> thx! 
> 

RE: GCC 3.2.3 on Solaris 2.7

[Balaji Srinivasa]

> 
> 
> > 4. I built Python 2.1 for a 32 bit sample
> > 5. I built lsof 4.70 for a 64 bit sample
> > 6. They both built successfully and ran successfully.
> 
> Nice!
> 
> > I am thinking that these failures might be due to
> > (a) me setting --disable-libgcj
> > (b) me setting --enable-languages=c,c++,objc
> > and the building of the sparcv9 dirs.
> 
> No, I don't think so, these are common and well-tested 
> options.  I'd tend to 
> think of a shell problem if you used /bin/sh, such problems are very 
> frequent on Solaris.
Can I just change SHELL=/bin/bash in configure.in, reconfigure
and bootstrap? I cannot see where I can pass it to configure?

Re: GCC 3.2.3 on Solaris 2.7

[Eric Botcazou]

> 4. I built Python 2.1 for a 32 bit sample
> 5. I built lsof 4.70 for a 64 bit sample
> 6. They both built successfully and ran successfully.

Nice!

> I am thinking that these failures might be due to
> (a) me setting --disable-libgcj
> (b) me setting --enable-languages=c,c++,objc
> and the building of the sparcv9 dirs.

No, I don't think so, these are common and well-tested options.  I'd tend to 
think of a shell problem if you used /bin/sh, such problems are very 
frequent on Solaris.

> This did not happen on 2 other 32 bit builds.
> 1. Solaris 2.6
> 2. Linux 2.4

Sure, sparc-sun-solaris2.6 is not multilibed.

-- 
Eric Botcazou

RE: GCC 3.2.3 on Solaris 2.7

[Balaji Srinivasa]

> > OK. This is what I also concluded. So I kicked of a build (twice)
> > and it churned for a while. It does not complete well.
> 
> Which bootstrap compiler?
gcc 2.95.2 32 bit built on 2.5.1
> 
> > ---------config.status------------
> > #!/bin/sh
> 
> Nah :-)  /bin/sh is not reliable as a configure shell.  See the 
> Solaris-specific release notes.
I am surprised. I am a bash user, and that is what it should be picking
up...
> 
> > # This file was generated automatically by configure.  Do not edit.
> > # This directory was configured as follows:
> > ../configure
> > --with-gcc-version-trigger=/home/balaji/gcc-3.2.3/gcc/version.c
> > --host=sparc-sun-solaris2.7 --prefix=/home/balaji/gcc-64
> > --with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as --disable-libgcj
> > --disable-nls --enable-languages=c,c++,objc --norecursion
> > # using "mh-frag"
> 
> > gmake[4]: Entering directory
> > 
> `/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/sparcv9
> /libiberty
> '
> > gmake[4]: *** No rule to make target `all'.  Stop.
> 
> Just to be sure: your Solaris 7 kernel is 64-bit capable, right?
Yes.


Here is more info:
1. Since it was past boostrap (i.e bootstrap was complete),
I decided that this failure might not be very bad.
2. I attempted an install, which went through all the steps
and failed at the same location.
3. However, the installed files seemed complete to me, so
I tried to build a few apps.
4. I built Python 2.1 for a 32 bit sample
5. I built lsof 4.70 for a 64 bit sample
6. They both built successfully and ran successfully.

I am thinking that these failures might be due to 
(a) me setting --disable-libgcj
(b) me setting --enable-languages=c,c++,objc
and the building of the sparcv9 dirs.

This did not happen on 2 other 32 bit builds.
1. Solaris 2.6
2. Linux 2.4

I am in the process of building for AIX 4.3.3 which does
support 64 bit exe's, and it is going well so far.


To conclude, I am not sure what caused it, I am not sure
if I am only adding noise, but I will keep everyone posted
if I have progress.

In the meantime, if anyone can point me to something, it
will be great. 

In the meantime, I thank Eric for his help.

thx
balaji

Re: GCC 3.2.3 on Solaris 2.7

[Eric Botcazou]

> OK. This is what I also concluded. So I kicked of a build (twice)
> and it churned for a while. It does not complete well.

Which bootstrap compiler?

> ---------config.status------------
> #!/bin/sh

Nah :-)  /bin/sh is not reliable as a configure shell.  See the 
Solaris-specific release notes.

> # This file was generated automatically by configure.  Do not edit.
> # This directory was configured as follows:
> ../configure
> --with-gcc-version-trigger=/home/balaji/gcc-3.2.3/gcc/version.c
> --host=sparc-sun-solaris2.7 --prefix=/home/balaji/gcc-64
> --with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as --disable-libgcj
> --disable-nls --enable-languages=c,c++,objc --norecursion
> # using "mh-frag"

> gmake[4]: Entering directory
> `/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/sparcv9/libiberty
'
> gmake[4]: *** No rule to make target `all'.  Stop.

Just to be sure: your Solaris 7 kernel is 64-bit capable, right?

-- 
Eric Botcazou

RE: GCC 3.2.3 on Solaris 2.7

[Balaji Srinivasa]

> > My bigger question is this:
> > 1. I want a compiler that can build me 32 & 64 bit executables
> > on single box.
> > 2. My base level support is Solaris 2.6
> > Can I even do this?
> 
> I think you need 2 compilers in any cases, unless you want to 
> hack GCC 
> itself.
> 
> > 1. Do I need a version hosted on 2.6 for all 32 bits
> > 2. A version hosted on a 64bit 2.7 (though it is 32 bit)
> > for all 64 bit output?
> >
> > I need to support 32 bits 2.6->2.9, 64 bits 2.7->2.9
> 
> Then build a native 32-bit compiler on the Solaris 2.6 
> machine and a native 
> 32/64-bit compiler on the Solaris 7 machine.  This would 
> greatly simplify 
> everything.
OK. This is what I also concluded. So I kicked of a build (twice)
and it churned for a while. It does not complete well. 

Here are my usual files...
Pls let me know if one needs more data.

thx
balaji

---------config.status------------
#!/bin/sh
# This file was generated automatically by configure.  Do not edit.
# This directory was configured as follows:
../configure
--with-gcc-version-trigger=/home/balaji/gcc-3.2.3/gcc/version.c
--host=sparc-sun-solaris2.7 --prefix=/home/balaji/gcc-64
--with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as --disable-libgcj
--disable-nls --enable-languages=c,c++,objc --norecursion 
# using "mh-frag"

---------compile error------------

/home/balaji/gcc-3.2.3/objdir-64/gcc/xgcc
-B/home/balaji/gcc-3.2.3/objdir-64/gcc/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/bin/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/lib/ -isystem
/home/balaji/gcc-64/sparc-sun-solaris2.7/include -c -DHAVE_CONFIG_H -O2
-g -O2 -I. -I../../../libiberty/../include  -W -Wall -Wtraditional
-pedantic ../../../libiberty/sigsetmask.c
if [ x"" != x ]; then \
  /home/balaji/gcc-3.2.3/objdir-64/gcc/xgcc
-B/home/balaji/gcc-3.2.3/objdir-64/gcc/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/bin/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/lib/ -isystem
/home/balaji/gcc-64/sparc-sun-solaris2.7/include -c -DHAVE_CONFIG_H -O2
-g -O2 -I. -I../../../libiberty/../include  -W -Wall -Wtraditional
-pedantic  ../../../libiberty/vasprintf.c -o pic/vasprintf.o; \
else true; fi
/home/balaji/gcc-3.2.3/objdir-64/gcc/xgcc
-B/home/balaji/gcc-3.2.3/objdir-64/gcc/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/bin/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/lib/ -isystem
/home/balaji/gcc-64/sparc-sun-solaris2.7/include -c -DHAVE_CONFIG_H -O2
-g -O2 -I. -I../../../libiberty/../include  -W -Wall -Wtraditional
-pedantic ../../../libiberty/vasprintf.c
rm -f libiberty.a pic/libiberty.a
ar rc libiberty.a \
  regex.o cplus-dem.o cp-demangle.o md5.o alloca.o argv.o choose-temp.o
concat.o dyn-string.o fdmatch.o fibheap.o floatformat.o fnmatch.o
getopt.o getopt1.o getpwd.o getruntime.o hashtab.o hex.o lbasename.o
make-temp-file.o objalloc.o obstack.o partition.o pexecute.o
safe-ctype.o sort.o spaces.o splay-tree.o strerror.o strsignal.o
ternary.o xatexit.o xexit.o xmalloc.o xmemdup.o xstrdup.o xstrerror.o
asprintf.o mkstemps.o setenv.o sigsetmask.o vasprintf.o
true libiberty.a
if [ x"" != x ]; then \
  cd pic; \
  ar rc libiberty.a \
    regex.o cplus-dem.o cp-demangle.o md5.o alloca.o argv.o
choose-temp.o concat.o dyn-string.o fdmatch.o fibheap.o floatformat.o
fnmatch.o getopt.o getopt1.o getpwd.o getruntime.o hashtab.o hex.o
lbasename.o make-temp-file.o objalloc.o obstack.o partition.o pexecute.o
safe-ctype.o sort.o spaces.o splay-tree.o strerror.o strsignal.o
ternary.o xatexit.o xexit.o xmalloc.o xmemdup.o xstrdup.o xstrerror.o
asprintf.o mkstemps.o setenv.o sigsetmask.o vasprintf.o; \
  true libiberty.a; \
  cd ..; \
else true; fi
rm -f needed-list; touch needed-list; \
for f in atexit calloc memchr memcmp memcpy memmove memset rename strchr
strerror strncmp strrchr strstr strtol strtoul tmpnam vfprintf vprintf
vfork waitpid bcmp bcopy bzero; do \
  for g in asprintf.o mkstemps.o setenv.o sigsetmask.o vasprintf.o ; do
\
    case "$g" in \
      *$f*) echo $g >> needed-list ;; \
    esac; \
  done; \
done
echo regex.o cplus-dem.o cp-demangle.o md5.o alloca.o argv.o
choose-temp.o concat.o dyn-string.o fdmatch.o fibheap.o floatformat.o
fnmatch.o getopt.o getopt1.o getpwd.o getruntime.o hashtab.o hex.o
lbasename.o make-temp-file.o objalloc.o obstack.o partition.o pexecute.o
safe-ctype.o sort.o spaces.o splay-tree.o strerror.o strsignal.o
ternary.o xatexit.o xexit.o xmalloc.o xmemdup.o xstrdup.o xstrerror.o >
required-list
gmake[3]: Entering directory
`/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/libiberty/testsui
te'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory
`/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/libiberty/testsui
te'
gmake[3]: Entering directory
`/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/libiberty'
if [ -z "sparcv9" ]; then \
  true; \
else \
  rootpre=`pwd`/; export rootpre; \
  srcrootpre=`cd ../../../libiberty; pwd`/; export srcrootpre; \
  lib=`echo ${rootpre} | sed -e 's,^.*/\([^/][^/]*\)/$,\1,'`; \
  compiler="/home/balaji/gcc-3.2.3/objdir-64/gcc/xgcc
-B/home/balaji/gcc-3.2.3/objdir-64/gcc/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/bin/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/lib/ -isystem
/home/balaji/gcc-64/sparc-sun-solaris2.7/include"; \
  for i in `${compiler} --print-multi-lib 2>/dev/null`; do \
    dir=`echo $i | sed -e 's/;.*$//'`; \
    if [ "${dir}" = "." ]; then \
      true; \
    else \
      if [ -d ../${dir}/${lib} ]; then \
        flags=`echo $i | sed -e 's/^[^;]*;//' -e 's/@/ -/g'`; \
        if (cd ../${dir}/${lib}; gmake "AR=ar" "AR_FLAGS=rc"
"CC=/home/balaji/gcc-3.2.3/objdir-64/gcc/xgcc
-B/home/balaji/gcc-3.2.3/objdir-64/gcc/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/bin/
-B/home/balaji/gcc-64/sparc-sun-solaris2.7/lib/ -isystem
/home/balaji/gcc-64/sparc-sun-solaris2.7/include" "CFLAGS=-O2 -g -O2"
"DESTDIR=" "LIBCFLAGS=-O2 -g -O2" "EXTRA_OFILES=" "HDEFINES="
"INSTALL=/bin/sh /home/balaji/gcc-3.2.3/install-sh -c"
"INSTALL_DATA=/bin/sh /home/balaji/gcc-3.2.3/install-sh -c -m 644"
"INSTALL_PROGRAM=/bin/sh /home/balaji/gcc-3.2.3/install-sh -c "
"LDFLAGS=" "LOADLIBES=" "RANLIB=true" "SHELL=/bin/sh"
"prefix=/home/balaji/gcc-64" "exec_prefix=/home/balaji/gcc-64"
"libdir=/home/balaji/gcc-64/lib"
"libsubdir=/home/balaji/gcc-64/lib/gcc-lib/sparc-sun-solaris2.7/3.2.3"
"tooldir=/home/balaji/gcc-64/sparc-sun-solaris2.7" \
                        CFLAGS="-O2 -g -O2 ${flags}" \
                        prefix="/home/balaji/gcc-64" \
                        exec_prefix="/home/balaji/gcc-64" \
                        GCJFLAGS=" ${flags}" \
                        CXXFLAGS="-g -O2 ${flags}" \
                        LIBCFLAGS="-O2 -g -O2 ${flags}" \
                        LIBCXXFLAGS="-g -O2 -fno-implicit-templates
${flags}" \
                        LDFLAGS=" ${flags}" \
                        DESTDIR="" \
                        all); then \
          true; \
        else \
          exit 1; \
        fi; \
      else true; \
      fi; \
    fi; \
  done; \
fi
gmake[4]: Entering directory
`/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/sparcv9/libiberty
'
gmake[4]: *** No rule to make target `all'.  Stop.
gmake[4]: Leaving directory
`/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/sparcv9/libiberty
'
gmake[3]: *** [multi-do] Error 1
gmake[3]: Leaving directory
`/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/libiberty'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/home/balaji/gcc-3.2.3/objdir-64/sparc-sun-solaris2.7/libiberty'
gmake[1]: *** [all-target-libiberty] Error 2
gmake[1]: Leaving directory `/home/balaji/gcc-3.2.3/objdir-64'
gmake: *** [bootstrap] Error 2

Re: GCC 3.2.3 on Solaris 2.7

[Eric Botcazou]

> My bigger question is this:
> 1. I want a compiler that can build me 32 & 64 bit executables
> on single box.
> 2. My base level support is Solaris 2.6
> Can I even do this?

I think you need 2 compilers in any cases, unless you want to hack GCC 
itself.

> 1. Do I need a version hosted on 2.6 for all 32 bits
> 2. A version hosted on a 64bit 2.7 (though it is 32 bit)
> for all 64 bit output?
>
> I need to support 32 bits 2.6->2.9, 64 bits 2.7->2.9

Then build a native 32-bit compiler on the Solaris 2.6 machine and a native 
32/64-bit compiler on the Solaris 7 machine.  This would greatly simplify 
everything.

> BTW, I plan to use /usr/ccs/bin/as and /usr/ccs/bin/ld for all my needs.

Fine, that's what I use every day.  Be sure to check the Solaris-specific GCC 
release notes though.

-- 
Eric Botcazou

RE: GCC 3.2.3 on Solaris 2.7

[Balaji Srinivasa]

> 
> > Yes. I cannot see why not...
> 
> Because GCC depends upon and applies certain transformations 
> to the header 
> files it was exposed to when built.  This may explain your problems.
OK, I am building a version of 3.2.3 without the sparcv9-sun-solaris2
set, and it seems like it is proceeding well. I am not sure what I
get out of this, but probably a 32 bit exe that can produce 64 bit
apps.

My bigger question is this:
1. I want a compiler that can build me 32 & 64 bit executables
on single box.
2. My base level support is Solaris 2.6
Can I even do this? 
Or ,
1. Do I need a version hosted on 2.6 for all 32 bits
2. A version hosted on a 64bit 2.7 (though it is 32 bit) 
for all 64 bit output?

I need to support 32 bits 2.6->2.9, 64 bits 2.7->2.9

BTW, I plan to use /usr/ccs/bin/as and /usr/ccs/bin/ld for all my needs.

thx!
balaji

Re: GCC 3.2.3 on Solaris 2.7

[Eric Botcazou]

> Yes. I cannot see why not...

Because GCC depends upon and applies certain transformations to the header 
files it was exposed to when built.  This may explain your problems.

-- 
Eric Botcazou

RE: GCC 3.2.3 on Solaris 2.7

[Balaji Srinivasa]

>> Now I am trying to use that to build a 32 bit gcc that can
>> generate 64 bit apps with the -m64 option.
>>
>> To do that, I am using a 64 bit Solaris 2.7 machine. I am
>> getting the following errors.

> Do you mean that you use on Solaris 7 the executable built on Solaris 2.6?  
> I'm not sure this can work for GCC.

Yes. I cannot see why not...

>> --with-gcc-version-trigger=/home/balaji/gcc-3.2.3/gcc/version.c
>> --host=sparcv9-sun-solaris2 --prefix=/home/balaji/gcc-64
>> --with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as --disable-libgcj
>> --disable-nls --enable-languages=c,c++,objc --norecursion
>> # using "mh-frag"

> --host=sparcv9-sun-solaris2 implies that you're trying to bootstrap a 64-bit 
> compiler, not a 32-bit one.  Passing sparc-sun-solaris2.7 is sufficient to 
> get a multi-arch 32/64-bit compiler.

I will try this. All I want is a 32 bit compiler that can produce a 64 bit executable.

thx
balaji