On Sun, Aug 31, 2003 at 11:43:25PM -0700, Scott Long wrote:
scottl 2003/08/31 23:43:25 PDT
FreeBSD src repository
Modified files:
.Makefile.inc1
Log:
Clarify the numbering of some of the build stages.
Revision ChangesPath
1.389 +9
Ruslan Ermilov wrote:
On Sun, Aug 31, 2003 at 11:43:25PM -0700, Scott Long wrote:
scottl 2003/08/31 23:43:25 PDT
FreeBSD src repository
Modified files:
.Makefile.inc1
Log:
Clarify the numbering of some of the build stages.
Revision ChangesPath
1.389
In message: [EMAIL PROTECTED]
Scott Long [EMAIL PROTECTED] writes:
: Clarify the numbering of some of the build stages.
: How about if we get rid of the numbering here completely?
: I like the numbering since it can give me an idea of progress at a
: quick glance without having to
[Sorry for a cross-post, it's intentional.]
The patch below brings us the following functionality:
1. FreeBSD 4.0 can be source upgraded to FreeBSD 4.5-STABLE.
(Only standard make world has been tested, with an empty
/etc/make.conf.)
FreeBSD 4.0 could be source upgraded to FreeBSD
On Thu, Oct 25, 2001 at 11:37:28AM -0400, Andrew Gallatin wrote:
x86 sysinstall seems to have a hardcoded reference to /boot. Eg:
=== usr.sbin/spray
rm -f .depend
mkdep -f .depend -a -nostdinc
-I/usr/obj/i386/home/gallatin/current/src/alpha/usr/include
Ruslan Ermilov writes:
+.if ${MACHINE_ARCH} == i386
+.if exists(${.OBJDIR}/../../sys/boot/${MACHINE}/boot0/boot0)
+BOOT0= ${.OBJDIR}/../../sys/boot/${MACHINE}/boot0/boot0
+.else
+BOOT0= /boot/boot0
+.endif
But its failing at the depends stage. At this stage, boot0 will
On 25-Oct-01 Andrew Gallatin wrote:
Ruslan Ermilov writes:
+.if ${MACHINE_ARCH} == i386
+.if exists(${.OBJDIR}/../../sys/boot/${MACHINE}/boot0/boot0)
+BOOT0=${.OBJDIR}/../../sys/boot/${MACHINE}/boot0/boot0
+.else
+BOOT0=/boot/boot0
+.endif
But its failing at the
After unhooking sysinstall from the build, we have almost total
success.
The only remaining problem is that the kernel install failed, due to
a missing hints file in my DESTIR's /boot.
One interesting bit of trivia -- an alpha crossbuilds an x86 world
roughly 30-40% faster than it builds a
On 21 May 2001, Cyrille Lefevre wrote:
Bruce Evans [EMAIL PROTECTED] writes:
Debian CDs on FreeBSD with linux emulation way better than you can build
say a -STABLE release on a -CURRENT box... )
I just tried a Linux fdisk binary built in 1997 under FreeBSD-current.
It seemed to
Bruce Evans wrote:
On 21 May 2001, Cyrille Lefevre wrote:
[snip]
I don't need it myself (I only ran it to see if it supported Linux
extended partitions (it didn't, at least in it's list of known partition
types)). This is for the old Linux fdisk with a dumb terminal interface
which hadn't
Bruce Evans [EMAIL PROTECTED] writes:
Debian CDs on FreeBSD with linux emulation way better than you can build
say a -STABLE release on a -CURRENT box... )
I just tried a Linux fdisk binary built in 1997 under FreeBSD-current.
It seemed to run perfectly except it couldn't determine the
Bruce Evans [EMAIL PROTECTED] writes:
Debian CDs on FreeBSD with linux emulation way better than you can build
say a -STABLE release on a -CURRENT box... )
I just tried a Linux fdisk binary built in 1997 under FreeBSD-current.
It seemed to run perfectly except it couldn't determine the
On Thu, 17 May 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] Brian
Somers writes:
: Solaris calls it's ioctl files /usr/include/sys/driver_io.h so I'd
: spell digiio.h /usr/include/sys/digi_io.h.
Actually, the more I think about it, the more I like putting it in
On Thu, 17 May 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] Brian
Somers writes:
: Solaris calls it's ioctl files /usr/include/sys/driver_io.h so I'd
: spell digiio.h /usr/include/sys/digi_io.h.
Actually, the more I think about it, the more I like putting it in
On Fri, 18 May 2001, Brian Somers wrote:
On Thu, 17 May 2001, Warner Losh wrote:
I quite like the fact that the programming interface sys/fooio.h is
separated from the driver implementation. There is less chance that the
driver writer will expose irrelavent implementation details in the
John/peter, could you repo-copy src/sys/dev/digi/digiio.h to
src/sys/sys/digiio.h ?
Ta.
On Fri, 18 May 2001, Brian Somers wrote:
On Thu, 17 May 2001, Warner Losh wrote:
I quite like the fact that the programming interface sys/fooio.h is
separated from the driver implementation.
On Thu, May 17, 2001 at 07:52:51PM +0300, Ruslan Ermilov wrote:
[...]
There are 59 Makefiles that have -I${.CURDIR}/(../)+sys in them.
All these are bogus. We should get rid of all of them (-I's).
So far, I have found sbin/mount_* use headers from /sys/miscfs/
that are not installed into
On Fri, May 18, 2001 at 05:11:11PM +0300, Ruslan Ermilov wrote:
On Thu, May 17, 2001 at 07:52:51PM +0300, Ruslan Ermilov wrote:
[...]
There are 59 Makefiles that have -I${.CURDIR}/(../)+sys in them.
All these are bogus. We should get rid of all of them (-I's).
So far, I have found
Brian Somers wrote:
John/peter, could you repo-copy src/sys/dev/digi/digiio.h to
src/sys/sys/digiio.h ?
Done.
Ta.
On Fri, 18 May 2001, Brian Somers wrote:
On Thu, 17 May 2001, Warner Losh wrote:
I quite like the fact that the programming interface sys/fooio.h is
separated
On Wed, 16 May 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] Brian Somers writes:
: How should this be done - and where should I install digiio.h if
: that's what's required ?
I think that ppi device sets the standard here. It installs into
/usr/include/dev/ppi/ppi*.h. digiio
On Wed, 16 May 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] Brian Somers writes:
: How should this be done - and where should I install digiio.h if
: that's what's required ?
I think that ppi device sets the standard here. It installs into
/usr/include/dev/ppi/ppi*.h.
On Thu, May 17, 2001 at 08:14:10PM +1000, Bruce Evans wrote:
On Wed, 16 May 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] Brian Somers writes:
: How should this be done - and where should I install digiio.h if
: that's what's required ?
I think that ppi device sets the
Most headers that define ioctls are in sys. I think there should
be at most one directory for ioctl headers and it shouldn't be a subdir
of /usr/include/sys (/usr/include/sys/dev doesn't even reflect the
kernel tree).
Might I guess it should probably be called
In message [EMAIL PROTECTED] Brian Somers writes:
: Solaris calls it's ioctl files /usr/include/sys/driver_io.h so I'd
: spell digiio.h /usr/include/sys/digi_io.h.
We're not solaris :-). BSD traditionally spells things fooio.h for
driver foo. FreeBSD changed the traditional place for devices,
In message [EMAIL PROTECTED] Brian
Somers writes:
: Solaris calls it's ioctl files /usr/include/sys/driver_io.h so I'd
: spell digiio.h /usr/include/sys/digi_io.h.
Actually, the more I think about it, the more I like putting it in
/usr/include/sys/fooio.h. We have lots of other files there
[cc'd to -arch and not to cvs-committers]
For anyone that's reading -arch and hasn't seen this on -current, the
thread is discussing userland sources that have -I../../sys in their
Makefile and then #include sys/dev/blahio.h.
I think everyone agrees that these headers should be made public,
On Thu, May 17, 2001 at 05:37:54PM +0100, Brian Somers wrote:
[cc'd to -arch and not to cvs-committers]
For anyone that's reading -arch and hasn't seen this on -current, the
thread is discussing userland sources that have -I../../sys in their
Makefile and then #include sys/dev/blahio.h.
In message [EMAIL PROTECTED] Szilveszter Adam writes:
: I think that cross-platform means compilation between i386 and alpha (and
: possibly others) not different OS's:-) (Although admittedly you can build
: Debian CDs on FreeBSD with linux emulation way better than you can build
: say a -STABLE
On Tue, May 15, 2001 at 05:02:25PM -0600, Warner Losh wrote:
In message [EMAIL PROTECTED] Maxim Sobolev writes:
: Perhaps we could rip off the code that dumps keymap file into a
: little utility on its own and use this utility to bootstrap
: sysinstall. I could look into this direction if
In message [EMAIL PROTECTED] Ruslan Ermilov writes:
: FWIW, my gross hack to usr.sbin/kbdcontrol also worked:
I tend to dislike adding ../../sys to the includes list since they
might not be compatible with the host's sys files used to build libc.
Warner
To Unsubscribe: send mail to [EMAIL
Warner Losh wrote:
In message [EMAIL PROTECTED] Maxim Sobolev writes:
: There is at least one easy way - we can check if PASTE
: is defined and define it to be NOP if it isn't. This would allow
: to use kbdcontrol as a bootstrap tool on 4-STABLE.
:
: See attached patch.
Heh. I came up
On Tue, 15 May 2001, Ruslan Ermilov wrote:
On Tue, May 15, 2001 at 05:42:04PM +0300, Peter Pentchev wrote:
[...]
Can't you teach sysinstall/Makefile to use the kbdcontrol in
${.OBJDIR}/../kbdcontrol/kbdcontrol instead, and make it somehow
depend on kbdcontrol being built beforehand?
On Wed, May 16, 2001 at 06:47:12PM +1000, Bruce Evans wrote:
On Tue, 15 May 2001, Ruslan Ermilov wrote:
On Tue, May 15, 2001 at 05:42:04PM +0300, Peter Pentchev wrote:
[...]
Can't you teach sysinstall/Makefile to use the kbdcontrol in
${.OBJDIR}/../kbdcontrol/kbdcontrol instead, and
On Wed, 16 May 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] Ruslan Ermilov writes:
: FWIW, my gross hack to usr.sbin/kbdcontrol also worked:
I tend to dislike adding ../../sys to the includes list since they
might not be compatible with the host's sys files used to build libc.
On Thu, May 17, 2001 at 12:51:59AM +1000, Bruce Evans wrote:
On Wed, 16 May 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] Ruslan Ermilov writes:
: FWIW, my gross hack to usr.sbin/kbdcontrol also worked:
I tend to dislike adding ../../sys to the includes list since they
might
On Wed, 16 May 2001, Szilveszter Adam wrote:
On Wed, May 16, 2001 at 06:47:12PM +1000, Bruce Evans wrote:
Even running kbdcontrol might break cross-platform builds. Consider
running it on a host platform of Linux. It might fail attempting to
do a keyboard ioctl in its initalization.
On Wed, 16 May 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] Ruslan Ermilov writes:
: FWIW, my gross hack to usr.sbin/kbdcontrol also worked:
I tend to dislike adding ../../sys to the includes list since they
might not be compatible with the host's sys files used to build
In message [EMAIL PROTECTED] Brian Somers writes:
: How should this be done - and where should I install digiio.h if
: that's what's required ?
I think that ppi device sets the standard here. It installs into
/usr/include/dev/ppi/ppi*.h. digiio should likely do the same.
Warner
To
On Mon, May 14, 2001 at 10:21:02AM -0700, Ruslan Ermilov wrote:
ru 2001/05/14 10:21:02 PDT
Modified files:
.Makefile.inc1
Log:
Add kbdcontrol(1) to bootstrap-tools.
This fixes the upgrade path breakage in usr.sbin/sysinstall.
Revision
OK, more details on 4.3-STABLE - 5.0-CURRENT upgrade path breakage.
1. kbdcontrol(1) is used by usr.sbin/sysinstall/Makefile to generate
keymap.h with keyboard maps.
2. Recent usr.sbin/sysinstall/Makefile wants to generate keymap.h
from current keymap sources in
On Tue, May 15, 2001 at 05:33:54PM +0300, Ruslan Ermilov wrote:
OK, more details on 4.3-STABLE - 5.0-CURRENT upgrade path breakage.
1. kbdcontrol(1) is used by usr.sbin/sysinstall/Makefile to generate
keymap.h with keyboard maps.
2. Recent usr.sbin/sysinstall/Makefile wants to
On Tue, May 15, 2001 at 05:42:04PM +0300, Peter Pentchev wrote:
[...]
Can't you teach sysinstall/Makefile to use the kbdcontrol in
${.OBJDIR}/../kbdcontrol/kbdcontrol instead, and make it somehow
depend on kbdcontrol being built beforehand?
Doing it this way would break cross-platform
In message [EMAIL PROTECTED] Ruslan Ermilov writes:
: Doing it this way would break cross-platform builds.
I'm not seeing this breakage, but I have some simple hacks in my
tree. Lemme see if I'm just lucky, or if those hacks actually work.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
Ruslan Ermilov wrote:
On Mon, May 14, 2001 at 10:21:02AM -0700, Ruslan Ermilov wrote:
ru 2001/05/14 10:21:02 PDT
Modified files:
.Makefile.inc1
Log:
Add kbdcontrol(1) to bootstrap-tools.
This fixes the upgrade path breakage in
On Tue, 15 May 2001 21:57:44 +0300, Maxim Sobolev wrote:
Ruslan Ermilov wrote:
On Mon, May 14, 2001 at 10:21:02AM -0700, Ruslan Ermilov wrote:
ru 2001/05/14 10:21:02 PDT
Modified files:
.Makefile.inc1
Log:
Add kbdcontrol(1) to
In message [EMAIL PROTECTED] Maxim Sobolev writes:
: There is at least one easy way - we can check if PASTE
: is defined and define it to be NOP if it isn't. This would allow
: to use kbdcontrol as a bootstrap tool on 4-STABLE.
:
: See attached patch.
Heh. I came up with this independently.
In message [EMAIL PROTECTED] Maxim Sobolev writes:
: Perhaps we could rip off the code that dumps keymap file into a
: little utility on its own and use this utility to bootstrap
: sysinstall. I could look into this direction if there aren't better
: ideas.
I think your idea of just defining
47 matches
Mail list logo
