Re: `sched_clock' changed from 144 in sched_4bsd.o to 258 in sched_ule.o

2009-06-15 Thread Mel Flynn
On Friday 12 June 2009 10:26:26 Neil Short wrote:
 --- On Fri, 6/12/09, Mel Flynn 
mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:
  From: Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net
  Subject: Re: `sched_clock' changed from 144 in sched_4bsd.o to 258 in
  sched_ule.o To: freebsd-questions@freebsd.org
  Cc: Neil Short nesh...@yahoo.com
  Date: Friday, June 12, 2009, 9:21 AM
  On Friday 12 June 2009 06:44:50 Neil
 
  Short wrote:
   I'm taking a crack at the port win4bsd. The port
 
  informs me that I need to
 
   add options SCHED_4BSD
   to my kernel.
 
  It's an either/or thing. Remove SCHED_ULE.
  --
  Mel

 I was starting to suspect as much after having found the related man pages.
 Do you know if sched_4bsd is required for the port win4bsd? It's definitely
 required for the port install; but I wonder if I can change it back
 afterwards.

I have no idea. I tried it once, didn't work as advertised and moved on. So if 
you're serious about taking maintainership of this port, you have your work 
cut out for you and it's probably best to get a good working relationship with 
the developers of the software.
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


`sched_clock' changed from 144 in sched_4bsd.o to 258 in sched_ule.o

2009-06-12 Thread Neil Short

I'm taking a crack at the port win4bsd. The port informs me that I need to add
options SCHED_4BSD
to my kernel. When I do and attempt buildkernel I get
errors in the build. Any quick answers?

I'm going to re-run it and try to get more details on the errors. Just thought 
there might be some pat answer out there.


-N
==
Wherever the corpse is, there the vultures will gather.
Matthew 24:28


  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: `sched_clock' changed from 144 in sched_4bsd.o to 258 in sched_ule.o

2009-06-12 Thread Mel Flynn
On Friday 12 June 2009 06:44:50 Neil Short wrote:
 I'm taking a crack at the port win4bsd. The port informs me that I need to
 add options SCHED_4BSD
 to my kernel.

It's an either/or thing. Remove SCHED_ULE. 
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


ld: Warning: size of symbol `sched_clock' changed from 144 in sched_4bsd.o to 258 in sched_ule.o

2009-06-12 Thread Neil Short

Here's more detail with context on my attempt to include

options SCHED_4BSD

in my kernel. Any ideas?



MAKE=make sh /usr/src/sys/conf/newvers.sh CARMEN
cc -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  
-I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include 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  vers.c
linking kernel
sched_ule.o(.text+0x670): In function `schedinit':
: multiple definition of `schedinit'
sched_4bsd.o(.text+0x1690): first defined here
ld: Warning: size of symbol `schedinit' changed from 84 in sched_4bsd.o to 50 
in sched_ule.o
sched_ule.o(.text+0x6b0): In function `sched_rr_interval':
: multiple definition of `sched_rr_interval'
sched_4bsd.o(.text+0xc0): first defined here
ld: Warning: size of symbol `sched_rr_interval' changed from 48 in sched_4bsd.o 
to 37 in sched_ule.o
sched_ule.o(.text+0x790): In function `sched_user_prio':
: multiple definition of `sched_user_prio'
sched_4bsd.o(.text+0x110): first defined here
ld: Warning: size of symbol `sched_user_prio' changed from 41 in sched_4bsd.o 
to 37 in sched_ule.o
sched_ule.o(.text+0x910): In function `sched_lend_user_prio':
: multiple definition of `sched_lend_user_prio'
sched_4bsd.o(.text+0x1e0): first defined here
sched_ule.o(.text+0x930): In function `sched_unlend_user_prio':
: multiple definition of `sched_unlend_user_prio'
sched_4bsd.o(.text+0x200): first defined here
sched_ule.o(.text+0x970): In function `sched_sleep':
: multiple definition of `sched_sleep'
sched_4bsd.o(.text+0x240): first defined here
ld: Warning: size of symbol `sched_sleep' changed from 35 in sched_4bsd.o to 22 
in sched_ule.o
sched_ule.o(.text+0x990): In function `sched_class':
: multiple definition of `sched_class'
sched_4bsd.o(.text+0xf0): first defined here
ld: Warning: size of symbol `sched_class' changed from 19 in sched_4bsd.o to 
150 in sched_ule.o
sched_ule.o(.text+0xa30): In function `sched_unbind':
: multiple definition of `sched_unbind'
sched_4bsd.o(.text+0x270): first defined here
ld: Warning: size of symbol `sched_unbind' changed from 17 in sched_4bsd.o to 
44 in sched_ule.o
sched_ule.o(.text+0xa60): In function `sched_is_bound':
: multiple definition of `sched_is_bound'
sched_4bsd.o(.text+0x290): first defined here
ld: Warning: size of symbol `sched_is_bound' changed from 18 in sched_4bsd.o to 
23 in sched_ule.o
sched_ule.o(.text+0xa80): In function `sched_load':
: multiple definition of `sched_load'
sched_4bsd.o(.text+0x2b0): first defined here
ld: Warning: size of symbol `sched_load' changed from 10 in sched_4bsd.o to 43 
in sched_ule.o
sched_ule.o(.text+0xab0): In function `sched_sizeof_proc':
: multiple definition of `sched_sizeof_proc'
sched_4bsd.o(.text+0x2c0): first defined here
sched_ule.o(.text+0xac0): In function `sched_sizeof_thread':
: multiple definition of `sched_sizeof_thread'
sched_4bsd.o(.text+0x2d0): first defined here
sched_ule.o(.text+0xad0): In function `sched_fork_exit':
: multiple definition of `sched_fork_exit'
sched_4bsd.o(.text+0x310): first defined here
ld: Warning: size of symbol `sched_fork_exit' changed from 31 in sched_4bsd.o 
to 47 in sched_ule.o
sched_ule.o(.text+0xb00): In function `runq_add':
: multiple definition of `runq_add'
sched_4bsd.o(.text+0x330): first defined here
sched_ule.o(.text+0xb90): In function `runq_add_pri':
: multiple definition of `runq_add_pri'
sched_4bsd.o(.text+0x3c0): first defined here
sched_ule.o(.text+0xdd0): In function `runq_check':
: multiple definition of `runq_check'
sched_4bsd.o(.text+0x450): first defined here
sched_ule.o(.text+0xdf0): In function `runq_choose':
: multiple definition of `runq_choose'
sched_4bsd.o(.text+0x4b0): first defined here
sched_ule.o(.data+0x0): multiple definition of `runq_fuzz'
sched_4bsd.o(.data+0x0): first defined here
sched_ule.o(.text+0xe90): In function `runq_choose_from':
: multiple definition of `runq_choose_from'
sched_4bsd.o(.text+0x550): first defined here
sched_ule.o(.text+0xf20): In function `sched_newproc':
: multiple definition of `sched_newproc'
sched_4bsd.o(.text+0x5e0): first defined here
sched_ule.o(.text+0x14c0): In function `sched_exit_thread':
: multiple definition of `sched_exit_thread'
sched_4bsd.o(.text+0x670): first defined here
ld: Warning: size of symbol `sched_exit_thread' changed from 310 in 
sched_4bsd.o to 157 in sched_ule.o
sched_ule.o(.text+0x1560): In function `sched_exit':
: multiple definition of `sched_exit'
sched_4bsd.o(.text+0x7b0): first defined here
sched_ule.o(.text+0x1580): In function `sched_newthread':
: multiple definition of `sched_newthread'
sched_4bsd.o(.text+0x7d0): first defined here

Re: ld: Warning: size of symbol `sched_clock' changed from 144 in sched_4bsd.o to 258 in sched_ule.o

2009-06-12 Thread Paul B. Mahol
On 6/12/09, Neil Short nesh...@yahoo.com wrote:

 Here's more detail with context on my attempt to include

 options SCHED_4BSD

 in my kernel. Any ideas?

You can't have two schedulers at same time in same kernel.
-- 
Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: `sched_clock' changed from 144 in sched_4bsd.o to 258 in sched_ule.o

2009-06-12 Thread Neil Short


--- On Fri, 6/12/09, Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net 
wrote:

 From: Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net
 Subject: Re: `sched_clock' changed from 144 in sched_4bsd.o to 258 in 
 sched_ule.o
 To: freebsd-questions@freebsd.org
 Cc: Neil Short nesh...@yahoo.com
 Date: Friday, June 12, 2009, 9:21 AM
 On Friday 12 June 2009 06:44:50 Neil
 Short wrote:
  I'm taking a crack at the port win4bsd. The port
 informs me that I need to
  add options SCHED_4BSD
  to my kernel.
 
 It's an either/or thing. Remove SCHED_ULE. 
 -- 
 Mel
 

I was starting to suspect as much after having found the related man pages. Do 
you know if sched_4bsd is required for the port win4bsd? It's definitely 
required for the port install; but I wonder if I can change it back afterwards.


  
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org