RE: 3.4.0 on solaris fails on install

RE: 3.4.0 on solaris fails on install

[lrtaylor]

No, the normal and recommend way is more like this:

unzip gcc into /junk
cd /junk
mkdir obj
cd obj
../gcc*/configure BLAH
make bootstrap
make install

The obj directory is not supposed to be in or anywhere under the source
directory.

Cheers,
Lyle
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of J.D. Bronson
Sent: Wednesday, April 21, 2004 5:31 PM
To: Alexandre Oliva
Cc: gcc-help@gcc.gnu.org
Subject: Re: 3.4.0 on solaris fails on install

I will try this. However, I never had any issues until just now.

Usually I do this :

unzip gcc into /junk

cd /junk/gcc*
mkdir obj
cd obj
../configure BLAH
make bootstrap
make install

isnt that that the normal and recommended way?

RE: 3.4.0 on solaris fails on install

[J.D. Bronson]

At 06:34 PM 4/21/2004, lrtaylor@micron.com wrote:
>No, the normal and recommend way is more like this:
>
>unzip gcc into /junk
>cd /junk
>mkdir obj
>cd obj
>../gcc*/configure BLAH
>make bootstrap
>make install
>
>The obj directory is not supposed to be in or anywhere under the source
>directory.
>
>Cheers,
>Lyle

thank you. I am trying this on a 2nd solaris machine.
my FreeBSD 5.2.1 install was a complete success!






-- 
J.D. Bronson
Aurora Health Care // Information Services // Milwaukee, WI USA
Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282

3.4.0 on solaris fails on install

[J.D. Bronson]

I used a precompild gcc 2.95.3 and build gcc 3.4.0 just fine.
However the install fails!

Built as:
../configure --with-as=/usr/local/bin/as \
--with-ld=/usr/local/bin/ld --disable-nls --enable-threads \
--enable-shared --enable-multilib --with-cpu=pentium4 \
--enable-languages=c,c++,f77 \

Then I try to install after successful build:
..
...
make[3]: Leaving directory `/usr/temp/gcc-3.4.0/obj/i386-pc-solaris2.10/libf2c'
make[2]: Leaving directory `/usr/temp/gcc-3.4.0/obj/i386-pc-solaris2.10/libf2c'
make[1]: Leaving directory `/usr/temp/gcc-3.4.0/obj'

# make install
/bin/sh ../mkinstalldirs /usr/local /usr/local
make[1]: Entering directory `/usr/temp/gcc-3.4.0/obj/gcc'
if [ -f specs.ready ] ; then \
         true; \
else \
         echo timestamp > specs.ready; \
fi
/bin/sh ../../gcc/mkinstalldirs /usr/local/lib/gcc/i386-pc-solaris2.10/3.4.0
mkdir -p -- /usr/local/lib/gcc/i386-pc-solaris2.10/3.4.0
/bin/sh ../../gcc/mkinstalldirs 
/usr/local/libexec/gcc/i386-pc-solaris2.10/3.4.0
mkdir -p -- /usr/local/libexec/gcc/i386-pc-solaris2.10/3.4.0
/bin/sh ../../gcc/mkinstalldirs /usr/local/bin
/bin/sh ../../gcc/mkinstalldirs /usr/local/include
/bin/sh ../../gcc/mkinstalldirs /usr/local/info
/bin/sh ../../gcc/mkinstalldirs /usr/local/lib
/bin/sh ../../gcc/mkinstalldirs /usr/local/man/man1
/bin/sh ../../gcc/mkinstalldirs /usr/local/man/man7
rm -f /usr/local/bin/g++
../install-sh -c g++ /usr/local/bin/g++
make[1]: ../install-sh: Command not found
make[1]: [c++.install-common] Error 127 (ignored)
chmod a+x /usr/local/bin/g++
chmod: WARNING: can't access /usr/local/bin/g++
make[1]: [c++.install-common] Error 1 (ignored)
rm -f /usr/local/bin/c++
( cd /usr/local/bin && \
       ln g++ c++ )
ln: cannot access g++
make[1]: [c++.install-common] Error 2 (ignored)
if [ -f cc1plus ] ; then \
   if [ -f g++-cross ] ; then \
     if [ -d 
/usr/local/lib/gcc/i386-pc-solaris2.10/3.4.0/../../../../i386-pc-solaris2.10/bin/. 
] ; then \
       rm -f 
/usr/local/lib/gcc/i386-pc-solaris2.10/3.4.0/../../../../i386-pc-solaris2.10/bin/g++; 
\
       ../install-sh -c g++-cross 
/usr/local/lib/gcc/i386-pc-solaris2.10/3.4.0/../../../../i386-pc-solaris2.10/bin/g++; 
\
       rm -f 
/usr/local/lib/gcc/i386-pc-solaris2.10/3.4.0/../../../../i386-pc-solaris2.10/bin/c++; 
\
       ( cd 
/usr/local/lib/gcc/i386-pc-solaris2.10/3.4.0/../../../../i386-pc-solaris2.10/bin 
&& \
         ln g++ c++ ); \
     else true; fi; \
   else \
     rm -f /usr/local/bin/i386-pc-solaris2.10-g++; \
     ( cd /usr/local/bin && \
       ln g++ i386-pc-solaris2.10-g++ ); \
     rm -f /usr/local/bin/i386-pc-solaris2.10-c++; \
     ( cd /usr/local/bin && \
       ln c++ i386-pc-solaris2.10-c++ ); \
   fi ; \
fi
ln: cannot access g++
ln: cannot access c++
make[1]: [c++.install-common] Error 2 (ignored)
if [ -f f771 ] ; then \
   rm -f /usr/local/bin/g77; \
   ../install-sh -c g77 /usr/local/bin/g77; \
   chmod a+x /usr/local/bin/g77; \
else true; fi
/bin/sh: ../install-sh: not found
chmod: WARNING: can't access /usr/local/bin/g77
make[1]: [f77.install-common] Error 1 (ignored)
for file in cc1  cc1plus f771; do \
   if [ -f $file ] ; then \
     rm -f /usr/local/libexec/gcc/i386-pc-solaris2.10/3.4.0/$file; \
     ../install-sh -c $file 
/usr/local/libexec/gcc/i386-pc-solaris2.10/3.4.0/$file; \
   else true; \
   fi; \
done
/bin/sh: ../install-sh: not found
/bin/sh: ../install-sh: not found
/bin/sh: ../install-sh: not found
make[1]: *** [install-common] Error 1
make[1]: Leaving directory `/usr/temp/gcc-3.4.0/obj/gcc'


Please help!





-- 
J.D. Bronson
Aurora Health Care // Information Services // Milwaukee, WI USA
Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282

Re: 3.4.0 on solaris fails on install

[Alexandre Oliva]

On Apr 21, 2004, "J.D. Bronson" <jd@wixb.com> wrote:

> I used a precompild gcc 2.95.3 and build gcc 3.4.0 just fine.
> However the install fails!

Ugh.  INSTALL_PROGRAM is passed from the top level to all subdirs, so
it doesn't work when srcdir is relative.  I suspect this is why we say
we don't support objdir as a subdir of srcdir in the installation
documentation: people will tend to use relative pathnames for that.

I suppose it will work if you run

make install INSTALL_PROGRAM=/full/path/to/src/install-sh

Please file a bug report on this, such that this doesn't get lost.  At
the very least, the documentation should be changed to make it clear
that relative pathnames are not expected to work.

Thanks,

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

Re: 3.4.0 on solaris fails on install

[J.D. Bronson]

At 05:46 PM 4/21/2004, Alexandre Oliva wrote:
>On Apr 21, 2004, "J.D. Bronson" <jd@wixb.com> wrote:
>
> > I used a precompild gcc 2.95.3 and build gcc 3.4.0 just fine.
> > However the install fails!
>
>Ugh.  INSTALL_PROGRAM is passed from the top level to all subdirs, so
>it doesn't work when srcdir is relative.  I suspect this is why we say
>we don't support objdir as a subdir of srcdir in the installation
>documentation: people will tend to use relative pathnames for that.
>
>I suppose it will work if you run
>
>make install INSTALL_PROGRAM=/full/path/to/src/install-sh
>
>Please file a bug report on this, such that this doesn't get lost.  At
>the very least, the documentation should be changed to make it clear
>that relative pathnames are not expected to work.
>
>Thanks,
>
>--
>Alexandre Oliva             http://www.ic.unicamp.br/~oliva/

I will try this. However, I never had any issues until just now.

Usually I do this :

unzip gcc into /junk

cd /junk/gcc*
mkdir obj
cd obj
../configure BLAH
make bootstrap
make install

isnt that that the normal and recommended way?

..I tried this same way (above) on my FreeBSD 5.2.1 system and it built 
100% fine. So could this be a solaris issue? - I am running solaris10 beta...








-- 
J.D. Bronson
Aurora Health Care // Information Services // Milwaukee, WI USA
Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282