broken world

2003-07-28 Thread Jan Willem Knopper
/usr/src/contrib/isc-dhcp/common/dispatch.c:47: error: syntax error
before string constant
/usr/src/contrib/isc-dhcp/common/dispatch.c:44:1: unterminated #ifndef
*** Error code 1

This error also occurs in isc-dhcp/includes/dhcpd.h:45 an possibly in
more files.

The source looks like:

#ifndef lint
$FreeBSD: src/contrib/isc-dhcp/includes/dhcpd.h,v 1.2 2003/07/28 08:30:11 mbr Exp 
$\n;
#endif /* not lint */

This is with a recently cvsupped current. It is probably caused by a
commit by mbr about three hours ago.

Jilles Tjoelker,
Jan Willem Knopper
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: broken world

2003-07-28 Thread Lukas Ertl
On Mon, 28 Jul 2003, Jan Willem Knopper wrote:

 /usr/src/contrib/isc-dhcp/common/dispatch.c:47: error: syntax error
 before string constant
 /usr/src/contrib/isc-dhcp/common/dispatch.c:44:1: unterminated #ifndef
 *** Error code 1

 This error also occurs in isc-dhcp/includes/dhcpd.h:45 an possibly in
 more files.

 The source looks like:

 #ifndef lint
 $FreeBSD: src/contrib/isc-dhcp/includes/dhcpd.h,v 1.2 2003/07/28 08:30:11 mbr Exp 
 $\n;
 #endif /* not lint */

This was fixed in rev. 1.3 of src/contrib/isc-dhcp/common/dispatch.c.

regards,
le

-- 
Lukas Ertl eMail: [EMAIL PROTECTED]
UNIX Systemadministrator   Tel.:  (+43 1) 4277-14073
Vienna University Computer Center  Fax.:  (+43 1) 4277-9140
University of Vienna   http://mailbox.univie.ac.at/~le/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: broken world

2003-07-28 Thread Martin Blapp

I should sleep more !

 /usr/src/contrib/isc-dhcp/common/dispatch.c:47: error: syntax error
 before string constant
 /usr/src/contrib/isc-dhcp/common/dispatch.c:44:1: unterminated #ifndef
 *** Error code 1

Sorry for the troubles I've caused.

Martin
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


/usr/src/gnu/lib/csu broken world

2002-07-17 Thread Troy

I've seen some of the past postings relating to prolems experienced with
lib/csu, but the only file in my csu director is the Makefile.  This error
has been with me for quite some time. I've made sure to do a make cleandir
prior to trying to build the world. I have built the latest GCC 3.1 from
the binaries. I'm still having the same issue. Ideas?

-Troy


--
 stage 4: building libraries
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=i386  MACHINE=i386  
OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec  
GROFF_BIN_PATH=/usr/obj/usr/src/i386/usr/bin  
GROFF_FONT_PATH=/usr/obj/usr/src/i386/usr/share/groff_font  
GROFF_TMAC_PATH=/usr/obj/usr/src/i386/usr/share/tmac  DESTDIR=/usr/obj/usr/src/i386  
INSTALL=sh /usr/src/tools/install.sh  
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
 make -f Makefile.inc1 -DNOHTML -DNOINFO -DNOMAN -DNOFSCHG libraries
cd /usr/src;  make -f Makefile.inc1 _startup_libs;  make -f Makefile.inc1 
_prebuild_libs;  make -f Makefile.inc1 _generic_libs;
cd /usr/src/gnu/lib/csu;  make DIRPRFX=gnu/lib/csu/ depend;  make DIRPRFX=gnu/lib/csu/ 
all;  make DIRPRFX=gnu/lib/csu/ install
make -f /usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile 
MFILE=/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile 
GCCDIR=/usr/src/gnu/lib/csu/../../../contrib/gcc tconfig.h
echo 'struct rtx_def;'   tconfig.h
echo 'typedef struct rtx_def *rtx;'  tconfig.h
echo 'struct rtvec_def;' tconfig.h
echo 'typedef struct rtvec_def *rtvec;'  tconfig.h
echo 'union tree_node;'  tconfig.h
echo 'typedef union tree_node *tree;'tconfig.h
echo ''  tconfig.h
echo '#include ansidecl.h' tconfig.h
echo '#include i386/i386.h'tconfig.h
echo '#include i386/att.h' tconfig.h
echo '#include dbxelf.h'   tconfig.h
echo '#include elfos.h'tconfig.h
echo '#include freebsd-native.h'   tconfig.h
echo '#include freebsd-spec.h' tconfig.h
echo '#include freebsd.h'  tconfig.h
echo '#include i386/freebsd.h' tconfig.h
echo '#include defaults.h' tconfig.h
echo '#ifndef POSIX' tconfig.h
echo '# define POSIX'tconfig.h
echo '#endif'tconfig.h
echo '#define CONFIG_SJLJ_EXCEPTIONS 0'  tconfig.h
rm -f .depend
CC=/usr/bin/cc MKDEP_CPP_OPTS=-M -DCRT_BEGIN mkdep -f .depend -a-DIN_GCC 
-DHAVE_LD_EH_FRAME_HDR -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config 
-I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. 
-I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools  
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c
/usr/bin/cc -O -pipe  -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -finhibit-size-directive 
-fno-inline-functions  -fno-exceptions -fno-omit-frame-pointer 
-I/usr/src/gnu/lib/csu/../../../contrib/gcc/config 
-I/usr/src/gnu/lib/csu/../../../contrib/gcc -I.  
-I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools  -g0 -DCRT_BEGIN  -c -o crtbegin.o 
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c
In file included from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:63:
/usr/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:37: field `array' has 
incomplete type
/usr/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:135: field `augmentation' 
has incomplete type
/usr/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:143: field `pc_begin' has 
incomplete type
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:254: warning: `used' attribute 
directive ignored
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: In function 
`__do_global_dtors_aux':
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:256: syntax error before 
`completed'
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: `completed' undeclared 
(first use in this function)
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: (Each undeclared identifier 
is reported only once
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: for each function it appears 
in.)
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: At top level:
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:298: warning: `used' attribute 
directive ignored
*** Error code 1

Stop in /usr/src/gnu/lib/csu.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world in rtld-elf...

2002-06-14 Thread Bruce Evans

On Thu, 13 Jun 2002, Alex Zepeda wrote:

 On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:

  rtld still uses asms with the old, broken/fragile 0 constraint.  This
  constraint is especially broken/fragile if things are pessimized by
  compiling without optimizations.

 D'oh!

 Is there any chance of sticking a warning in the makefile if -O0 (or
 whatever else would cause it to not compile) is present?

Not really.  It is a transient bug that is almost as easy to fix as
warn about.

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world in rtld-elf...

2002-06-14 Thread Alex Zepeda

On Fri, Jun 14, 2002 at 07:09:06PM +1000, Bruce Evans wrote:

 Not really.  It is a transient bug that is almost as easy to fix as
 warn about.

So when can I expect the fix to be committed? :-D

- alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world in rtld-elf...

2002-06-13 Thread Alex Zepeda

On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:

 rtld still uses asms with the old, broken/fragile 0 constraint.  This
 constraint is especially broken/fragile if things are pessimized by
 compiling without optimizations.

D'oh!

Is there any chance of sticking a warning in the makefile if -O0 (or
whatever else would cause it to not compile) is present?

- alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world in rtld-elf...

2002-06-13 Thread Terry Lambert

Alex Zepeda wrote:
 On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
  rtld still uses asms with the old, broken/fragile 0 constraint.  This
  constraint is especially broken/fragile if things are pessimized by
  compiling without optimizations.
 
 D'oh!
 
 Is there any chance of sticking a warning in the makefile if -O0 (or
 whatever else would cause it to not compile) is present?


GCCVERS=`gcc -v 21 | grep version | cut -d   -f 3`
.if ${GCCVERS} = 3.1
.BEGIN:
echo Optimization with GCC 3.1 is often broken! 2
.endif


Oh... you wanted to grep -O out of the CFLAGS and CXXFLAGS?
How to do that should be obvious from the above...

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world in rtld-elf...

2002-06-13 Thread Juli Mallett

* Terry Lambert [EMAIL PROTECTED] escriurères
 Alex Zepeda wrote:
  On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
   rtld still uses asms with the old, broken/fragile 0 constraint.  This
   constraint is especially broken/fragile if things are pessimized by
   compiling without optimizations.
  
  D'oh!
  
  Is there any chance of sticking a warning in the makefile if -O0 (or
  whatever else would cause it to not compile) is present?
 
 
 GCCVERS=`gcc -v 21 | grep version | cut -d   -f 3`
 .if ${GCCVERS} = 3.1
 .BEGIN:
   echo Optimization with GCC 3.1 is often broken! 2
 .endif
 
 
 Oh... you wanted to grep -O out of the CFLAGS and CXXFLAGS?
 How to do that should be obvious from the above...

Errr, it was with 0 level optimisation that is the problem, not a real
level.  Read carefully what bde said, and look at hte warnings and how
GCC deals with the code in question.

Also, your example is very wrong, read make(1)'s section on dealing with
variables.
-- 
Juli Mallett [EMAIL PROTECTED]  FreeBSD: The Power To Serve
Perception is prejudice / Don't classify me / Accept me as me / Not what you see

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world in rtld-elf...

2002-06-13 Thread Terry Lambert

Juli Mallett wrote:
 Errr, it was with 0 level optimisation that is the problem, not a real
 level.  Read carefully what bde said, and look at hte warnings and how
 GCC deals with the code in question.
 
 Also, your example is very wrong, read make(1)'s section on dealing with
 variables.


I know my example is very wrong; though it could be used to grep
for optimizer flags, where it could not be used for what I jokingly
said it could be used for... I guess it was too subtle.

Question:

-O0 fails to produce good code; how do I check and warn if
-O0 is being used?

Answer:

Fix -O0, or grep its use and complain about it

Answer 2:

Make its use an argument error to the compiler, until it is
fixed

Answer 3:

Quit munging the Makefiles, when they will just need to be
unmunged later, and the problem goes away if you change
the compiler

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world in rtld-elf...

2002-06-13 Thread Juli Mallett

* Terry Lambert [EMAIL PROTECTED] escriurères
 Juli Mallett wrote:
  Errr, it was with 0 level optimisation that is the problem, not a real
  level.  Read carefully what bde said, and look at hte warnings and how
  GCC deals with the code in question.
  
  Also, your example is very wrong, read make(1)'s section on dealing with
  variables.
 
 
 I know my example is very wrong; though it could be used to grep
 for optimizer flags, where it could not be used for what I jokingly
 said it could be used for... I guess it was too subtle.
 
 Question:
 
   -O0 fails to produce good code; how do I check and warn if
   -O0 is being used?
 
 Answer:
 
   Fix -O0, or grep its use and complain about it

.if ${MACHINE_ARCH} == i386
CFLAGS:= $(CFLAGS:N-O0)
.endif

I think.

 Answer 2:
 
   Make its use an argument error to the compiler, until it is
   fixed

-O0 isn't broken, it just doesn't handle this construct right, and the issue
is known.

 Answer 3:
 
   Quit munging the Makefiles, when they will just need to be
   unmunged later, and the problem goes away if you change
   the compiler

NetBSD and OpenBSD do this to work around crappy toolchains all the time.

Most of the time it's to *enable* -O0 though, ironically :)
-- 
Juli Mallett [EMAIL PROTECTED]  FreeBSD: The Power To Serve
Perception is prejudice / Don't classify me / Accept me as me / Not what you see

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Broken World in xlint/llib

2002-06-12 Thread Troy

Seeing some errors trying to buildworld with the xlint/llib-lposix. It
appears the error is in stdarg.h. I am running version 1.14 of stdarg.h

Line 43 in /usr/include/stdarg.h and /usr/include/machine/stdarg.h states:

typedef _BSD_VA_LIST_   va_list;

but in /usr/src/contrib/gcc/ginclude/stdarg.h it's version 1.5 (from
latest CVSUP) it states #ifndef __GNUC_VA_LIST

Not sure what I can do to fix this problem...I did a make includes
before issuing the make buildworld. Any help would be appreciated.

-Troy


=== usr.bin/xlint/llib
lint -cghapbx -Cposix /usr/src/usr.bin/xlint/llib/llib-lposix
llib-lposix:
stdarg.h:43: syntax error [249]
stdarg.h:110: syntax error [249]
time.h:141: warning: conversion from 'unsigned long long' may lose accuracy [132
]
time.h:158: warning: conversion from 'unsigned long long' may lose accuracy [132
]
time.h:165: warning: conversion from 'long' may lose accuracy [132]
llib-lposix:306: syntax error [249]
llib-lposix:307: syntax error [249]
llib-lposix:308: syntax error [249]
llib-lposix:308: cannot recover from previous errors [224]
*** Error code 1

Stop in /usr/src/usr.bin/xlint/llib.
*** Error code 1

Stop in /usr/src/usr.bin/xlint.
*** Error code 1

Stop in /usr/src/usr.bin.
*** Error code 1

top in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Broken world in rtld-elf...

2002-06-12 Thread Alex Zepeda

So what's up with -current?

I had to install gawk to get the kernel to build (and world too for that
matter).. I haven't had the balls to put the one true awk back in place.

But now whether in world mode or not I get:

blarf:/usr/src/libexec/rtld-elf#make
cc -O0 -Wall -DFREEBSD_ELF -I/usr/src/libexec/rtld-elf/i386 
-I/usr/src/libexec/rtld-elf -elf -fpic -DPIC   -Wformat=2 
-Wno-format-extra-args  -c /usr/src/libexec/rtld-elf/rtld.c
/usr/src/libexec/rtld-elf/rtld.c: In function `atomic_decr_int':
/usr/src/libexec/rtld-elf/i386/rtld_machdep.h:58: inconsistent operand 
constraints in an `asm'
*** Error code 1

Stop in /usr/src/libexec/rtld-elf.
blarf:/usr/src/libexec/rtld-elf#


eek?

- alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world in rtld-elf...

2002-06-12 Thread Bruce Evans

On Wed, 12 Jun 2002, Alex Zepeda wrote:

 So what's up with -current?

 I had to install gawk to get the kernel to build (and world too for that
 matter).. I haven't had the balls to put the one true awk back in place.

 But now whether in world mode or not I get:

 blarf:/usr/src/libexec/rtld-elf#make
 cc -O0 -Wall -DFREEBSD_ELF -I/usr/src/libexec/rtld-elf/i386
 ^^^
 -I/usr/src/libexec/rtld-elf -elf -fpic -DPIC   -Wformat=2
 -Wno-format-extra-args  -c /usr/src/libexec/rtld-elf/rtld.c
 /usr/src/libexec/rtld-elf/rtld.c: In function `atomic_decr_int':
 /usr/src/libexec/rtld-elf/i386/rtld_machdep.h:58: inconsistent operand
 constraints in an `asm'
 *** Error code 1

rtld still uses asms with the old, broken/fragile 0 constraint.  This
constraint is especially broken/fragile if things are pessimized by
compiling without optimizations.

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Broken world (was Re: cvs commit: src/lib/libc/posix1e cap_text.c)

2001-08-31 Thread Robert Watson

This should now be fixed (actually, as of last night I think).  Thanks!

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services

On Fri, 31 Aug 2001, Mike Barcroft wrote:

 Robert Watson [EMAIL PROTECTED] writes:
  rwatson 2001/08/30 19:12:00 PDT
  
Modified files:
  lib/libc/posix1e cap_text.c 
Log:
o Remove definition of CAP_MAX_BUF_LEN since it is defined in
  sys/capability.h now.

Submitted by: tmm
Obtained from:TrustedBSD Project

Revision  ChangesPath
1.4   +5 -2  src/lib/libc/posix1e/cap_text.c
 
 This seems to break world on my Alpha.  The error is:
 /usr/src/lib/libc/../libc/posix1e/cap_text.c:293: `CAP_MAX_BUF_LEN'
 undeclared
 
 CAP_MAX_BUF_LEN doesn't seem to be defined in rev 1.8 of capability.h.
 
 Best regards,
 Mike Barcroft
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Broken world (was Re: cvs commit: src/lib/libc/posix1e cap_text.c)

2001-08-30 Thread Mike Barcroft

Robert Watson [EMAIL PROTECTED] writes:
 rwatson 2001/08/30 19:12:00 PDT
 
   Modified files:
 lib/libc/posix1e cap_text.c 
   Log:
   o Remove definition of CAP_MAX_BUF_LEN since it is defined in
 sys/capability.h now.
   
   Submitted by:   tmm
   Obtained from:  TrustedBSD Project
   
   Revision  ChangesPath
   1.4   +5 -2  src/lib/libc/posix1e/cap_text.c

This seems to break world on my Alpha.  The error is:
/usr/src/lib/libc/../libc/posix1e/cap_text.c:293: `CAP_MAX_BUF_LEN'
undeclared

CAP_MAX_BUF_LEN doesn't seem to be defined in rev 1.8 of capability.h.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: broken world (kerberos5/lib/libasn1)

2001-06-21 Thread David Wolfskill

Date: Fri, 22 Jun 2001 01:00:53 +0900
From: Jun Kuriyama [EMAIL PROTECTED]

Today's nightly build reports breakage of the world...

/usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/lex.l:65: `SEQUENCE' 
undeclared (first use in this function)
/usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/lex.l:66: `OF' 
undeclared (first use in this function)
...

Stop in /usr/src/kerberos5/lib/libasn1.

You may well have obtained your updates at an inopportune time:  I'm
still building today's -CURRENT, but have got beyond the buildworld
(with no incident), and am in the process of building the new kernel.

My CVSup was between 03:47 - 03:52 this morning, PDT (GMT-0700), from
cvsup14.

Cheers,
david (of course, I haven't tried to *boot* it yet)
-- 
David H. Wolfskill  [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: broken world (kerberos5/lib/libasn1)

2001-06-21 Thread Jun Kuriyama

At Thu, 21 Jun 2001 09:04:51 -0700 (PDT),
David Wolfskill wrote:
 You may well have obtained your updates at an inopportune time:  I'm
 still building today's -CURRENT, but have got beyond the buildworld
 (with no incident), and am in the process of building the new kernel.

Thank you for your information.  My script will retry building the
world within one hour...


-- 
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc.
 [EMAIL PROTECTED] // FreeBSD Project

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: broken world (kerberos5/lib/libasn1)

2001-06-21 Thread Assar Westerlund

Jun Kuriyama [EMAIL PROTECTED] writes:
 Today's nightly build reports breakage of the world...

Please update to kerberos5/lib/libasn1/Makefile:1.9 or apply the
appended patch (relative to 1.8).

/assar

Index: Makefile
===
RCS file: /home/ncvs/src/kerberos5/lib/libasn1/Makefile,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -w -u -w -r1.8 -r1.9
--- Makefile2001/06/21 12:55:44 1.8
+++ Makefile2001/06/21 19:19:00 1.9
@@ -1,4 +1,4 @@
-# $FreeBSD: src/kerberos5/lib/libasn1/Makefile,v 1.8 2001/06/21 12:55:44 assar Exp $
+# $FreeBSD: src/kerberos5/lib/libasn1/Makefile,v 1.9 2001/06/21 19:19:00 assar Exp $
 
 LIB=   asn1
 CFLAGS+=-I${KRB5DIR}/include \
@@ -70,7 +70,6 @@
 .PATH: ${KRB5DIR}/lib/asn1
 .PATH: ${KRB5DIR}/lib/vers
 .PATH: ${KRB5DIR}/lib/roken
-.ORDER:parse.o lex.o
 
 build-tools:   make-print-version asn1_compile
 
@@ -115,7 +114,7 @@
mv y.tab.c parse.c
mv y.tab.h parse.h
 
-lex.o: lex.l
+lex.o: lex.l parse.h
 
 print_version.o: print_version.h print_version.c roken.h
${CC} ${CFLAGS} -c -o ${.TARGET} ${KRB5DIR}/lib/vers/print_version.c

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: broken world (kerberos5/lib/libasn1)

2001-06-21 Thread Jun Kuriyama

At 21 Jun 2001 21:19:58 +0200,
Assar Westerlund wrote:
 Please update to kerberos5/lib/libasn1/Makefile:1.9 or apply the
 appended patch (relative to 1.8).

Fixed.  Thanks!


-- 
Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc.
 [EMAIL PROTECTED] // FreeBSD Project

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



BROKEN WORLD

2000-01-26 Thread Warner Losh


Peter,

I'd like to see your world log, and the output of 
cd src/share/mk ; cvs diff bsd.kmod.mk.  I get the following error
when I try to build world as of about 2 hours ago.  I just did a cvsup
and only things in lib and ports updated.

=== sys/modules/vpo
@ - /home/imp/FreeBSD/src/sys
machine - /home/imp/FreeBSD/src/sys/i386/include
perl @/kern/makedevops.pl -h @/kern/bus_if.m
perl @/kern/makedevops.pl -h @/kern/device_if.m
make: don't know how to make ppbus_if.h. Stop

Yours in frustration,

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: BROKEN WORLD

2000-01-26 Thread Warner Losh


Warner Losh writes:
:   I'd like to see your world log, and the output of 
: cd src/share/mk ; cvs diff bsd.kmod.mk.  I get the following error
: when I try to build world as of about 2 hours ago.  I just did a cvsup
: and only things in lib and ports updated.

Ummm, I think cvs did something strange...  I retract this statement
until such time as I can make sure that cvs didn't do something
stupid.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Broken world

1999-07-29 Thread David O'Brien

 Any prognosis on a fix?

I'll revert when I go to bed if I am not getting anywhere.
 
-- 
-- David([EMAIL PROTECTED]  -or-  [EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Broken world

1999-07-28 Thread Greg Lehey

c++ -c -I/usr/obj/usr/src/tmp/usr/include/g++ -O -pipe 
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config 
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC 
-I/usr/obj/usr/src/tmp/usr/include 
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -DL_op_new -o 
_op_new.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc
In file included from /usr/obj/usr/src/tmp/usr/include/stddef.h:39,
 from /usr/obj/usr/src/tmp/usr/include/g++/new:8,
 from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28:
/usr/obj/usr/src/tmp/usr/include/machine/ansi.h:103: syntax error before 
`__attribute__'
/usr/obj/usr/src/tmp/usr/include/machine/ansi.h:104: syntax error before 
`__attribute__'
In file included from /usr/obj/usr/src/tmp/usr/include/g++/new:9,
 from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28:
/usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string constant
*** Error code 1

This happened on multiple machines.

Greg
-- 
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Broken world

1999-07-28 Thread David O'Brien

  from 
/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28:
 /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string constant
 *** Error code 1


This is due to the Bison-Yacc change.  I did builds of the compiler and
all, but not a full make world before commiting.  I am *VERY* surprised
it has taken nearly 24hrs for someone to yell Ouch!  

This morning and now I have been unable to verify this wasn't a problem
due to local hacks.  I am glad to now have independant verification.

-- 
-- David([EMAIL PROTECTED]  -or-  [EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Broken world

1999-07-28 Thread Greg Lehey

On Wednesday, 28 July 1999 at 23:05:56 -0700, David O'Brien wrote:
  from 
/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28:
 /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string 
constant
 *** Error code 1

 This is due to the Bison-Yacc change.

I almost thought so.

 I did builds of the compiler and all, but not a full make world
 before commiting.  I am *VERY* surprised it has taken nearly 24hrs
 for someone to yell Ouch!

I like to check my findings before screaming :-)

 This morning and now I have been unable to verify this wasn't a
 problem due to local hacks.  I am glad to now have independant
 verification.

Any prognosis on a fix?

Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Broken world

1999-07-28 Thread Peter Jeremy

"David O'Brien" [EMAIL PROTECTED] wrote:
  from 
/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28:
 /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string 
constant
 *** Error code 1


This is due to the Bison-Yacc change.  I did builds of the compiler and
all, but not a full make world before commiting.  I am *VERY* surprised
it has taken nearly 24hrs for someone to yell Ouch!  

I wrote exactly the same thing as Greg, just over 9 hours ago.

Petrer


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



broken world

1999-03-20 Thread Hostas Red
Hi!

For a couple weeks for now i have a broken world with following reason:

=== usr.sbin/i4b/isdnd
cc -O -pipe -I/usr/src/usr.sbin/i4b/isdnd/../isdnmonitor
-I/usr/src/usr.sbin/i4b/isdnd/../isdntel
-I/usr/obj/usr/src/usr.sbin/i4b/isdnd -DDEBUG -DUSE_RTPRIO -DUSE_CURSES
-I/usr/obj/usr/src/tmp/usr/include -c rc_scan.c
/usr/src/usr.sbin/i4b/isdnd/rc_scan.l: In function `yylex':
/usr/src/usr.sbin/i4b/isdnd/rc_scan.l:95: `BEEPCONNECT' undeclared (first
use this function)
/usr/src/usr.sbin/i4b/isdnd/rc_scan.l:95: (Each undeclared identifier is
reported only once
/usr/src/usr.sbin/i4b/isdnd/rc_scan.l:95: for each function it appears
in.)
/usr/src/usr.sbin/i4b/isdnd/rc_scan.l:111: `IDLE_ALG_OUT' undeclared
(first use this function)
*** Error code 1

Cleaning obj tree doesn't helps. Nothing helps, so. Anybody have similar
problems?

Adios,
/KONG



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Broken world

1999-02-27 Thread Bret Ford
  My 4.0-current buildworld broke. The sources were from yesterday
night.  The system is currently 4.0-current from Feb 16.  My UNIX 
system is a 486 main board with an evergreen upgrade. The
world was almost over, too! Argh! :-)

Bret Ford

=== usr.sbin/natd
gcc -O -Wall   -I/tigger/obj/usr/src/tmp/usr/include -c 
/usr/src/usr.sbin/natd/natd.c
/usr/src/usr.sbin/natd/natd.c: In function `SetAliasAddressFromIfName':
/usr/src/usr.sbin/natd/natd.c:702: warning: implicit declaration of function 
`SetPacketAliasAddress'
/usr/src/usr.sbin/natd/natd.c: In function `SetupPermanentLink':
/usr/src/usr.sbin/natd/natd.c:1203: warning: implicit declaration of function 
`PacketAliasPermanentLink'
gcc -O -Wall   -I/tigger/obj/usr/src/tmp/usr/include -c 
/usr/src/usr.sbin/natd/icmp.c
gcc -O -Wall   -I/tigger/obj/usr/src/tmp/usr/include  -o natd natd.o icmp.o  
-lalias
natd.o: In function `SetAliasAddressFromIfName':
natd.o(.text+0xc47): undefined reference to `SetPacketAliasAddress'
natd.o: In function `SetupPermanentLink':
natd.o(.text+0x12c4): undefined reference to `PacketAliasPermanentLink'
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Broken world

1999-02-27 Thread John Polstra
In article 199902271936.laa25...@uop.cs.uop.edu,
Bret Ford  bf...@uop.cs.uop.edu wrote:
   My 4.0-current buildworld broke. The sources were from yesterday
 night.  The system is currently 4.0-current from Feb 16.  My UNIX 
 system is a 486 main board with an evergreen upgrade. The
 world was almost over, too! Argh! :-)
 
 Bret Ford
 
 === usr.sbin/natd
 gcc -O -Wall   -I/tigger/obj/usr/src/tmp/usr/include -c 
 /usr/src/usr.sbin/natd/natd.c
 /usr/src/usr.sbin/natd/natd.c: In function `SetAliasAddressFromIfName':
 /usr/src/usr.sbin/natd/natd.c:702: warning: implicit declaration of function 
 `SetPacketAliasAddress'
 /usr/src/usr.sbin/natd/natd.c: In function `SetupPermanentLink':
 /usr/src/usr.sbin/natd/natd.c:1203: warning: implicit declaration of function 
 `PacketAliasPermanentLink'
 gcc -O -Wall   -I/tigger/obj/usr/src/tmp/usr/include -c 
 /usr/src/usr.sbin/natd/icmp.c
 gcc -O -Wall   -I/tigger/obj/usr/src/tmp/usr/include  -o natd natd.o icmp.o  
 -lalias
 natd.o: In function `SetAliasAddressFromIfName':
 natd.o(.text+0xc47): undefined reference to `SetPacketAliasAddress'
 natd.o: In function `SetupPermanentLink':
 natd.o(.text+0x12c4): undefined reference to `PacketAliasPermanentLink'
 *** Error code 1

It was broken by the recent commit to src/lib/libalias.  You can
probably get around it by reverting that directory to around Feb 25.

John
-- 
  John Polstra   j...@polstra.com
  John D. Polstra  Co., Inc.Seattle, Washington USA
  Nobody ever went broke underestimating the taste of the American public.
-- H. L. Mencken


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message