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
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
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
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
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
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
* 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
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
* 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
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:
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
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)
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
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:
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:
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
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
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
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
"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
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
21 matches
Mail list logo
