David O'Brien wrote:
>> I think the best fix is to edit "src/contrib/libg++/libg++/src/std.h"
>
> But src/contrib/libg++ & src/gnu/lib/libg++ is about to be ``cvs rm''ed.
That's even better. :-)
> IF we wanted to continue to offer libg++ I would need to import libg++
> 2.8.1.3.
Ick. I'm all f
> I've been looking into this. The main problem of course is that we're
> trying to use an old libg++
Yes.
> I think the best fix is to edit "src/contrib/libg++/libg++/src/std.h"
But src/contrib/libg++ & src/gnu/lib/libg++ is about to be ``cvs rm''ed.
IF we wanted to continue to offer libg++ I
In article <19990404162457.b78...@nuxi.com>,
David O'Brien wrote:
> > I've hit this one now too.
>
> I'm trying to duplicate the problem.
>
> My guess at the fix is to remove the "-DHAVE_CC_OSFCN_H=1\" line from
> src/gnu/usr.bin/groff/Makefile.cfg. But I can't tell what other problems
> this m
This seems to fix the problem. I got all the through buildworld and
have installed the code. Man(1) seems to work fine, but I haven't done
a major stress test of groff and the related programs.
Jim Bloom
bl...@acm.org
David O'Brien wrote:
>
> > I've hit this one now too.
>
> I'm trying to du
> I've hit this one now too.
I'm trying to duplicate the problem.
My guess at the fix is to remove the "-DHAVE_CC_OSFCN_H=1\" line from
src/gnu/usr.bin/groff/Makefile.cfg. But I can't tell what other problems
this may cause.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsub
I've hit this one now too.
Jim Bloom wrote:
>I get the same error. This is more to the error message which I have
>included below. I am doing a "make buildworld" after deleting
>everything in /usr/obj. Cvsup from freebsd3.freebsd.org at around 21:00
>GMT.
>
>Jim Bloom
>bl...@acm.org
>
>c++ -I/
I get the same error. This is more to the error message which I have
included below. I am doing a "make buildworld" after deleting
everything in /usr/obj. Cvsup from freebsd3.freebsd.org at around 21:00
GMT.
Jim Bloom
bl...@acm.org
c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe
> Only if you make world with -j x ...
> without -j it's working.
OH YES! DON'T -j at this time.
I know there are a few dependency problems in the Makefiles at this time.
I wanted to do the minimum number of changes to them to get EGCS'ifed.
(so cvs diff would be useful)
They will be cleaned up
Hi,
At 9:38 pm +0200 4/4/99, Martin Blapp wrote:
>Only if you make world with -j x ...
>without -j it's working.
>
>make buildworld -j10 > /tmp/build.out 2>&1 &
>breaks the same time making the cc_tools :
>
>`gencheck.c' is up to date.
>`c-parse.in' is up to date.
>`gencheck.c' is up to date.
>`c-
> c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe -fno-for-scope
> -I/usr/src/gnu/usr.bin/groff/libgroff/../include -DHAVE_UNISTD_H=1
> -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1
> -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1
> -DSTDIO_H_
Hello Bob,
Monday, April 05, 1999, 12:03:48 AM, you wrote:
BB> --
Rebuilding tools needed to build libraries
BB> --
BB> [...]
===>> cc_int
BB> make: don't know how to make
Only if you make world with -j x ...
without -j it's working.
make buildworld -j10 > /tmp/build.out 2>&1 &
breaks the same time making the cc_tools :
`gencheck.c' is up to date.
`c-parse.in' is up to date.
`gencheck.c' is up to date.
`c-parse.in' is up to date.
===> cc_int
make: don't know how
12 matches
Mail list logo
