FBSD 5-CURRENT: Kernel Makefile.inc1 Error

2003-12-06 Thread William M. Grim
Hey there!  I'm having a slight problem performing a build on my FreeBSD 5.1
machine.  I downloaded the 5-CURRENT source code and only added the line,
device pcm to the GENERIC kernel, renaming it to ZEUS.

Then, I went into /usr/src and typed make buildkernel KERNCONF=ZEUS, and it
immediately came up with the errors:
--
-su-2.05b# make buildkernel
/usr/src/Makefile.inc1, line 745: warning: String comparison operator should be 
either == or !=
/usr/src/Makefile.inc1, line 745: Malformed conditional ((!defined(NO_RESCUE) ||  
defined(RELEASEDIR))   (${TARGET_ARCH} != ${MACHINE_ARCH} || ${BOOTSTRAPPING}  
501101))
/usr/src/Makefile.inc1, line 745: Need an operator
/usr/src/Makefile.inc1, line 747: if-less endif
/usr/src/Makefile.inc1, line 747: Need an operator
make: fatal errors encountered -- cannot continue
*** Error code 1

Stop in /usr/src.
--

The problem is with ${BOOTSTRAPING}  501101).  For some reason, it is
suddenly expecting BOOSTRAPPING to be a string, when it is apparent earlier in
the Makefile.inc1 that it is not.

I tried patching this on my own but failed; would someone more experienced
be able to patch this for me?

I have attached my dmesg and Makefile.inc1 to this as well just in case
someone wishes to view them.
-- 
William Michael Grim
Student, Southern Illinois University at Edwardsville
Unix Network Administrator, SIUE, Computer Science dept.
Phone: (217) 341-6552
Email: [EMAIL PROTECTED]


#
# $FreeBSD: src/Makefile.inc1,v 1.397 2003/11/16 21:17:43 gordon Exp $
#
# Make command line options:
#   -DNO_DYNAMICROOT do not link /bin and /sbin dynamically
#   -DNO_KERBEROS Do not build Heimdal (Kerberos 5)
#   -DNO_RESCUE do not build rescue binaries
#   -DNOCLEANDIR run ${MAKE} clean, instead of ${MAKE} cleandir
#   -DNOCLEAN do not clean at all
#   -DNOCRYPT will prevent building of crypt versions
#   -DNOMAN do not build the manual pages
#   -DNOPROFILE do not build profiled libraries
#   -DNOGAMES do not go into games subdir
#   -DNOSHARE do not go into share subdir
#   -DNOINFO do not make or install info files
#   -DNOLIBC_R do not build libc_r.
#   -DNO_FORTRAN do not build g77 and related libraries.
#   -DNO_KERNELCONFIG do not run config in ${MAKE} buildkernel
#   -DNO_KERNELCLEAN do not run ${MAKE} clean in ${MAKE} buildkernel
#   -DNO_KERNELDEPEND do not run ${MAKE} depend in ${MAKE} buildkernel
#   -DNO_PORTSUPDATE do not update ports in ${MAKE} update
#   -DNO_DOCUPDATE do not update doc in ${MAKE} update
#   LOCAL_DIRS=list of dirs to add additional dirs to the SUBDIR list
#   TARGET_ARCH=arch to crossbuild world to a different arch

#
# The intended user-driven targets are:
# buildworld  - rebuild *everything*, including glue to help do upgrades
# installworld- install everything built by buildworld
# update  - convenient way to update your source tree (eg: sup/cvs)
#
# Standard targets (not defined here) are documented in the makefiles in
# /usr/share/mk.  These include:
#   obj depend all install clean cleandepend cleanobj

# Put initial settings here.
SUBDIR=

# We must do share/info early so that installation of info `dir'
# entries works correctly.  Do it first since it is less likely to
# grow dependencies on include and lib than vice versa.
.if exists(${.CURDIR}/share/info)
SUBDIR+= share/info
.endif

.if exists(${.CURDIR}/include)
SUBDIR+= include
.endif
.if exists(${.CURDIR}/lib)
SUBDIR+= lib
.endif

# When upgrading to a dynamically linked root, install the runtime
# linker early into its new location before make(1) has a chance
# to run the dynamically linked /bin/sh.
.if !defined(NO_DYNAMICROOT)  !defined(NOPIC)  \
(!defined(TARGET_ARCH) || ${TARGET_ARCH} == ${MACHINE_ARCH})  \
!defined(DISTDIR)  \
(!defined(DESTDIR) || empty(DESTDIR) || ${DESTDIR} == /)  \
!exists(/libexec/ld-elf.so.1)
SUBDIR+= libexec/rtld-elf
.endif

.if exists(${.CURDIR}/bin)
SUBDIR+= bin
.endif
.if exists(${.CURDIR}/games)  !defined(NOGAMES)
SUBDIR+= games
.endif
.if exists(${.CURDIR}/gnu)
SUBDIR+= gnu
.endif
.if exists(${.CURDIR}/kerberos5)  exists(${.CURDIR}/crypto)  \
!defined(NOCRYPT)  !defined(NO_OPENSSL)  !defined(NO_KERBEROS)
SUBDIR+= kerberos5
.endif
.if exists(${.CURDIR}/libexec)
SUBDIR+= libexec
.endif
.if exists(${.CURDIR}/rescue)  !defined(NO_RESCUE)
SUBDIR+= rescue
.endif
.if exists(${.CURDIR}/sbin)
SUBDIR+= sbin
.endif
.if exists(${.CURDIR}/secure)  !defined(NOCRYPT)
SUBDIR+= secure
.endif
.if exists(${.CURDIR}/share)  !defined(NOSHARE)
SUBDIR+= share
.endif
.if exists(${.CURDIR}/sys)
SUBDIR+= sys
.endif
.if exists(${.CURDIR}/usr.bin)
SUBDIR+= usr.bin
.endif
.if exists(${.CURDIR}/usr.sbin)
SUBDIR+= usr.sbin
.endif

# etc must be last for distribute to work
.if exists(${.CURDIR}/etc)
SUBDIR+= etc
.endif

# These are last, since it is nice to at least get the base system
# rebuilt 

Re: FBSD 5-CURRENT: Kernel Makefile.inc1 Error

2003-12-06 Thread Garance A Drosihn
At 1:45 AM -0600 12/6/03, William M. Grim wrote:
Hey there!  I'm having a slight problem performing a build
on my FreeBSD 5.1 machine.  I downloaded the 5-CURRENT
source code and only added the line, device pcm to
the GENERIC kernel, renaming it to ZEUS.
Then, I went into /usr/src and typed
  make buildkernel KERNCONF=ZEUS,
and it immediately came up with the errors [...]
From the above description, it sounds like you are running
on a 5.1 system, and you are trying to compile a 5.2 kernel.
Is this true?
If the system you are on is 5.1, then you are going to have
to do a 'make buildworld' of the 5.2-source before you can
do a 'make buildkernel' of a 5.2 kernel.
--
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Incorrect identification of ultra dma ATA cables

2003-12-06 Thread Ion-Mihai Tetcu
On Fri, 5 Dec 2003 12:28:01 -0800 (PST)
Dan Strick [EMAIL PROTECTED] wrote:

 Dan Strick wrote:
  
  Did you plug the cable in the right way?
 
 Then Ion-Mihai Tetcu wrote:
  
  Well, I'm just sitting here and waching a few 80 conductor cables and
  they are:
  black - black - black x 3
  black - grey - black x 5
  blue - grey - black x 1
  red - grey - black x 1
  
  And the nice thing is that all are from Gigabyte motherboards boxes.
 
 
 Yes, I plugged the cables in the right way.  The motherboard end, which
 is supposed to use a blue socket connector, is the end that is not
 connected to the PDIAG/CBLID signal line.
 
 My Gigabyte motheboard did come with some astonishingly gaudy UDMA
 cables.  Two were bright yellow with green (instead of blue) host
 end connectors and a bright red stripe along the conductor#1 edge
 of the cable.  One grey cable had a red (instead of blue) connector.
 As near as I can tell, the electrons still drift along at pretty
 much the same old speed regardless of the color.

I'm sure the electrons in your cables know the Cristmas is approaching
and that's the reason Gigabyte gives us so many different-colored
conectors, so they don't slow down on their way. ;-)


-- 
IOnut
Unregistered ;) FreeBSD user
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: running wine automatically as a shell for w32 binaries

2003-12-06 Thread Julian Stacey
   Hi all,
   I wrote a new imgact function for FreeBSD to start wine
   automatically as a sort of an interpreter for windows
   binaries.
   http://www.mawit.com/~jau/imgact_wine-4.9.patch

Great idea !  If this small diff gets tested  merged into src/
automatic MS support will be a real plus.

-
Julian Stacey.   Munich Unix  Net Consultant.http://berklix.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: running wine automatically as a shell for w32 binaries

2003-12-06 Thread Chris BeHanna
On Saturday 06 December 2003 10:19, Julian Stacey wrote:
Hi all,
I wrote a new imgact function for FreeBSD to start wine
automatically as a sort of an interpreter for windows
binaries.
http://www.mawit.com/~jau/imgact_wine-4.9.patch

 Great idea !  If this small diff gets tested  merged into src/
 automatic MS support will be a real plus.

With the weekly proliferation of MS worms, trojans, and viruses,
do you *really* think this is a good idea?

Yeah, it's neat, nifty, and cool, but it comes with substantial
risk.

--
Chris BeHanna
Software Engineer   (Remove bogus before responding.)
[EMAIL PROTECTED]
 Turning coffee into software since 1990.


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