public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* failed compile
@ 1998-03-19  8:19 Jean-Pierre Radley
  1998-03-21 10:36 ` Jeffrey A Law
                   ` (3 more replies)
  0 siblings, 4 replies; 8+ messages in thread
From: Jean-Pierre Radley @ 1998-03-19  8:19 UTC (permalink / raw)
  To: EGCS Developers

SCO OpenServer 5.0.4
My last compilation was on March 10th, and it succeeded.

After a 'cvs update' today, compilation halts at this point:

  Configuring in libraries/libf2c
  loading cache ./config.cache
  /s/tools/egcs/libf2c/configure: syntax error at line 537: `<<' unexpected
  make: *** [configure-target-libf2c] Error 2


-- 
Jean-Pierre Radley <jpr@jpr.com>  XC/XT Custodian   Sysop, CompuServe SCOForum

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: failed compile
  1998-03-19  8:19 failed compile Jean-Pierre Radley
@ 1998-03-21 10:36 ` Jeffrey A Law
  1998-03-21 10:36 ` Joern Rennecke
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 8+ messages in thread
From: Jeffrey A Law @ 1998-03-21 10:36 UTC (permalink / raw)
  To: Jean-Pierre Radley; +Cc: EGCS Developers

  In message < 19980319111935.15836@jpr.com >you write:
  > SCO OpenServer 5.0.4
  > My last compilation was on March 10th, and it succeeded.
  > 
  > After a 'cvs update' today, compilation halts at this point:
  > 
  >   Configuring in libraries/libf2c
  >   loading cache ./config.cache
  >   /s/tools/egcs/libf2c/configure: syntax error at line 537: `<<' unexpected
  >   make: *** [configure-target-libf2c] Error 2
Did CVS report any conflicts when you updated?


Another way to check is to do an update in libf2c and see if it
reports something like

C configure

That means there's a conflict block in the configure file.


If this is the case, refer to the faq for the solution:-)

jeff

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: failed compile
  1998-03-19  8:19 failed compile Jean-Pierre Radley
  1998-03-21 10:36 ` Jeffrey A Law
@ 1998-03-21 10:36 ` Joern Rennecke
  1998-03-21 13:50   ` Jean-Pierre Radley
  1998-03-21 13:50 ` Martin von Loewis
  1998-03-21 13:50 ` Robert Lipe
  3 siblings, 1 reply; 8+ messages in thread
From: Joern Rennecke @ 1998-03-21 10:36 UTC (permalink / raw)
  To: Jean-Pierre Radley; +Cc: egcs

> SCO OpenServer 5.0.4
> My last compilation was on March 10th, and it succeeded.
> 
> After a 'cvs update' today, compilation halts at this point:
> 
>   Configuring in libraries/libf2c
>   loading cache ./config.cache
>   /s/tools/egcs/libf2c/configure: syntax error at line 537: `<<' unexpected
>   make: *** [configure-target-libf2c] Error 2

rm libf2c/configure and update it again.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: failed compile
  1998-03-19  8:19 failed compile Jean-Pierre Radley
                   ` (2 preceding siblings ...)
  1998-03-21 13:50 ` Martin von Loewis
@ 1998-03-21 13:50 ` Robert Lipe
  3 siblings, 0 replies; 8+ messages in thread
From: Robert Lipe @ 1998-03-21 13:50 UTC (permalink / raw)
  To: Jean-Pierre Radley, EGCS Developers

Jean-Pierre Radley wrote:

> After a 'cvs update' today, compilation halts at this point:
> 
>   Configuring in libraries/libf2c
>   loading cache ./config.cache
>   /s/tools/egcs/libf2c/configure: syntax error at line 537: `<<' unexpected
>   make: *** [configure-target-libf2c] Error 2

If you do a 'cvs status libf2c/configure', is the leading character a 'C'?

If so, this indicates you had a conflict during the update.   Since 
configure is a generated file, manually resolving conflicts in it is
pointless.  

If you have autoconf and related tools:
	cd libf2c; rm configure ; autoconf
else
	rm libf2c/configure ; cvs update libf2c/configure


RJL

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: failed compile
  1998-03-21 10:36 ` Joern Rennecke
@ 1998-03-21 13:50   ` Jean-Pierre Radley
  0 siblings, 0 replies; 8+ messages in thread
From: Jean-Pierre Radley @ 1998-03-21 13:50 UTC (permalink / raw)
  To: EGCS Developers

Joern Rennecke telecommunicated (on 20Mar):
| > SCO OpenServer 5.0.4
| > My last compilation was on March 10th, and it succeeded.
| > 
| > After a 'cvs update' today, compilation halts at this point:
| > 
| >   Configuring in libraries/libf2c
| >   loading cache ./config.cache
| >   /s/tools/egcs/libf2c/configure: syntax error at line 537: `<<' unexpected
| >   make: *** [configure-target-libf2c] Error 2
| 
| rm libf2c/configure and update it again.

Thanks; I tried that last night, and everything is OK again.

-- 
Jean-Pierre Radley <jpr@jpr.com>  XC/XT Custodian   Sysop, CompuServe SCOForum

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: failed compile
  1998-03-19  8:19 failed compile Jean-Pierre Radley
  1998-03-21 10:36 ` Jeffrey A Law
  1998-03-21 10:36 ` Joern Rennecke
@ 1998-03-21 13:50 ` Martin von Loewis
  1998-03-21 13:50 ` Robert Lipe
  3 siblings, 0 replies; 8+ messages in thread
From: Martin von Loewis @ 1998-03-21 13:50 UTC (permalink / raw)
  To: jpr; +Cc: egcs

> After a 'cvs update' today, compilation halts at this point:
> 
>   Configuring in libraries/libf2c
>   loading cache ./config.cache
>   /s/tools/egcs/libf2c/configure: syntax error at line 537: `<<' unexpected
>   make: *** [configure-target-libf2c] Error 2

Did you have conflicts during the update? If so, removing configure,
and updating it might help.

Regards,
Martin

^ permalink raw reply	[flat|nested] 8+ messages in thread

* failed compile
@ 1998-05-15 14:00 Jean-Pierre Radley
  0 siblings, 0 replies; 8+ messages in thread
From: Jean-Pierre Radley @ 1998-05-15 14:00 UTC (permalink / raw)
  To: EGCS Developers

Compiling the latest code for SCO OpenServer 5.0.4, it fails with:

	Undefined                       first referenced
	 symbol                             in file
	 output_lang_identify              toplev.o

I see that the gcc/Changelog notes that on May 14th,
	
	(output_lang_identify): Hide prototype and definition.

and indeed, it's surrounded by '#if 0 ... #endif' in toplev.c.

I suspect the code at line 2450 regarding ASM_IDENTIFY_LANGUAGE
ought to go bye-bye too, 	

-- 
Jean-Pierre Radley <jpr@jpr.com>  XC/XT Custodian   Sysop, CompuServe SCOForum

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Failed compile
@ 1998-05-11 15:14 Jean-Pierre Radley
  0 siblings, 0 replies; 8+ messages in thread
From: Jean-Pierre Radley @ 1998-05-11 15:14 UTC (permalink / raw)
  To: EGCS Developers

SCO OpenServer 5.0.4

cvs checkout egcs
mkdir egcs/obj
cd egcs/obj
../configure --host=i486-pc-sco3.2v5.0
make

Compilation fails:

make[1]: Entering directory `/s/tools/egcs/obj/libraries/libio'
if [ x"no" = xyes ] && [ ! -d pic ]; then \
  mkdir pic; \
else true; fi
touch stamp-picdir
rootme=`pwd`/ ; export rootme; \
CC="/s/tools/egcs/obj/gcc/xgcc -B/s/tools/egcs/obj/gcc/ -I. -I../../../libio"; export CC; \
CXX="/s/tools/egcs/obj/gcc/xgcc -B/s/tools/egcs/obj/gcc/ -I. -I../../../libio -nostdinc++ -nostdinc++ -g -O2"; export CXX; \
CONFIG_NM="nm"; export CONFIG_NM; \
/bin/sh ../../../libio/gen-params LIB_VERSION=2.8.0 MATH_H_INLINES=1 >tmp-params.h
(EOF):undefined name: .L_T87
gen-params: could not compile dummy.C with /s/tools/egcs/obj/gcc/xgcc -B/s/tools/egcs/obj/gcc/ -I. -I../../../libio -nostdinc++ -nostdinc++ -g -O2
make[1]: *** [_G_config.h] Error 1
make[1]: Leaving directory `/s/tools/egcs/obj/libraries/libio'
make: *** [all-target-libio] Error 2


-- 
Jean-Pierre Radley <jpr@jpr.com>  XC/XT Custodian   Sysop, CompuServe SCOForum

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~1998-05-15 14:00 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-03-19  8:19 failed compile Jean-Pierre Radley
1998-03-21 10:36 ` Jeffrey A Law
1998-03-21 10:36 ` Joern Rennecke
1998-03-21 13:50   ` Jean-Pierre Radley
1998-03-21 13:50 ` Martin von Loewis
1998-03-21 13:50 ` Robert Lipe
1998-05-11 15:14 Failed compile Jean-Pierre Radley
1998-05-15 14:00 failed compile Jean-Pierre Radley

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).