Re: Kernel Compile Error

[chris]

> Chris Maness <[EMAIL PROTECTED]> writes:
>
>> I was trying to compile a 7.0 Release and the compile failed.  I have
>> never had a kernel compilation fail before.
>>
>> Here is the last of the output:
>>
>> opt_global.h -fno-common -finline-limit=8000 --param
>> inline-unit-growth=100 --param large-function-growth=1000
>> -mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx bla bla bla
>
> That's really weird.  Is that an unchanged GENERIC kernel, with an
> empty make.conf?  If so, youseem to have something inconsistent in
> your sources.  How did you install the sources?  Can you wipe them
> clean and try again?
>
> --
> Lowell Gilbert, embedded/networking software engineer, Boston area
>   http://be-well.ilk.org/~lowell/
>

Thanks for responding.  I used CVSUP to update the source.  This system is
actually a restore from another server that I dumped from.  The original
server worked just fine (I tried it as an experiment).  This is the only
issue I have seen on the restored server so far.  I just did a binary
upgrade and am now rebuilding all of the ports from scratch.  I will do as
you suggested when that is done (rm -rf /usr/src/) and start from scratch.
 I thought the fact that the compile failed was really strange.  I have
never seen that before.

Chris Maness

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

Re: Kernel Compile Error

[Lowell Gilbert]

Chris Maness <[EMAIL PROTECTED]> writes:

> I was trying to compile a 7.0 Release and the compile failed.  I have
> never had a kernel compilation fail before.
>
> Here is the last of the output:
>
> opt_global.h -fno-common -finline-limit=8000 --param
> inline-unit-growth=100 --param large-function-growth=1000
> -mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx
> -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror
> /usr/src/sys/kern/kern_descrip.c
> /usr/src/sys/kern/kern_descrip.c:211:36: error: macro
> "FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1
> /usr/src/sys/kern/kern_descrip.c: In function 'fdused':
> /usr/src/sys/kern/kern_descrip.c:211: error: 'FILEDESC_LOCK_ASSERT'
> undeclared (first use in this function)
> /usr/src/sys/kern/kern_descrip.c:211: error: (Each undeclared
> identifier is reported only once
> /usr/src/sys/kern/kern_descrip.c:211: error: for each function it
> appears in.)
> /usr/src/sys/kern/kern_descrip.c:227:36: error: macro
> "FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1
> /usr/src/sys/kern/kern_descrip.c: In function 'fdunused':
> /usr/src/sys/kern/kern_descrip.c:227: error: 'FILEDESC_LOCK_ASSERT'
> undeclared (first use in this function)
> cc1: warnings being treated as errors
> /usr/src/sys/kern/kern_descrip.c: In function 'kern_fcntl':
> /usr/src/sys/kern/kern_descrip.c:383: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c:386: warning: implicit declaration of
> function 'FILEDESC_UNLOCK'
> /usr/src/sys/kern/kern_descrip.c:386: warning: nested extern
> declaration of 'FILEDESC_UNLOCK'
> /usr/src/sys/kern/kern_descrip.c:540: warning: implicit declaration of
> function 'FILEDESC_LOCK_FAST'
> /usr/src/sys/kern/kern_descrip.c:540: warning: nested extern
> declaration of 'FILEDESC_LOCK_FAST'
> /usr/src/sys/kern/kern_descrip.c:543: warning: implicit declaration of
> function 'FILEDESC_UNLOCK_FAST'
> /usr/src/sys/kern/kern_descrip.c:543: warning: nested extern
> declaration of 'FILEDESC_UNLOCK_FAST'
> /usr/src/sys/kern/kern_descrip.c: In function 'do_dup':
> /usr/src/sys/kern/kern_descrip.c:631: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c:670: error: 'UF_OPENING' undeclared
> (first use in this function)
> /usr/src/sys/kern/kern_descrip.c: In function 'kern_close':
> /usr/src/sys/kern/kern_descrip.c:994: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c:997: error: 'UF_OPENING' undeclared
> (first use in this function)
> /usr/src/sys/kern/kern_descrip.c:1202:36: error: macro
> "FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1
> /usr/src/sys/kern/kern_descrip.c: In function 'fdgrowtable':
> /usr/src/sys/kern/kern_descrip.c:1202: error: 'FILEDESC_LOCK_ASSERT'
> undeclared (first use in this function)
> /usr/src/sys/kern/kern_descrip.c:1224: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c:1263:36: error: macro
> "FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1
> /usr/src/sys/kern/kern_descrip.c: In function 'fdalloc':
> /usr/src/sys/kern/kern_descrip.c:1263: error: 'FILEDESC_LOCK_ASSERT'
> undeclared (first use in this function)
> /usr/src/sys/kern/kern_descrip.c:1313:36: error: macro
> "FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1
> /usr/src/sys/kern/kern_descrip.c: In function 'fdavail':
> /usr/src/sys/kern/kern_descrip.c:1313: error: 'FILEDESC_LOCK_ASSERT'
> undeclared (first use in this function)
> /usr/src/sys/kern/kern_descrip.c: In function 'falloc':
> /usr/src/sys/kern/kern_descrip.c:1351: warning: implicit declaration
> of function 'suser_cred'
> /usr/src/sys/kern/kern_descrip.c:1351: warning: nested extern
> declaration of 'suser_cred'
> /usr/src/sys/kern/kern_descrip.c:1351: error: 'SUSER_RUID' undeclared
> (first use in this function)
> /usr/src/sys/kern/kern_descrip.c:1376: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c: In function 'fdinit':
> /usr/src/sys/kern/kern_descrip.c:1409: error: 'struct filedesc' has no
> member named 'fd_mtx'
> /usr/src/sys/kern/kern_descrip.c:1409: error: 'FILEDESC_LOCK_DESC'
> undeclared (first use in this function)
> /usr/src/sys/kern/kern_descrip.c:1411: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c: In function 'fddrop':
> /usr/src/sys/kern/kern_descrip.c:1460: error: 'struct filedesc' has no
> member named 'fd_mtx'
> /usr/src/sys/kern/kern_descrip.c: In function 'fdcopy':
> /usr/src/sys/kern/kern_descrip.c:1514: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c:1524: error: 'UF_OPENING' undeclared
> (first use in this function)
> /usr/src/sys/kern/kern_descrip.c:1535: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c: In function 'fdfree':
> /usr/src/sys/kern/kern_descrip.c:1570: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c:1598: warning: statement with no effect
> /usr/src/sys/kern/kern_descrip.c:1612: error: 'struct filedesc' has no
> member named 'fd_mtx'
> /us

Kernel Compile Error

[Chris Maness]

I was trying to compile a 7.0 Release and the compile failed.  I have 
never had a kernel compilation fail before.


Here is the last of the output:

opt_global.h -fno-common -finline-limit=8000 --param 
inline-unit-growth=100 --param large-function-growth=1000  
-mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx 
-mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror  
/usr/src/sys/kern/kern_descrip.c
/usr/src/sys/kern/kern_descrip.c:211:36: error: macro 
"FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1

/usr/src/sys/kern/kern_descrip.c: In function 'fdused':
/usr/src/sys/kern/kern_descrip.c:211: error: 'FILEDESC_LOCK_ASSERT' 
undeclared (first use in this function)
/usr/src/sys/kern/kern_descrip.c:211: error: (Each undeclared identifier 
is reported only once
/usr/src/sys/kern/kern_descrip.c:211: error: for each function it 
appears in.)
/usr/src/sys/kern/kern_descrip.c:227:36: error: macro 
"FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1

/usr/src/sys/kern/kern_descrip.c: In function 'fdunused':
/usr/src/sys/kern/kern_descrip.c:227: error: 'FILEDESC_LOCK_ASSERT' 
undeclared (first use in this function)

cc1: warnings being treated as errors
/usr/src/sys/kern/kern_descrip.c: In function 'kern_fcntl':
/usr/src/sys/kern/kern_descrip.c:383: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c:386: warning: implicit declaration of 
function 'FILEDESC_UNLOCK'
/usr/src/sys/kern/kern_descrip.c:386: warning: nested extern declaration 
of 'FILEDESC_UNLOCK'
/usr/src/sys/kern/kern_descrip.c:540: warning: implicit declaration of 
function 'FILEDESC_LOCK_FAST'
/usr/src/sys/kern/kern_descrip.c:540: warning: nested extern declaration 
of 'FILEDESC_LOCK_FAST'
/usr/src/sys/kern/kern_descrip.c:543: warning: implicit declaration of 
function 'FILEDESC_UNLOCK_FAST'
/usr/src/sys/kern/kern_descrip.c:543: warning: nested extern declaration 
of 'FILEDESC_UNLOCK_FAST'

/usr/src/sys/kern/kern_descrip.c: In function 'do_dup':
/usr/src/sys/kern/kern_descrip.c:631: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c:670: error: 'UF_OPENING' undeclared 
(first use in this function)

/usr/src/sys/kern/kern_descrip.c: In function 'kern_close':
/usr/src/sys/kern/kern_descrip.c:994: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c:997: error: 'UF_OPENING' undeclared 
(first use in this function)
/usr/src/sys/kern/kern_descrip.c:1202:36: error: macro 
"FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1

/usr/src/sys/kern/kern_descrip.c: In function 'fdgrowtable':
/usr/src/sys/kern/kern_descrip.c:1202: error: 'FILEDESC_LOCK_ASSERT' 
undeclared (first use in this function)

/usr/src/sys/kern/kern_descrip.c:1224: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c:1263:36: error: macro 
"FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1

/usr/src/sys/kern/kern_descrip.c: In function 'fdalloc':
/usr/src/sys/kern/kern_descrip.c:1263: error: 'FILEDESC_LOCK_ASSERT' 
undeclared (first use in this function)
/usr/src/sys/kern/kern_descrip.c:1313:36: error: macro 
"FILEDESC_LOCK_ASSERT" passed 2 arguments, but takes just 1

/usr/src/sys/kern/kern_descrip.c: In function 'fdavail':
/usr/src/sys/kern/kern_descrip.c:1313: error: 'FILEDESC_LOCK_ASSERT' 
undeclared (first use in this function)

/usr/src/sys/kern/kern_descrip.c: In function 'falloc':
/usr/src/sys/kern/kern_descrip.c:1351: warning: implicit declaration of 
function 'suser_cred'
/usr/src/sys/kern/kern_descrip.c:1351: warning: nested extern 
declaration of 'suser_cred'
/usr/src/sys/kern/kern_descrip.c:1351: error: 'SUSER_RUID' undeclared 
(first use in this function)

/usr/src/sys/kern/kern_descrip.c:1376: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c: In function 'fdinit':
/usr/src/sys/kern/kern_descrip.c:1409: error: 'struct filedesc' has no 
member named 'fd_mtx'
/usr/src/sys/kern/kern_descrip.c:1409: error: 'FILEDESC_LOCK_DESC' 
undeclared (first use in this function)

/usr/src/sys/kern/kern_descrip.c:1411: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c: In function 'fddrop':
/usr/src/sys/kern/kern_descrip.c:1460: error: 'struct filedesc' has no 
member named 'fd_mtx'

/usr/src/sys/kern/kern_descrip.c: In function 'fdcopy':
/usr/src/sys/kern/kern_descrip.c:1514: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c:1524: error: 'UF_OPENING' undeclared 
(first use in this function)

/usr/src/sys/kern/kern_descrip.c:1535: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c: In function 'fdfree':
/usr/src/sys/kern/kern_descrip.c:1570: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c:1598: warning: statement with no effect
/usr/src/sys/kern/kern_descrip.c:1612: error: 'struct filedesc' has no 
member named 'fd_mtx'
/usr/src/sys/kern/kern_descrip.c:1622: error: 'struct filedesc' has no 
member named 'fd_mtx'

/usr/src/sys/kern/kern_descrip.c:1653: warning: statement with no effect
/usr/sr

Re: Kernel Compile Error

[Giorgos Keramidas]

On 2008-03-03 13:00, Win32 Win32 <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I tried to compile an custom kernel, and i've got a lot of errors.
> I don't know what is the problem, even when i try to compile with
> GENERIC conf file i've got same link errors.  So, what should i do ?

The problem is that you trimmed / commented out too much stuff...

> # Wireless NIC cards
> #devicewlan# 802.11 support
> #devicewlan_wep# 802.11 WEP support
> #devicewlan_ccmp# 802.11 CCMP support
> #devicewlan_tkip# 802.11 TKIP support
> #devicewlan_amrr# AMRR transmit rate control algorithm
> #devicewlan_scan_ap# 802.11 AP mode scanning
> #devicewlan_scan_sta# 802.11 STA mode scanning
[...]
> # USB support
[...]
> devicerum# Ralink Technology RT2501USB wireless NICs
>
>  linker error =
>
> linking kernel
> if_ural.o(.text+0x713): In function `ural_free_tx_list':
> : undefined reference to `ieee80211_free_node'

`rum' is a wireless NIC driver.  You need `wlan' options to compile into
the kernel.

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

Kernel Compile Error

[Win32 Win32]

Hi there,

I tried to compile an custom kernel, and i've got a lot of errors.
I don't know what is the problem, even when i try to compile with GENERIC conf 
file i've got same link errors.
So, what should i do ?
Thanks for help.

#uname -a
FreeBSD  7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008


=== conf file ==

#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.2.2.1 2008/02/06 03:24:28 
scottl Exp $

#cpuI486_CPU
#cpuI586_CPU
cpuI686_CPU
identMyKernel

# To statically compile in device wiring instead of /boot/device.hints
#hints"GENERIC.hints"# Default places to look for devices.

#makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols

options SCHED_4BSD# 4BSD scheduler
options PREEMPTION# Enable kernel thread preemption
options INET# InterNETworking
options INET6# IPv6 communications protocols
options SCTP# Stream Control Transmission Protocol
options FFS# Berkeley Fast Filesystem
options SOFTUPDATES# Enable FFS soft updates support
options UFS_ACL# Support for access control lists
options UFS_DIRHASH# Improve performance on big directories
options UFS_GJOURNAL# Enable gjournal-based UFS journaling
options MD_ROOT# MD is a potential root device
options NFSCLIENT# Network Filesystem Client
options NFSSERVER# Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options MSDOSFS# MSDOS Filesystem
options CD9660# ISO 9660 Filesystem
options PROCFS# Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_PART_GPT# GUID Partition Tables.
options GEOM_LABEL# Provides labelization
options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!]
options COMPAT_FREEBSD4# Compatible with FreeBSD4
options COMPAT_FREEBSD5# Compatible with FreeBSD5
options COMPAT_FREEBSD6# Compatible with FreeBSD6
options SCSI_DELAY=5000# Delay (in ms) before probing SCSI
options KTRACE# ktrace(1) support
options SYSVSHM# SYSV-style shared memory
options SYSVMSG# SYSV-style message queues
options SYSVSEM# SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options ADAPTIVE_GIANT# Giant mutex is adaptive.
options STOP_NMI# Stop CPUS using NMI instead of IPI
options AUDIT# Security event auditing

# To make an SMP kernel, the next two lines are needed
options SMP# Symmetric MultiProcessor Kernel
deviceapic# I/O APIC

# CPU frequency control
devicecpufreq

# Bus support.
deviceeisa
devicepci

# Floppy drives
devicefdc

# ATA and ATAPI devices
deviceata
deviceatadisk# ATA disk drives
deviceataraid# ATA RAID drives
deviceatapicd# ATAPI CDROM drives
deviceatapifd# ATAPI floppy drives
deviceatapist# ATAPI tape drives
options ATA_STATIC_ID# Static device numbering

# SCSI Controllers
deviceahb# EISA AHA1742 family
deviceahc# AHA2940 and onboard AIC7xxx devices
options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~128k to driver.
deviceahd# AHA39320/29320 and onboard AIC79xx devices
options AHD_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~215k to driver.
deviceamd# AMD 53C974 (Tekram DC-390(T))
devicehptiop# Highpoint RocketRaid 3xxx series
deviceisp# Qlogic family
#device ispfw# Firmware for QLogic HBAs- normally a module
devicempt# LSI-Logic MPT-Fusion
#devicencr# NCR/Symbios Logic
devicesym# NCR/Symbios Lo

Re: Kernel Compile Error

[Schiz0]

On Nov 28, 2007 12:17 PM, Philip M. Gollucci <[EMAIL PROTECTED]> wrote:
> Schiz0 wrote:
> > On Nov 28, 2007 8:47 AM, Philip M. Gollucci <[EMAIL PROTECTED]> wrote:
> >> Schiz0 wrote:
> >>> Hey,
> >>>
> >>> I'm running FreeBSD 6.3-PRERELEASE. I recently csuped the source code
> >>> (src-all) and built world.
> >>> I then tried to "make buildkernel", and it ran for a little while,
> >>> then gave the following error and stopped:
> >>>
> >>> http://schiz0.securityexploits.com/make.buildkernel.out
> >>> The error is at the bottom - that is the log of the entire buildkernel 
> >>> process.
> >> I see no error -- looks like you didnt' copy enough of it.
> >> use -DNO_CLEAN to skip all the rm -f stuff at the start when you post
> >> the new output.
> >>

>
> Add these 3 to your kernel config file near the end. Don't use the
> -DNO_CLEAN when you build this time.  That was just to cut down on the
> output in the log file (or when you intentionally don't want to delete
> the build from the previous attempt or success)
>
> options SYSVSHM #SYSV-style shared memory
> options SYSVMSG #SYSV-style message queues
> options SYSVSEM #SYSV-style semaphores
>

Worked perfectly. Thanks. I took those lines out of the kernel config
because I wasn't sure what SYSV-style was (And figured I didn't need
it since I didn't know what it was, hehe).

Thanks for the help.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compile Error

[Philip M. Gollucci]

Schiz0 wrote:
> On Nov 28, 2007 8:47 AM, Philip M. Gollucci <[EMAIL PROTECTED]> wrote:
>> Schiz0 wrote:
>>> Hey,
>>>
>>> I'm running FreeBSD 6.3-PRERELEASE. I recently csuped the source code
>>> (src-all) and built world.
>>> I then tried to "make buildkernel", and it ran for a little while,
>>> then gave the following error and stopped:
>>>
>>> http://schiz0.securityexploits.com/make.buildkernel.out
>>> The error is at the bottom - that is the log of the entire buildkernel 
>>> process.
>> I see no error -- looks like you didnt' copy enough of it.
>> use -DNO_CLEAN to skip all the rm -f stuff at the start when you post
>> the new output.
>>
linux_ipc.o(.text+0x8e4):/usr/src/sys/compat/linux/linux_ipc.c:583:
undefined reference to `__semctl'^M
linux_ipc.o(.text+0x918): In function `linux_msgsnd':^M
/usr/src/sys/compat/linux/linux_ipc.c:600: undefined reference to `msgsnd'^M
linux_ipc.o(.text+0x94e): In function `linux_msgrcv':^M
/usr/src/sys/compat/linux/linux_ipc.c:619: undefined reference to `msgrcv'^M
linux_ipc.o(.text+0x970): In function `linux_msgget':^M
/usr/src/sys/compat/linux/linux_ipc.c:632: undefined reference to `msgget'^M
linux_ipc.o(.text+0x9d2): In function `linux_msgctl':^M
/usr/src/sys/compat/linux/linux_ipc.c:650: undefined reference to
`kern_msgctl'^M
linux_ipc.o(.text+0xa4d): In function `linux_shmat':^M
/usr/src/sys/compat/linux/linux_ipc.c:680: undefined reference to `shmat'^M
linux_ipc.o(.text+0xaae): In function `linux_shmdt':^M
/usr/src/sys/compat/linux/linux_ipc.c:699: undefined reference to `shmdt'^M
linux_ipc.o(.text+0xad6): In function `linux_shmget':^M
/usr/src/sys/compat/linux/linux_ipc.c:714: undefined reference to `shmget'^M
linux_ipc.o(.text+0xb18): In function `linux_shmctl':^M
/usr/src/sys/compat/linux/linux_ipc.c:733: undefined reference to
`kern_shmctl'^M
linux_ipc.o(.text+0xb68):/usr/src/sys/compat/linux/linux_ipc.c:748:
undefined reference to `kern_shmctl'^M
linux_ipc.o(.text+0xbb0):/usr/src/sys/compat/linux/linux_ipc.c:761:
undefined reference to `kern_shmctl'^M
linux_ipc.o(.text+0xc00):/usr/src/sys/compat/linux/linux_ipc.c:773:
undefined reference to `kern_shmctl'^M
linux_ipc.o(.text+0xc7c):/usr/src/sys/compat/linux/linux_ipc.c:792:
undefined reference to `kern_shmctl'^M
linux_ipc.o(.text+0xcd2):/usr/src/sys/compat/linux/linux_ipc.c:808: more
undefined references to `kern_shmctl' follow^M

Add these 3 to your kernel config file near the end. Don't use the
-DNO_CLEAN when you build this time.  That was just to cut down on the
output in the log file (or when you intentionally don't want to delete
the build from the previous attempt or success)

options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores

-- 

Philip M. Gollucci ([EMAIL PROTECTED])
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB  B89E 1324 9B4F EC88 A0BF

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

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

Re: Kernel Compile Error

[Schiz0]

On Nov 28, 2007 8:47 AM, Philip M. Gollucci <[EMAIL PROTECTED]> wrote:
> Schiz0 wrote:
> > Hey,
> >
> > I'm running FreeBSD 6.3-PRERELEASE. I recently csuped the source code
> > (src-all) and built world.
> > I then tried to "make buildkernel", and it ran for a little while,
> > then gave the following error and stopped:
> >
> > http://schiz0.securityexploits.com/make.buildkernel.out
> > The error is at the bottom - that is the log of the entire buildkernel 
> > process.
> I see no error -- looks like you didnt' copy enough of it.
> use -DNO_CLEAN to skip all the rm -f stuff at the start when you post
> the new output.
>

Hey,

That make.buildkernel.out is the entire output of that make
buildkernel process. I used "script /root/make.buildkernel.out" to
record it, then just copied the file to my web server. I didn't
manually copy/paste or edit anything out.

I cleared /usr/obj/ and ran "make cleandir" twice, as the Handbook
says to. I then recompiled world without any error.

I ran "make -DNO_CLEAN buildkernel KERNCONF=my kernel config" and got
the following output:
http://schiz0.securityexploits.com/make.buildkernel2.out

It doesn't look like it provides any more information than the
previous output did. It's obviously some error with the COMPAT_LINUX
option   in the kernel config.

Thanks for the help and the quick reply,
~Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compile Error

[Philip M. Gollucci]

Schiz0 wrote:
> Hey,
> 
> I'm running FreeBSD 6.3-PRERELEASE. I recently csuped the source code
> (src-all) and built world.
> I then tried to "make buildkernel", and it ran for a little while,
> then gave the following error and stopped:
> 
> http://schiz0.securityexploits.com/make.buildkernel.out
> The error is at the bottom - that is the log of the entire buildkernel 
> process.
I see no error -- looks like you didnt' copy enough of it.
use -DNO_CLEAN to skip all the rm -f stuff at the start when you post
the new output.

-- 

Philip M. Gollucci ([EMAIL PROTECTED])
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB  B89E 1324 9B4F EC88 A0BF

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

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

Kernel Compile Error

[Schiz0]

Hey,

I'm running FreeBSD 6.3-PRERELEASE. I recently csuped the source code
(src-all) and built world.
I then tried to "make buildkernel", and it ran for a little while,
then gave the following error and stopped:

http://schiz0.securityexploits.com/make.buildkernel.out
The error is at the bottom - that is the log of the entire buildkernel process.

I recompiled my kernel cause I wanted to add linux support.
The only change I made to my kernel config, was adding the line:
optionsCOMPAT_LINUX

Compiling the kernel using the same config (Without that COMPAT_LINUX
line) worked perfectly in the past.

Thanks for your time,
~Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make depend kernel compile error

[Lowell Gilbert]

Peter Miller <[EMAIL PROTECTED]> writes:

> I'm running a clean install of the freebsd 5.4 and i'm
> building a new kernel with usb 2.0 support but i'm
> getting the following error after typing make depend.

Go back to the GENERIC kernel.  Change a small number of things at a
time until you have figured out which config file change caused the
kernel to stop compiling.  Armed with that knowledge, you should be
able to ask how to do that change properly.  It would be polite to
look at the relevant manual page for that config entry before asking
on a mailing list, though.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make depend kernel compile error [solved]

[Peter Miller]

Sorry, i wasn't too clear.  The only thing I changed
to the config was the addition of the usb2 support.  I
had tried compiling the generic kernel which didn't
work either.  The good news is that I installed and
ran cvsup and used the 2nd compile method in the
handbook (after running make clean) and the kernel
compiled.

Thanks
 
--- Lowell Gilbert
<[EMAIL PROTECTED]> wrote:
> Peter Miller <[EMAIL PROTECTED]> writes:
> 
> > I'm running a clean install of the freebsd 5.4 and
> i'm
> > building a new kernel with usb 2.0 support but i'm
> > getting the following error after typing make
> depend.
> 
> Go back to the GENERIC kernel.  Change a small
> number of things at a
> time until you have figured out which config file
> change caused the
> kernel to stop compiling.  Armed with that
> knowledge, you should be
> able to ask how to do that change properly.  It
> would be polite to
> look at the relevant manual page for that config
> entry before asking
> on a mailing list, though.
> 

__ 
Post your free ad now! http://personals.yahoo.ca
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

make depend kernel compile error

[Peter Miller]

I'm running a clean install of the freebsd 5.4 and i'm
building a new kernel with usb 2.0 support but i'm
getting the following error after typing make depend.

basement# make depend
rm -f .olddep
if [ -f .depend ]; then mv .depend .olddep; fi
make _kernel-depend
cc -c -O -pipe -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-
arith -Winline -Wcast-qual -fformat-extensions
-std=c99 -nostdinc -I- -I. -I../../..
-I../../../contrib/dev
/acpica -I../../../contrib/altq
-I../../../contrib/ipfilter -I../../../contrib/pf
-I../../../contrib/dev/at
h -I../../../contrib/dev/ath/freebsd
-I../../../contrib/ngatm -D_KERNEL -include
opt_global.h -finline-limi
t=8000 --param inline-unit-growth=100 --param
large-function-growth=1000 -mno-align-long-strings
-mpreferre
d-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse
-mno-sse2 -ffreestanding ../../../i386/i386/genassym.c
../../../i386/i386/genassym.c:35:23: sys/cdefs.h: No
such file or directory
../../../i386/i386/genassym.c:36: error: syntax error
before string constant
../../../i386/i386/genassym.c:42:23: sys/param.h: No
such file or directory
../../../i386/i386/genassym.c:43:23: sys/systm.h: No
such file or directory
../../../i386/i386/genassym.c:44:23: sys/assym.h: No
such file or directory
../../../i386/i386/genassym.c:45:21: sys/bio.h: No
such file or directory
../../../i386/i386/genassym.c:46:21: sys/buf.h: No
such file or directory
../../../i386/i386/genassym.c:47:22: sys/proc.h: No
such file or directory
../../../i386/i386/genassym.c:48:23: sys/errno.h: No
such file or directory
../../../i386/i386/genassym.c:49:23: sys/mount.h: No
such file or directory
../../../i386/i386/genassym.c:50:23: sys/mutex.h: No
such file or directory
../../../i386/i386/genassym.c:51:24: sys/socket.h: No
such file or directory
../../../i386/i386/genassym.c:52:29:
sys/resourcevar.h: No such file or directory
../../../i386/i386/genassym.c:53:27: sys/signalvar.h:
No such file or directory
../../../i386/i386/genassym.c:54:26: sys/ucontext.h:
No such file or directory
In file included from
../../../i386/i386/genassym.c:55:
./machine/bootinfo.h:49: error: syntax error before
"u_int32_t"
../../../i386/i386/genassym.c:57:25: sys/vmmeter.h: No
such file or directory
../../../i386/i386/genassym.c:58:19: vm/vm.h: No such
file or directory
../../../i386/i386/genassym.c:59:25: vm/vm_param.h: No
such file or directory
../../../i386/i386/genassym.c:60:21: vm/pmap.h: No
such file or directory
../../../i386/i386/genassym.c:61:23: vm/vm_map.h: No
such file or directory
../../../i386/i386/genassym.c:63:20: net/if.h: No such
file or directory
../../../i386/i386/genassym.c:64:24: netinet/in.h: No
such file or directory
../../../i386/i386/genassym.c:65:26: nfs/nfsproto.h:
No such file or directory
../../../i386/i386/genassym.c:66:23: nfs/rpcv2.h: No
such file or directory
../../../i386/i386/genassym.c:67:27: nfsclient/nfs.h:
No such file or directory
../../../i386/i386/genassym.c:68:35:
nfsclient/nfsdiskless.h: No such file or directory
In file included from
../../../i386/i386/genassym.c:70:
./machine/apicreg.h:122:23: sys/types.h: No such file
or directory
In file included from
../../../i386/i386/genassym.c:70:
./machine/apicreg.h:130: error: syntax error before
"u_int32_t"
./machine/apicreg.h:131: error: syntax error before
"u_int32_t"
./machine/apicreg.h:136: error: syntax error before
"u_int32_t"
./machine/apicreg.h:137: error: syntax error before
"u_int32_t"

I cut the error message short...let me know if i shold
post the whole thing.

I'm following the handbook for compiling a kernel and
the only thing I changed was the line affecting usb2
by removing the #

Again, my system is a fresh install and i have hardly
done anything yet...just added a few packages with
pkg_add -r (i haven't done any updates)

Thanks
Peter

__ 
Post your free ad now! http://personals.yahoo.ca
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kernel compile error

[Dick Davies]

* Brian Bobowski <[EMAIL PROTECTED]> [1134 14:34]:
> Joshua Lokken wrote:
> 
> >>On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote:
> >>   
> >>
> >>>Matt Emmerton wrote:
> >>> 
> >>>
> >>>Having such a mechanism, would prevent lots of beginners in the
> >>>kernel compiling stuff, to get frustrated with errors like above.
> >>> 
> >>>
> >Also, as you see, it's well-documented in the kernel config file ;)
> > 
> >
> While this is true, it's also easy enough for someone to snip the 
> directions when slicing things out of the config file. Assuming that the 
> user won't do things the wrong way is a sure way to succumb to Murphy's 
> Law(the real one).

Yeah, but assuming a user who can't read a comment is happy enough to 
go editing a kernel config file, that's their funeral.

"we'll err on the side of handing out rope and guns to all interested
parties while hoping you have enough smarts to keep from hanging yourself
or shooting yourself in the foot." - html, the definitive guide

> The main barrier I can see to this is getting whatever parses the config 
> file to recognise such dependencies

I agree it should be fixed in config if anywhere, but it's worth bearing
in mind that kernel compiles on any platform are still non-trivial.

I did a kernel build on Debian yesterday and it took half a dozen goes to 
get a USB mouse working because usbhid wasn't there. No warnings, just 
shedloads of insmod failures on reboot. Nice.

At least our compiler craps out :)

-- 
What have you done to the cat? It looks half-dead. - Schroedinger's wife
Rasputin :: Jack of All Trades - Master of Nuns
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kernel compile error

[Gert Cuykens]

On Fri, 26 Nov 2004 09:32:08 -0500, Brian Bobowski <[EMAIL PROTECTED]> wrote:
> Joshua Lokken wrote:
> 
> >>On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote:
> >>
> >>
> >>>Matt Emmerton wrote:
> >>>
> >>>
> >>>Having such a mechanism, would prevent lots of beginners in the
> >>>kernel compiling stuff, to get frustrated with errors like above.
> >>>
> >>>
> >Also, as you see, it's well-documented in the kernel config file ;)
> >
> >
> While this is true, it's also easy enough for someone to snip the
> directions when slicing things out of the config file. Assuming that the
> user won't do things the wrong way is a sure way to succumb to Murphy's
> Law(the real one).
> 
> The main barrier I can see to this is getting whatever parses the config
> file to recognise such dependencies; as it is, it's the compiler that
> runs into the problem, not the program that calls the compiler. The
> compiler doesn't know where the relevant source is if not told to
> include it, after all.
> 
> -BB
> 
> 
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 

this is how a teletubie config file look like , teletubies dont like
big files the prefer small ones.

machine amd64
cpu HAMMER
ident   GERT   

options SCHED_4BSD  # ?
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT   # Network Filesystem Client
options NFSSERVER   # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options NTFS# NT File System
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_GPT# GUID Partition Tables.
options COMPAT_IA32 # Compatible with i386 binaries
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options SCSI_DELAY=15000# Delay (in ms) before probing SCSI
options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # Posix P1003_1B real-time extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
output.  Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in debug
output.  Adds ~215k to driver.
options ADAPTIVE_GIANT  # Giant mutex is adaptive.
options NO_MIXED_MODE   # SK8N
options ATA_STATIC_ID   # Static device numbering
options UDF # DJO 

device  atpic   # 8259A compatability
device  acpi# Bus support
device  isa # Bus support
device  pci # Bus support
device  fdc # Floppy drives
device  ata # ATA and ATAPI devices
device  atadisk # ATA disk drives
device  ataraid # ATA RAID drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
device  atapist # ATAPI tape drives
device  scbus   # SCSI bus (required for SCSI)
device  ch  # SCSI media changers
device  da  # Direct Access (disks)
device  sa  # Sequential Access (tape etc)
device  cd  # CD
device  pass# Passthrough device (direct SCSI access)
device  ses # SCSI Environmental Services (and SAF-TE)
device  atkbdc  # AT keyboard controller
device  atkbd   # AT keyboard
device  psm # PS/2 mouse
device  vga # VGA video card driver
device  splash  # Splash screen and screen saver support
device  sc  # syscons is the default console
driver, resembling an SCO console
device  cbb # cardbus (yenta) bridge
device  pccard

Re: kernel compile error

[Brian Bobowski]

Joshua Lokken wrote:
On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote:
   

Matt Emmerton wrote:
 

Having such a mechanism, would prevent lots of beginners in the
kernel compiling stuff, to get frustrated with errors like above.
 

Also, as you see, it's well-documented in the kernel config file ;)
 

While this is true, it's also easy enough for someone to snip the 
directions when slicing things out of the config file. Assuming that the 
user won't do things the wrong way is a sure way to succumb to Murphy's 
Law(the real one).

The main barrier I can see to this is getting whatever parses the config 
file to recognise such dependencies; as it is, it's the compiler that 
runs into the problem, not the program that calls the compiler. The 
compiler doesn't know where the relevant source is if not told to 
include it, after all.

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

Re: kernel compile error

[Joshua Lokken]

> On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote:
> > Matt Emmerton wrote:
> > >>/usr/src/sys/pci/if_rl.c:122:23: miibus_if.h: No such file or directory
> > >>mkdep: compile failed
> > >
> > >
> > >You need "device miibus" in your kernel config if you want to use "device
> > >rl".
> > Having such a mechanism, would prevent lots of beginners in the
> > kernel compiling stuff, to get frustrated with errors like above.

Also, as you see, it's well-documented in the kernel config file ;)

-- 
Joshua Lokken
Open Source Advocate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kernel compile error

[Kris Kennaway]

On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote:
> Matt Emmerton wrote:
> >
> >>/usr/src/sys/dev/usb/if_rue.c:104:23: miibus_if.h: No such file or
> >
> >directory
> >
> >>/usr/src/sys/pci/if_rl.c:122:23: miibus_if.h: No such file or directory
> >>mkdep: compile failed
> >
> >
> >You need "device miibus" in your kernel config if you want to use "device
> >rl".
> 
> I always wonder why there has not yet been constructed a mechanism that
> automatically pulls in devices that are needed to prevent compile failure.
> 
> It wouldn't be too difficult, I assume, to have "device miibus" pulled
> in, when needed for certain devices.
> 
> Or is there a good reason to allow people to compile, for example
> "device rl", without the miibus device?
> 
> Having such a mechanism, would prevent lots of beginners in the
> kernel compiling stuff, to get frustrated with errors like above.

Let us know when it's ready :)

Kris


pgp8ZKBHio2NU.pgp
Description: PGP signature

Re: kernel compile error

[Rob]

Matt Emmerton wrote:

/usr/src/sys/dev/usb/if_rue.c:104:23: miibus_if.h: No such file or
directory
/usr/src/sys/pci/if_rl.c:122:23: miibus_if.h: No such file or directory
mkdep: compile failed

You need "device miibus" in your kernel config if you want to use "device
rl".
I always wonder why there has not yet been constructed a mechanism that
automatically pulls in devices that are needed to prevent compile failure.
It wouldn't be too difficult, I assume, to have "device miibus" pulled
in, when needed for certain devices.
Or is there a good reason to allow people to compile, for example
"device rl", without the miibus device?
Having such a mechanism, would prevent lots of beginners in the
kernel compiling stuff, to get frustrated with errors like above.
Rob.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kernel compile error

[Matt Emmerton]

> /usr/src/sys/dev/usb/if_rue.c:104:23: miibus_if.h: No such file or
directory
> /usr/src/sys/pci/if_rl.c:122:23: miibus_if.h: No such file or directory
> mkdep: compile failed

You need "device miibus" in your kernel config if you want to use "device
rl".



# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device  miibus  # MII bus support
device  dc  # DEC/Intel 21143 and various workalikes
device  fxp # Intel EtherExpress PRO/100B (82557, 82558)
device  pcn # AMD Am79C97x PCI 10/100 NICs
device  rl  # RealTek 8129/8139




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

kernel compile error

[Gert Cuykens]

/usr/src/sys/dev/usb/if_rue.c:104:23: miibus_if.h: No such file or directory
/usr/src/sys/pci/if_rl.c:122:23: miibus_if.h: No such file or directory
mkdep: compile failed
*** Error code 1

Stop in /usr/obj/usr/src/sys/gert.
*** Error code 1

Stop in /usr/obj/usr/src/sys/gert.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
7rxI#
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compile Error

[Bill Moran]

Not 100% sure, but you don't have a keyboard device in your kernel
(device atkbdc0).  I figure if you're compiling in a console (sc0),
that you'll need at least atkbdc0.

Ryan <[EMAIL PROTECTED]> wrote:

> bash-2.05b# make buildkernel KERNCONF=POTL
> 
> --
> >>> Kernel build for POTL started on Mon Aug  9 09:07:24 EST 2004
> --
> ===> POTL
> 
> Skiping To The End
> 
> cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
> -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
> -fformat-extensions -ansi  -nostdinc -I- -I. -I/usr/src/sys 
> -I/usr/src/sys/../include -I/usr/src/sys/contrib/dev/acpica 
> -I/usr/src/sys/contrib/ipfilter  -D_KERNEL -include opt_global.h  
> -mpreferred-stack-boundary=2  setdef1.c
> touch hack.c
> cc -shared -nostdlib hack.c -o hack.So
> rm -f hack.c
> sh /usr/src/sys/conf/newvers.sh POTL 
> cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
> -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
> -fformat-extensions -ansi  -nostdinc -I- -I. -I/usr/src/sys 
> -I/usr/src/sys/../include -I/usr/src/sys/contrib/dev/acpica 
> -I/usr/src/sys/contrib/ipfilter  -D_KERNEL -include opt_global.h  
> -mpreferred-stack-boundary=2  vers.c
> linking kernel
> kbd.o: In function `kbd_register':
> kbd.o(.text+0x314): undefined reference to `kbddriver_set'
> kbd.o(.text+0x31b): undefined reference to `kbddriver_set'
> kbd.o: In function `kbd_get_switch':
> kbd.o(.text+0x429): undefined reference to `kbddriver_set'
> kbd.o(.text+0x42e): undefined reference to `kbddriver_set'
> kbd.o: In function `kbd_configure':
> kbd.o(.text+0x6b3): undefined reference to `kbddriver_set'
> kbd.o(.text+0x6b8): more undefined references to `kbddriver_set' follow
> *** Error code 1
> 
> Stop in /usr/obj/usr/src/sys/POTL.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> 
> 
> 
> 
> (Kernel Config
> 
> machine i386
> cpu I686_CPU
> ident   POTL
> maxusers0
> 
> options INET#InterNETworking
> options FFS #Berkeley Fast Filesystem
> options FFS_ROOT#FFS usable as root device [keep this!]
> options SOFTUPDATES #Enable FFS soft updates support
> options UFS_DIRHASH #Improve performance on big directories
> options MFS #Memory Filesystem
> options MD_ROOT #MD is a potential root device
> options CD9660  #ISO 9660 Filesystem   
> options CD9660_ROOT #CD-ROM usable as root, CD9660 required
> options PROCFS  #Process filesystem  
> options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
> options SCSI_DELAY=15000#Delay (in ms) before probing SCSI
> options USERCONFIG  #boot -c editor
> options VISUAL_USERCONFIG   #visual boot -c editor
> options KTRACE  #ktrace(1) support
> options SYSVSHM #SYSV-style shared memory
> options SYSVMSG #SYSV-style message queues
> options SYSVSEM #SYSV-style semaphores
> options P1003_1B#Posix P1003_1B real-time extensions
> options _KPOSIX_PRIORITY_SCHEDULING
> options ICMP_BANDLIM#Rate limit bad replies
> options KBD_INSTALL_CDEV# install a CDEV entry in /dev
> options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
> # output.  Adds ~128k to driver.
> options AHD_REG_PRETTY_PRINT# Print register bitfields in debug
> # output.  Adds ~215k to driver.
> 
> device  ata
> device  atadisk # ATA disk drives
> device  atapicd # ATAPI CDROM drives
> device  atapifd # ATAPI floppy drives
> options ATA_STATIC_ID   #Static device numbering
> 
> device  stg # TMC 18C30/18C50
> device  scbus   # SCSI bus (required)
> device  vga0at isa?
> pseudo-device   splash
> device  sc0 at isa? flags 0x100
> device  agp # support several AGP chipsets
> device  npx0at nexus? port IO_NPX irq 13
> device  apm0at nexus? disable flags 0x20 # Advanced Power Management
> device  sio0at isa? port IO_COM1 flags 0x10 irq 4
> device  sio1at isa? port IO_COM2 irq 3
> device  miibus  # MII bus support
> device  vr  

Kernel Compile Error

[Ryan]

bash-2.05b# make buildkernel KERNCONF=POTL

--
>>> Kernel build for POTL started on Mon Aug  9 09:07:24 EST 2004
--
===> POTL

Skiping To The End

cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -ansi  -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include 
-I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter  -D_KERNEL -include 
opt_global.h  -mpreferred-stack-boundary=2  setdef1.c
touch hack.c
cc -shared -nostdlib hack.c -o hack.So
rm -f hack.c
sh /usr/src/sys/conf/newvers.sh POTL 
cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -ansi  -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include 
-I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter  -D_KERNEL -include 
opt_global.h  -mpreferred-stack-boundary=2  vers.c
linking kernel
kbd.o: In function `kbd_register':
kbd.o(.text+0x314): undefined reference to `kbddriver_set'
kbd.o(.text+0x31b): undefined reference to `kbddriver_set'
kbd.o: In function `kbd_get_switch':
kbd.o(.text+0x429): undefined reference to `kbddriver_set'
kbd.o(.text+0x42e): undefined reference to `kbddriver_set'
kbd.o: In function `kbd_configure':
kbd.o(.text+0x6b3): undefined reference to `kbddriver_set'
kbd.o(.text+0x6b8): more undefined references to `kbddriver_set' follow
*** Error code 1

Stop in /usr/obj/usr/src/sys/POTL.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.




(Kernel Config

machine i386
cpu I686_CPU
ident   POTL
maxusers0

options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options SOFTUPDATES #Enable FFS soft updates support
options UFS_DIRHASH #Improve performance on big directories
options MFS #Memory Filesystem
options MD_ROOT #MD is a potential root device
options CD9660  #ISO 9660 Filesystem   
options CD9660_ROOT #CD-ROM usable as root, CD9660 required
options PROCFS  #Process filesystem  
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=15000#Delay (in ms) before probing SCSI
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B#Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM#Rate limit bad replies
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~215k to driver.

device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
options ATA_STATIC_ID   #Static device numbering

device  stg # TMC 18C30/18C50
device  scbus   # SCSI bus (required)
device  vga0at isa?
pseudo-device   splash
device  sc0 at isa? flags 0x100
device  agp # support several AGP chipsets
device  npx0at nexus? port IO_NPX irq 13
device  apm0at nexus? disable flags 0x20 # Advanced Power Management
device  sio0at isa? port IO_COM1 flags 0x10 irq 4
device  sio1at isa? port IO_COM2 irq 3
device  miibus  # MII bus support
device  vr  # VIA Rhine, Rhine II
pseudo-device   loop# Network loopback
pseudo-device   ether   # Ethernet support
pseudo-device   tun # Packet tunnel.
pseudo-device   pty # Pseudo-ttys (telnet etc)
pseudo-device   md  # Memory "disks"
options MAXDSIZ="(256*1024*1024)"
options MAXSSIZ="(256*1024*1024)"
options DFLDSIZ="(256*1024*102

Re: kernel compile error

[Danny Pansters]

[CC'd to -questions so that it gets archived]

On Sunday 29 February 2004 04:56, you wrote:
> > Never run "make world" literally. Run make buildworld, make kernel, make
> > installworld, mergemaster.
> >
> >> Or is it possible that my GENERIC file is wrong?
> >
> > Yes, you edited too much out. This is a FAQ:
> >> #device scbus   # SCSI bus (required for SCSI)
> >> device  umass   # Disks/Mass storage - Requires scbus
> >> and
>
> i dont have any SCSI devices.  Is it still needed?  Can you give me
> specific instructions to clean my slate and start over from the
> buildworld part?

It's needed because USB disks work through the SCSI interface, that is as if 
they were SCSI disks.

> IS there a howto that is very detailed that you have?

The Handbook. Apart from that, for kernel options and devices you can look 
at /usr/src/sys/conf/NOTES for architecture independent stuff, 
and /usr/src/sys/i386/conf/NOTES for specific i386 kernel options and other 
knobs. In 4.x this used to be the LINT file.

> btw, i did the thing the other guy said to do
>
> cd /usr/src/sys/i386/conf/
> edited GENERIC file
>
> couldn't find
> cd ../compile/GENERIC [i typed it as you wrote, didnt work, so i went into
> ../compile and #ls but no files

This is often (wrongly) referred to as "the old method" to build a kernel. 
You'll use configure, make depend, make install if you want to compile a 
custom kernel against your installed version ("world") of FreeBSD. 

The often (wrongly) called "new method" is make kernel KERNCONF=BLAH 
from /usr/src. Now you are building a kernel against what's in your object 
tree (/usr/obj). Normally it will be have been populated when you did a make 
buildworld. You're going to install that version (world) later on, so you'll 
want a kernel that is built against this "future world" and with its 
toolchain. The difference seems subtle, but if you don't do this, you may 
find yourself with an unbootable kernel after you've run installworld, or a 
kernel that boots but a userland that gives you nothing but coredumps if it 
doesn't panic at init right away.

Of course you can have a situation in which your object tree holds the same 
"world" that you're currently running and it is in that case and in that case 
only that you can safely use either method to build a custom kernel. 

To be fair, you can get away with using the wrong kernel build method if 
there's only minor differences between the currently installed and the newly 
built worlds if you're lucky but still it may cause certain quirks and 
instabilities that are quite impossible to pin down. Things like seemingly 
random panics or reboots that never get explained.

> so i went into
> #cd /usr/src and then
> make clean && make depend && make && make install

I think this effectly translates to running "make world".

> and it worked out.  could i work with that??  or should i do a clean slate
> reinstall?

Well, I wouldn't recommend making it into a habit but if you got your bootable 
system with kernel and world from the same codebase ("in sync" as they say) 
and it runs OK, then just stick with it.

Please note that if all you want is to rebuild your kernel without updating 
FreeBSD itself, you don't have to cvsup or make world at all. Just use the 
so-called "old method". Also, in that case you only need the kernel source 
which you can simply extract from your install CD manually or with 
sysinstall. 

FreeBSD kernels are not versioned, the whole FreeBSD OS is. Cvsup and building 
world is moving to another version and in that case the kernel you build 
while going through your updating procedure should match that OS version. 
With Linux, the kernel *is* seperately versioned and the rest of a 
distribution can be considered something like our ports. So it's different 
concepts and it seems to never cease confusing the heck out of people :)


HTH,

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

RE: kernel compile error

[Remko Lodder]

Overlooked this email,
And overlooked the make world process,

My apologies for giving inaccurate information

Cheers,

--

Kind regards,

Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl Dutch community for helping newcomers on the
hackerscene

mrtg.grunn.org Dutch mirror of MRTG

-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Danny Pansters
Verzonden: zondag 29 februari 2004 2:31
Aan: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Onderwerp: Re: kernel compile error


On Sunday 29 February 2004 01:52, [EMAIL PROTECTED] wrote:
> Im kinda new at this and
>
> I was compiling my kernel on my Dell Inspiron600m running FreeBSD 5.2
> RELEASE when I just remembered[after taking a nap] that I did
>
> #make buildkernel KERNCONF=GENERIC

If you build your own kernel, you should give it another name than GENERIC
(and change ident in your config file).

>
> and I forgot to edit the /usr/src/sys/i386/conf/GENERIC file before
> running the process.
>
> anyway, the #make buildkernel completed and i wanted to change the GENERIC
> file so i went aroung and commented out all the stuff that i didnt have on
> my system and did a #make buildkernel KERNCONF=GENERIC again only to have
> errors after about a minute into the process.
>
> My Questions Are:
> Is it wrong to do this process again after a successful #make buildkernel?
> If so, what should I do to do it successfully? [should i rm -rf /usr/src
> && cvsup -g -L 2 /etc/standard-supfile && make world again?]

Never run "make world" literally. Run make buildworld, make kernel, make
installworld, mergemaster.

>
> Or is it possible that my GENERIC file is wrong?

Yes, you edited too much out. This is a FAQ:

> #device scbus   # SCSI bus (required for SCSI)
> device  umass   # Disks/Mass storage - Requires scbus and

HTH,

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

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

RE: kernel compile error

[Remko Lodder]

He stated that he used:

#make buildkernel KERNCONF=GENERIC

That is not a make world, so he can safely recompile his kernel in my
opinion,
Will try to examine his problem today :)

Cheers

--

Kind regards,

Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl Dutch community for helping newcomers on the
hackerscene

-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Danny Pansters
Verzonden: zondag 29 februari 2004 2:33
Aan: [EMAIL PROTECTED]
Onderwerp: Re: kernel compile error


On Sunday 29 February 2004 01:39, Remko Lodder wrote:
> Hi dude,
>
> It's not harmfull to replay the whole process,
> The way i do it is go to the dir
>
> cd /usr/src/sys/i386/conf/
> edit the GENERIC file,
> cd ../compile/GENERIC
> make clean && make depend && make && make install
> the && makes sure the next command only get's runned when
> the previous command complete succesfully or returned status 0 (success in
> almost every case :))

You shouldn't do this while in a 'make world' cycle. (or if you insist do it
from /usr/obj instead)


HTH,

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

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

Re: kernel compile error

[Danny Pansters]

On Sunday 29 February 2004 01:39, Remko Lodder wrote:
> Hi dude,
>
> It's not harmfull to replay the whole process,
> The way i do it is go to the dir
>
> cd /usr/src/sys/i386/conf/
> edit the GENERIC file,
> cd ../compile/GENERIC
> make clean && make depend && make && make install
> the && makes sure the next command only get's runned when
> the previous command complete succesfully or returned status 0 (success in
> almost every case :))

You shouldn't do this while in a 'make world' cycle. (or if you insist do it 
from /usr/obj instead)


HTH,

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

Re: kernel compile error

[Danny Pansters]

On Sunday 29 February 2004 01:52, [EMAIL PROTECTED] wrote:
> Im kinda new at this and
>
> I was compiling my kernel on my Dell Inspiron600m running FreeBSD 5.2
> RELEASE when I just remembered[after taking a nap] that I did
>
> #make buildkernel KERNCONF=GENERIC

If you build your own kernel, you should give it another name than GENERIC 
(and change ident in your config file). 

>
> and I forgot to edit the /usr/src/sys/i386/conf/GENERIC file before
> running the process.
>
> anyway, the #make buildkernel completed and i wanted to change the GENERIC
> file so i went aroung and commented out all the stuff that i didnt have on
> my system and did a #make buildkernel KERNCONF=GENERIC again only to have
> errors after about a minute into the process.
>
> My Questions Are:
> Is it wrong to do this process again after a successful #make buildkernel?
> If so, what should I do to do it successfully? [should i rm -rf /usr/src
> && cvsup -g -L 2 /etc/standard-supfile && make world again?]

Never run "make world" literally. Run make buildworld, make kernel, make 
installworld, mergemaster.

>
> Or is it possible that my GENERIC file is wrong?

Yes, you edited too much out. This is a FAQ:

> #device scbus   # SCSI bus (required for SCSI)
> device  umass   # Disks/Mass storage - Requires scbus and

HTH,

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

RE: kernel compile error

[Remko Lodder]

i did not mention that you needed to redownload the source
and that you recompile everything
you can just recompile the kernel, in the directories i mentioned
takes some time, but NOT that many time :)

Cheers :)

--

Kind regards,

Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl Dutch community for helping newcomers on the
hackerscene

mrtg.grunn.org Dutch mirror of MRTG

-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Verzonden: zondag 29 februari 2004 2:16
Aan: Remko Lodder
CC: [EMAIL PROTECTED]
Onderwerp: RE: kernel compile error


the only problem though with doing it all again is it takes so many hours!!
especialy downloading and make world

is there something i should do before the process to make a backup before
starting?  so instead of downloading from the

should i tar the whole /usr/src?

what do you think about this?

TIA



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

RE: kernel compile error

[rfa]

the only problem though with doing it all again is it takes so many hours!!
especialy downloading and make world

is there something i should do before the process to make a backup before
starting?  so instead of downloading from the

should i tar the whole /usr/src?

what do you think about this?

TIA


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

RE: kernel compile error

[Remko Lodder]

Hi dude,

It's not harmfull to replay the whole process,
The way i do it is go to the dir

cd /usr/src/sys/i386/conf/
edit the GENERIC file,
cd ../compile/GENERIC
make clean && make depend && make && make install
the && makes sure the next command only get's runned when
the previous command complete succesfully or returned status 0 (success in
almost every case :))
Perhaps it gives a better output then,

I am too tired to spit in your error at this time, so if no one replied
tomorrow, i will
have a look at it, and give it a toss.

Cheers :)

--

Kind regards,

Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl Dutch community for helping newcomers on the
hackerscene

mrtg.grunn.org Dutch mirror of MRTG

-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
Verzonden: zondag 29 februari 2004 1:53
Aan: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Onderwerp: kernel compile error


Im kinda new at this and

I was compiling my kernel on my Dell Inspiron600m running FreeBSD 5.2
RELEASE when I just remembered[after taking a nap] that I did

#make buildkernel KERNCONF=GENERIC

and I forgot to edit the /usr/src/sys/i386/conf/GENERIC file before
running the process.

anyway, the #make buildkernel completed and i wanted to change the GENERIC
file so i went aroung and commented out all the stuff that i didnt have on
my system and did a #make buildkernel KERNCONF=GENERIC again only to have
errors after about a minute into the process.

My Questions Are:
Is it wrong to do this process again after a successful #make buildkernel?
If so, what should I do to do it successfully? [should i rm -rf /usr/src
&& cvsup -g -L 2 /etc/standard-supfile && make world again?]

Or is it possible that my GENERIC file is wrong?

Here is the GENERIC file[The error output will follow]:

machine i386
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
ident   GENERIC

# To statically compile in device wiring instead of /boot/device.hints
#hints  "GENERIC.hints" # Default places to look for
devices.

makeoptions DEBUG=-g# Build kernel with gdb(1) debug
symbols

options SCHED_ULE   # ULE scheduler
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big
directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT   # Network Filesystem Client
options NFSSERVER   # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires
NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem (requires
PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options COMPAT_43   # Compatible with BSD 4.3 [KEEP
THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options SCSI_DELAY=15000# Delay (in ms) before probing SCSI
options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~215k to driver.
options PFIL_HOOKS  # pfil(9) framework

# Debugging for use in -current
options DDB # Enable the kernel debugger
options INVARIANTS  # Enable calls of extra sanity
checking
options INVARIANT_SUPPORT   # Extra sanity checks of internal
structures, required by INVARIANTS
options WITNESS # Enable checks to detect
deadlocks and cycles
options WITNESS_SKIPSPIN# Don't run witness on spinlocks
for speed

# To make an SMP kernel, the next two are needed
#optionsSMP # Symmetric MultiProcessor Kernel
device  apic# I/O APIC

device  isa
#device eisa
device 

kernel compile error

[rfa]

Im kinda new at this and

I was compiling my kernel on my Dell Inspiron600m running FreeBSD 5.2
RELEASE when I just remembered[after taking a nap] that I did

#make buildkernel KERNCONF=GENERIC

and I forgot to edit the /usr/src/sys/i386/conf/GENERIC file before
running the process.

anyway, the #make buildkernel completed and i wanted to change the GENERIC
file so i went aroung and commented out all the stuff that i didnt have on
my system and did a #make buildkernel KERNCONF=GENERIC again only to have
errors after about a minute into the process.

My Questions Are:
Is it wrong to do this process again after a successful #make buildkernel?
If so, what should I do to do it successfully? [should i rm -rf /usr/src
&& cvsup -g -L 2 /etc/standard-supfile && make world again?]

Or is it possible that my GENERIC file is wrong?

Here is the GENERIC file[The error output will follow]:

machine i386
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
ident   GENERIC

# To statically compile in device wiring instead of /boot/device.hints
#hints  "GENERIC.hints" # Default places to look for devices.

makeoptions DEBUG=-g# Build kernel with gdb(1) debug
symbols

options SCHED_ULE   # ULE scheduler
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big
directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT   # Network Filesystem Client
options NFSSERVER   # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem (requires
PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options COMPAT_43   # Compatible with BSD 4.3 [KEEP
THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options SCSI_DELAY=15000# Delay (in ms) before probing SCSI
options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~215k to driver.
options PFIL_HOOKS  # pfil(9) framework

# Debugging for use in -current
options DDB # Enable the kernel debugger
options INVARIANTS  # Enable calls of extra sanity
checking
options INVARIANT_SUPPORT   # Extra sanity checks of internal
structures, required by INVARIANTS
options WITNESS # Enable checks to detect
deadlocks and cycles
options WITNESS_SKIPSPIN# Don't run witness on spinlocks
for speed

# To make an SMP kernel, the next two are needed
#optionsSMP # Symmetric MultiProcessor Kernel
device  apic# I/O APIC

device  isa
#device eisa
device  pci

# Floppy drives
#device fdc

# ATA and ATAPI devices
device  ata
device  atadisk # ATA disk drives
#device ataraid # ATA RAID drives
device  atapicd # ATAPI CDROM drives
#device atapifd # ATAPI floppy drives
#device atapist # ATAPI tape drives
options ATA_STATIC_ID   # Static device numbering

# SCSI Controllers
#device ahb # EISA AHA1742 family
#device ahc # AHA2940 and onboard AIC7xxx devices
#device ahd # AHA39320/29320 and onboard AIC79xx devices
#device amd # AMD 53C974 (Tekram DC-390(T))
#device isp # Qlogic family
device  mpt # LSI-Logic MPT-Fusion
#device ncr # NCR/Symbios Logic
#device sym # NCR/Symbios Logic (newer chipsets +
those of `ncr')
#device trm # Tekram DC395U/UW/F DC315U adapters

#device adv # Advansys SC

Re: 5.1-CURRENT kernel compile error

[Doug White]

On Thu, 1 Jan 2004, Philip M. Gollucci wrote:

> vegeta# cd /usr/share/example/cvsup
> vegeta# cvsup -g -L2 standard-supfile

Did you check the standard-supfile before using it? You may have gotten
source that you didn't think you did. In general you should copy this to a
different location and edit it first to make sure you get the right thing.

> if_em.o: In function `em_process_receive_interrupts':
> if_em.o(.text+0x47f5): undefined reference to `vlan_tag_alloc'

I think you have the wrong source.  There is no vlan_tag_alloc in that
entire file, or in the entire kernel (if fxr.watson.org is to be
believed).  Check standard-supfile, delete your compile directory, and try
updating again.

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.1-CURRENT kernel compile error

[Ryan Sommers]

On Thu, 2004-01-01 at 22:43, Philip M. Gollucci wrote:
> vegeta# cd /usr/share/example/cvsup
> vegeta# cvsup -g -L2 standard-supfile
> vegeta# cd /usr/src/sys/i386/conf
> vegeta# config VEGETA
> vegeta# cd ../compile/VEGETA
> vegeta# make depend
> vegeta# make

I would recommend trying the "official" way of building the source
first. What did you CVSUP to? Current? Try doing the following build
order:

cd /usr/src
edit your config (sys/i386/conf/VEGETA)
make buildworld
make buildkernel
make installkernel
reboot in single user
make installworld
mergemaster
reboot



mergemaster

-- 
Ryan "leadZERO" Sommers
Gamer's Impact President
[EMAIL PROTECTED]
ICQ: 1019590
AIM/MSN: leadZERO

-= http://www.gamersimpact.com =-


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

5.1-CURRENT kernel compile error

[Philip M. Gollucci]

vegeta# cd /usr/share/example/cvsup
vegeta# cvsup -g -L2 standard-supfile
vegeta# cd /usr/src/sys/i386/conf
vegeta# config VEGETA
vegeta# cd ../compile/VEGETA
vegeta# make depend
vegeta# make
[lots of output snipped]
linking kernel
if_em.o: In function `em_process_receive_interrupts':
if_em.o(.text+0x47f5): undefined reference to `vlan_tag_alloc'
*** Error code 1
Note: the following Kernel Config file has worked for quite some time.
Also a yahoo/google and google group search returns 0 (ZERO) results on 
this.
That may be a first.

Thanks in advance

Philip

P.S.
 Please CC me so I'm sure to see the response.
Kernel Config for VEGETA:
###
## Architecture 
###
###
machine i386
maxusers256
cpu I686_CPU# aka Pentium Pro(tm)
ident   PHILIP

#options MATH_EMULATE#Support for x87 emulation

device  npx

###
# Compatibility 
###
###
options COMPAT_43
options COMPAT_FREEBSD4
options SCHED_4BSD

###
# Networking 
##
###
options INET#Internet communications protocols
options IPSEC   #IP security
options IPSEC_ESP   #IP security (crypto; define w/ IP

device  ether   #Generic Ethernet
device  loop#Network loopback device
device  miibus
device  fxp
device  em   ## ** ERROR IS RELATED TO THUIS 
#

###
## Firewalls 
##
###
options IPFIREWALL  #firewall
options IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity

options IPDIVERT#divert sockets
options IPFILTER#ipfilter support
options IPFILTER_LOG#ipfilter logging
options PFIL_HOOKS
options IPSTEALTH   #support for stealth forwarding
options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN
###
# FileSystems 
#
###
options FFS #Memory File System
options CD9660  #ISO 9660 filesystem
options PSEUDOFS
options PROCFS  #Process filesystem

options SOFTUPDATES
options UFS_DIRHASH
options QUOTA   #enable disk quotas
###
## ATA Devices 

###
device  isa
device  pci

device  ata
device  atadisk
device  ataraid # RAID
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
options ATA_STATIC_ID
###
### Misc Devices 
##
###
device  pty #Pseudo ttys
device  speaker #Play IBM BASIC-style noises out your 
speaker
device  md  #Memory/malloc disk
device  snp #Snoop device - to look at pty/vty/etc..

device  atkbdc
device  atkbd
device  psm
device  vga
device  agp
device  random
###
## Terminal Options 
###
###
device  sc
options MAXCONS=16  # number of virtual consoles

options SYSVSHM #SYSV-style shared memory
options SYSVMSG  

RESOLVED: kernel compile error: unknown option "USER_LDT"

[Barry Hawkins]

On Friday, Sep 19, 2003, at 17:04 US/Eastern, Barry C.Hawkins wrote:

List,
	I am trying to build a kernel using a copy of GENERIC for RELENG_5_1. 
 I have CVSuped by source tree prior to copying /usr/src/conf/GENERIC. 
 I initially disabled the all RAID devices, so I started with a fresh 
copy of GENERIC.  That was recommended once in the list archives for 
what seemed a similar scenario.  However the error message persists.  
Here are my extra lines at the bottom of my kernel config file, in all 
other ways it is an unmodified copy of GENERIC:

# Added for sound and Java
device  pcm # enable SoundBlaster PCI support
options USER_LDT# used by Java and nVidia
options CPU_ENABLE_SSE  # used by DVD
	When I run the following as root:

/usr/sbin/config GENERIC_SND

I receive the following message:

GENERIC_SND: unknown option "USER_LDT"

	The kernel config file resides in ~/kernels/, and I have a symlink in 
/usr/src/conf bearing the name GENERIC_SND.  This is a Dell OptiPlex 
200 with a PIII 733 MHz and 256MB RAM.  Any ideas?  The pupil sits, 
awaiting enlightenment...

Regards,
--
Barry C. Hawkins
All Things Computed
site: www.allthingscomputed.com/
weblog: www.allthingscomputed.com/blog/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"



List,
	The pupil just saw the probable answer in another posting from the 
following link:



'options USER_LDT' is not needed anymore in 5.x - [casaveli, 07/19/2003]

Sorry to bother everyone about that.

Regards,
--
Barry C. Hawkins
All Things Computed
site: www.allthingscomputed.com/
weblog: www.allthingscomputed.com/blog/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

kernel compile error: unknown option "USER_LDT"

[Barry C . Hawkins]

List,
	I am trying to build a kernel using a copy of GENERIC for RELENG_5_1.  
I have CVSuped by source tree prior to copying /usr/src/conf/GENERIC.  
I initially disabled the all RAID devices, so I started with a fresh 
copy of GENERIC.  That was recommended once in the list archives for 
what seemed a similar scenario.  However the error message persists.  
Here are my extra lines at the bottom of my kernel config file, in all 
other ways it is an unmodified copy of GENERIC:

# Added for sound and Java
device  pcm # enable SoundBlaster PCI support
options USER_LDT# used by Java and nVidia
options CPU_ENABLE_SSE  # used by DVD
	When I run the following as root:

/usr/sbin/config GENERIC_SND

I receive the following message:

GENERIC_SND: unknown option "USER_LDT"

	The kernel config file resides in ~/kernels/, and I have a symlink in 
/usr/src/conf bearing the name GENERIC_SND.  This is a Dell OptiPlex 
200 with a PIII 733 MHz and 256MB RAM.  Any ideas?  The pupil sits, 
awaiting enlightenment...

Regards,
--
Barry C. Hawkins
All Things Computed
site: www.allthingscomputed.com/
weblog: www.allthingscomputed.com/blog/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Kernel Compile Error

[Kris Kennaway]

On Sat, Jul 26, 2003 at 12:53:34AM +0200, A. Gillissen wrote:
> Hi,
> 
> While I was builing a custom kernel the following error occured during the 
> "make depend" (FreeBSD 5.0 RELEASE):

Sounds like you don't have a consistent source tree.

Kris


pgp0.pgp
Description: PGP signature

Kernel Compile Error

[A. Gillissen]

Hi,

While I was builing a custom kernel the following error occured during the 
"make depend" (FreeBSD 5.0 RELEASE):

--
mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev 
-I@/../in
clude -I/usr/include /usr/src/sys/modules/aha/../../dev/aha/aha.c 
/usr/src/sys/modu
les/aha/../../dev/aha/aha_isa.c
===> aic7xxx
===> aic7xxx/aicasm
===> aic7xxx/ahc
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
( cd /usr/src/sys/modules/aic7xxx/ahc/../aicasm; make aicasm; )
cc -O -pipe -mcpu=pentiumpro -nostdinc -I/usr/include -I. 
-I/usr/src/sys/modules/aic
7xxx/aicasm/../../../dev/aic7xxx/aicasm -c 
/usr/src/sys/modules/aic7xxx/aicasm/..
/../../dev/aic7xxx/aicasm/aicasm.c
cc -O -pipe -mcpu=pentiumpro -nostdinc -I/usr/include -I. 
-I/usr/src/sys/modules/aic
7xxx/aicasm/../../../dev/aic7xxx/aicasm -c 
/usr/src/sys/modules/aic7xxx/aicasm/..
/../../dev/aic7xxx/aicasm/aicasm_symbol.c
/usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:52:19: fcntl.h: No such 
file or dire
ctory
/usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c: In function `symtable_open':
/usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:134: `O_CREAT' undeclared 
(first use
in this function)
/usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:134: (Each undeclared 
identifier is
reported only once
/usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:134: for each function it 
appears in
.)
/usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:134: `O_NONBLOCK' 
undeclared (first
use in this function)
/usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:134: `O_RDWR' undeclared 
(first use
in this function)
*** Error code 1

Stop in /usr/src/sys/modules/aic7xxx/aicasm.
*** Error code 1
Stop in /usr/src/sys/modules/aic7xxx/ahc.
*** Error code 1
Stop in /usr/src/sys/modules/aic7xxx.
*** Error code 1
Stop in /usr/src/sys/modules.
*** Error code 1
Stop in /usr/src/sys/i386/compile/MYKERNEL.
bsdbox#
--
This happens with any configuration file - even with the GENERIC kernel 
config.
I've tried to comment out several options / devices but nothing worked.
Does anybody know a solution to this problem?

Best Regards,
Alexander Gillissen
Tel: +49 ( 0 ) 214 / 20 29 239
Mobil: +49 ( 0 ) 179 / 73 25 616
e-mail: [EMAIL PROTECTED]
icq uin: 62304741
www: http://drdoo.mine.nu
gpg public key: http://drdoo.mine.nu/ag_public_key.gpg  

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

Re: Kernel compile error (from newbies)

[clayton rollins]

On Sat,  5 Jul 2003 Mihail <[EMAIL PROTECTED]> wrote:
Hi,

While building a custom kernel "make" failed with this error:

cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
-Wcast-qual  -fformat-extensions -std=c99  -nostdinc -I-  -I. -I../../.. 
-I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter 
-D_KERNEL -include opt_global.h -fno-common -falign-functions=4 
-march=pentium4 -mfpmath=sse -msse -msse2 -mno-align-long-strings 
-mpreferred-stack-boundary=2 -ffreestanding -Werror  ../../../dev/fb/vga.c
{standard input}: Assembler messages:
{standard input}:3833: Error: suffix or operands invalid for `movd'
{standard input}:4053: Error: suffix or operands invalid for `movd'
*** Error code 1

I did "make" from /usr/src/sys/i386/compile/MYKERNEL just as described on 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html
BTW, how to change the _default_ CFLAGS? I would want to remove 
-mcpu=pentiumpro  that is being appended (in case -mcpu=pentiumpro 
conflicts with my -march=pentium4 flag?)

I really can't figure why the kernel won't compile. (Other than the obvious 
reason.)
If you're using gcc 3.2, the -msse2 flag is known to cause this problem. 
Other than
that, what you propose sounds like the next thing to check.

I'll cc -questions, which is the proper list for tech. advice. Maybe someone 
there
will have a better answer for you.

You can alter /etc/make.conf to change the flags; I'm not sure how it picks 
up the
'automatic settings.' (Again, maybe someone at -questions will have a better 
answer.)

Peace,
Clayton
_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.  
http://join.msn.com/?page=features/virus

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

Kernel Compile Error

[Mike Grover]

I am trying to compile a kernel under 4.8.
I copied GENERIC to STANDISH in the /usr/src/sys/i386/conf dir

when I run "make buildkernel KERNCONF=STANDISH" I get the following
error?

linking kernel
/usr/libexec/elf/ld: BFD 2.12.1 [FreeBSD] 2002-07-20 assertion fail
/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf32-i386.c:2255

*** Signal 10

Stop in /usr/obj/usr/src/sys/STANDISH.
*** Error code 1

Stop in /usr/src.
*** Error code 1


Any Ideas?

  mike

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