Re: Latest versions of bsd.lib.mk break picobsd...
> This still doesn't answer my question -- how can I reproduce the problem? > > cd /foo/bar > make grrr > > Something like that... Whoops, sorry. To reproduce this do: cd /usr/src ./release/picobsd/build/picobsd --src /usr/src --init yes, I know that --src is unnecessary but I always use it since I'm often using a tree that's NOT at /usr/src so I include it here. The --init will break with: mkdep -f .depend -a -nostdinc -DSTANDARD_INCLUDE_DIR=/home/gnn/FreeBSD/src.latest../usr/include -I/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:32: stddef.h: No such file or directory /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:33: stdlib.h: No such file or directory In file included from /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:34: /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common/crtbrand.c:28: sys/param.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf. *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest. *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest. ---> fail: Error <1> error code in <> Error: failed while making libraries ---> Aborting ./release/picobsd/build/picobsd Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
On Wed, Feb 27, 2002 at 09:49:28AM -0800, George V. Neville-Neil wrote: > > You'll have to pay some money if you need a 24-hour responsiveness. :-) > > > > The check is in the mail ;-) > > > What src/release PicoBSD script should I try to run to reproduce this? > > > > -CURRENT as of Monday. > > Things work fine in a checkout from 20 Feb 2002 and that's what I'm working with. > > If you can give me a bit of info (or a place to look) I can help address this >problem. > I'm going to try to work with Luigi on maintaining picobsd as this will be my > main development system. It's a very good way for embedded systems hacks > (like myself) to work. Very natural. And it's nice that I don't have to worry about > having -CURRENT on my development machine. > This still doesn't answer my question -- how can I reproduce the problem? cd /foo/bar make grrr Something like that... Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
> You'll have to pay some money if you need a 24-hour responsiveness. :-) > The check is in the mail ;-) > What src/release PicoBSD script should I try to run to reproduce this? > -CURRENT as of Monday. Things work fine in a checkout from 20 Feb 2002 and that's what I'm working with. If you can give me a bit of info (or a place to look) I can help address this problem. I'm going to try to work with Luigi on maintaining picobsd as this will be my main development system. It's a very good way for embedded systems hacks (like myself) to work. Very natural. And it's nice that I don't have to worry about having -CURRENT on my development machine. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
On Mon, Feb 25, 2002 at 04:38:29PM -0800, George V. Neville-Neil wrote: > Hi Folks, > > I've tried contacting [EMAIL PROTECTED] directly but haven't seen anything so I > figure I'll throw this out to the list. On 21 Feb 2002 a change was made to > the > You'll have to pay some money if you need a 24-hour responsiveness. :-) > bsd.lib.mk and bsd.prog.mk which is commented, in part, as: > > Get rid of the (now unneeded) -I${DESTDIR}/usr/include magic in bsd.prog.mk > and bsd.lib.mk. Finish the removal of LDDESTDIR in bsd.lib.mk,v 1.55 -- we > no longer have users of it. > > This change was made by "ru." Alas this breaks the picobsd build since the > statically built libraries need some way to know to get their includes from the > directory you're building in. This does not affect a general 5.0 build (I checked > that this morning) but is still very problematic. I'm only just starting with the > picobsd stuff and I would love to fix this bug in the right place if only someone > could tell me what this change meant and how pervasive it was. > > Putting in an extra CFLAG for -I${SRC}usr/include works for some libraries but > breaks libbind as alluded to by this comment in the same checkin: > > (Attempt to move the "-nostdinc -I..." part of CFLAGS into the new CINCLUDES > (modeled after a similar CXXINCLUDES) eventually failed because hard-coding > ${WORLDTMP}/usr/include to be the first in the include list does not always > work, e.g. lib/libbind.) > > So, can someone help me out here? > What src/release PicoBSD script should I try to run to reproduce this? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Latest versions of bsd.lib.mk break picobsd...
Hi Folks, I've tried contacting [EMAIL PROTECTED] directly but haven't seen anything so I figure I'll throw this out to the list. On 21 Feb 2002 a change was made to the bsd.lib.mk and bsd.prog.mk which is commented, in part, as: Get rid of the (now unneeded) -I${DESTDIR}/usr/include magic in bsd.prog.mk and bsd.lib.mk. Finish the removal of LDDESTDIR in bsd.lib.mk,v 1.55 -- we no longer have users of it. This change was made by "ru." Alas this breaks the picobsd build since the statically built libraries need some way to know to get their includes from the directory you're building in. This does not affect a general 5.0 build (I checked that this morning) but is still very problematic. I'm only just starting with the picobsd stuff and I would love to fix this bug in the right place if only someone could tell me what this change meant and how pervasive it was. Putting in an extra CFLAG for -I${SRC}usr/include works for some libraries but breaks libbind as alluded to by this comment in the same checkin: (Attempt to move the "-nostdinc -I..." part of CFLAGS into the new CINCLUDES (modeled after a similar CXXINCLUDES) eventually failed because hard-coding ${WORLDTMP}/usr/include to be the first in the include list does not always work, e.g. lib/libbind.) So, can someone help me out here? Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message