Compilation problem in Dynix/ptx

biswapesh.chattopadhyay@bt.com biswapesh.chattopadhyay@bt.com
Mon Dec 11 09:34:00 GMT 2000


OK - thanks to all concerned, I finally managed to build GCC (c, c++) on
Dynix/ptx i386 V4.4.8. I found this excellent post by Andrew Gaylard (thanks
Andrew !) at http://gcc.gnu.org/ml/gcc-help/2000-06/msg00088.html (sorry for
not searching the ML before :-()
Couple of points:

a) There is no need to build 2.8.1 to build 2.95.2 succesfully.
b) Is it possible to put a link the above message (modified to reflect point
(a) above) somewhere on the GCC home page ? This will go a long way towards
helping people compile GCC on not-so-common platforms.

- Biswa.

> -----Original Message-----
> From: biswapesh.chattopadhyay@bt.com
> [ mailto:biswapesh.chattopadhyay@bt.com ]
> Sent: 11 December 2000 16:09
> To: gcc@gcc.gnu.org
> Subject: RE: Compilation problem in Dynix/ptx
> 
> 
> Well, I thought (a) would work but now I get something 
> completely different:
> --------------------------------------------------------------
> --------------
> ----
> for name in _muldi3 _divdi3 _moddi3 _udivdi3 _umoddi3 _negdi2 _lshrdi3
> _ashldi3 _ashrdi3 _ffsdi2 _udiv_w_sdiv _udivmoddi4 _cm
> pdi2 _ucmpdi2 _floatdidf _floatdisf _fixunsdfsi _fixunssfsi 
> _fixunsdfdi
> _fixdfdi _fixunssfdi _fixsfdi _fixxfdi _fixunsxfdi _f
> loatdixf _fixunsxfsi _fixtfdi _fixunstfdi _floatditf 
> __gcc_bcmp _varargs
> __dummy _eprintf _bb _shtab _clear_cache _trampoline
>  __main _exit _ctors _pure; \
> do \
>   echo ${name}; \
>   ./xgcc 
> -B/var/opt/spool/out/em/biswa/gnu/i386-sequent-sysv4/bin/ -B./
> -I/var/opt/spool/out/em/biswa/gnu/i386-sequent-sysv4/
> include -O2   -DIN_GCC     -g -I./include  -fPIC -g1  -DIN_LIBGCC2
> -D__GCC_FLOAT_NOT_NEEDED   -I. -I../../gcc-2.95.2/gcc -I..
> /../gcc-2.95.2/gcc/config -I../../gcc-2.95.2/gcc/../include 
> -c -DL${name} \
>        ../../gcc-2.95.2/gcc/libgcc2.c -o ${name}.o; \
>   if [ $? -eq 0 ] ; then true; else exit 1; fi; \
>   ` if [ -f
> /var/opt/spool/out/email/biswa/gnu/src/gcc-build/gcc/../binuti
> ls/ar ] ; then
> echo /var/opt/spool/out/email/biswa/
> gnu/src/gcc-build/gcc/../binutils/ar ; else if [ 
> "i386-sequent-sysv4" =
> "i386-sequent-sysv4" ] ; then echo ar; else t='s,x,x,
> '; echo ar | sed -e $t ; fi; fi` rc tmplibgcc2.a ${name}.o; \
>   rm -f ${name}.o; \
> done
> _muldi3
> /var/opt/spool/out/em/biswa/gnu/i386-sequent-sysv4/bin/as: 
> unrecognized
> option `-no_0f_fix'
> make[2]: *** [libgcc2.a] Error 1
> make[2]: Leaving directory
> `/var/opt/spool/out/email/biswa/gnu/src/gcc-build/gcc'
> make[1]: *** [bootstrap] Error 2
> make[1]: Leaving directory
> `/var/opt/spool/out/email/biswa/gnu/src/gcc-build/gcc'
> make: *** [bootstrap] Error 2
> --------------------------------------------------------------
> --------------
> -------
> I must admit I'm really stumped this time :-(
> 
> Help!!
> - Biswa.
> 
> > -----Original Message-----
> > From: Robert Lipe [ mailto:robertlipe@usa.net ]
> > Sent: 11 December 2000 15:43
> > To: biswapesh.chattopadhyay@bt.com
> > Cc: gcc@gcc.gnu.org
> > Subject: Re: Compilation problem in Dynix/ptx
> > 
> > 
> > biswapesh.chattopadhyay@bt.com wrote:
> > 
> > > I'm getting the following error while compiling gcc-2.95.2 
> > (make bootstrap)
> > > (enable-languages="c++", uname -a='DYNIX/ptx hwcmcr1 4.0 
> > V4.4.8 i386'):
> > 
> > > -c `echo ../../gcc-2.95.2/gcc/collect2.c | sed 's,^\./,,'`
> > > "../../gcc-2.95.2/gcc/collect2.c", line 364: undefined 
> > symbol: _sys_siglist
> > > "../../gcc-2.95.2/gcc/collect2.c", line 364: cannot 
> > dereference non-pointer
> > > type
> > > "../../gcc-2.95.2/gcc/collect2.c", line 364: warning: improper
> > > pointer/integer combination: op "="
> > 
> > Options:
> >  * define NO_SYS_SIGLIST in your config file 
> >  * look for a system function name strsignal() (which you 
> > probably won't have) 
> >    and set HAVE_STRSIGNAL
> >  * Graft strsignal.c from current libiberty.
> > 
> > Given the actual _need_ for the target functionality (realistically,
> > it's only used to report detail in an internal error inside 
> collect2)
> > and since this is replaced in GCC3 anyway, I'd probably just stick a
> > NO_SYS_SIGLIST in my local copy of collect2.c and move on.
> > 
> > RJL
> > 
> 


More information about the Gcc mailing list