pthread and write()

2001-06-08 Thread Idea Receiver



I dont know if this is cause by -current, I have not yet try on the
-stable. However, I just write here, maybe someone can help me.. :P

recently, I wrote a multithread network server for my work. what it does
is to accept TCP connection from remote, and then put it into a new
thread. I have wrote a simulation client to test this application i
wrote. The simulation client will keep opening multi connection to the
server, and keep sent a 8byte structure to server using loop and
sleep(1) in between each write(). Also each of the thread created by
server will simply reply a 8byte structure to its client (using
write() again).

When the client bring up enough (between 300-1000) connection to
the server, then the server will core dump around 30mis to 1hr time.
After I trace the problem, I found it is cause by write() with signal
11. then i use gdb to trace out the problem. follow is what i get from
gdb:
 
   Program received signal SIGSEGV, Segmentation fault.
   0x28121637 in _fd_lock_backout () from /usr/lib/libc_r.so.4

can anyone plz help with this problem? is there anything important I
missed?

thx!!
 





To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



pthread and write()

2001-06-08 Thread Idea Receiver


I dont know if this is cause by -current, I have not yet try on the
-stable. However, I just write here, maybe someone can help me.. :P

recently, I wrote a multithread network server for my work. what it does
is to accept TCP connection from remote, and then put it into a new
thread. I have wrote a simulation client to test this application i
wrote. The simulation client will keep opening multi connection to the
server, and keep sent a 8byte structure to server using loop and
sleep(1) in between each write(). Also each of the thread created by
server will simply reply a 8byte structure to its client (using
write() again).

When the client bring up enough (between 300-1000) connection to
the server, then the server will core dump around 30mis to 1hr time.
After I trace the problem, I found it is cause by write() with signal
11. then i use gdb to trace out the problem. follow is what i get from
gdb:
 
   Program received signal SIGSEGV, Segmentation fault.
   0x28121637 in _fd_lock_backout () from /usr/lib/libc_r.so.4

can anyone plz help with this problem? is there anything important I
missed?

thx!!
 





To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



pthread and write()

2001-06-08 Thread Idea Receiver



I dont know if this is cause by -current, I have not yet try on the
-stable. However, I just write here, maybe someone can help me.. :P

recently, I wrote a multithread network server for my work. what it does
is to accept TCP connection from remote, and then put it into a new
thread. I have wrote a simulation client to test this application i
wrote. The simulation client will keep opening multi connection to the
server, and keep sent a 8byte structure to server using loop and
sleep(1) in between each write(). Also each of the thread created by
server will simply reply a 8byte structure to its client (using
write() again).

When the client bring up enough (between 300-1000) connection to
the server, then the server will core dump around 30mis to 1hr time.
After I trace the problem, I found it is cause by write() with signal
11. then i use gdb to trace out the problem. follow is what i get from
gdb:
 
   Program received signal SIGSEGV, Segmentation fault.
   0x28121637 in _fd_lock_backout () from /usr/lib/libc_r.so.4

can anyone plz help with this problem? is there anything important I
missed?

thx!!
 




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



pthread and write()

2001-06-08 Thread Idea Receiver



I dont know if this is cause by -current, I have not yet try on the
-stable. However, I just write here, maybe someone can help me.. :P

recently, I wrote a multithread network server for my work. what it does
is to accept TCP connection from remote, and then put it into a new
thread. I have wrote a simulation client to test this application i
wrote. The simulation client will keep opening multi connection to the
server, and keep sent a 8byte structure to server using loop and
sleep(1) in between each write(). Also each of the thread created by
server will simply reply a 8byte structure to its client (using
write() again).

When the client bring up enough (between 300-1000) connection to
the server, then the server will core dump around 30mis to 1hr time.
After I trace the problem, I found it is cause by write() with signal
11. then i use gdb to trace out the problem. follow is what i get from
gdb:
 
   Program received signal SIGSEGV, Segmentation fault.
   0x28121637 in _fd_lock_backout () from /usr/lib/libc_r.so.4

can anyone plz help with this problem? is there anything important I
missed?

thx!!
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



pthread and write()

2001-06-08 Thread Idea Receiver


I dont know if this is cause by -current, I have not yet try on the
-stable. However, I just write here, maybe someone can help me.. :P

recently, I wrote a multithread network server for my work. what it does
is to accept TCP connection from remote, and then put it into a new
thread. I have wrote a simulation client to test this application i
wrote. The simulation client will keep opening multi connection to the
server, and keep sent a 8byte structure to server using loop and
sleep(1) in between each write(). Also each of the thread created by
server will simply reply a 8byte structure to its client (using
write() again).

When the client bring up enough (between 300-1000) connection to
the server, then the server will core dump around 30mis to 1hr time.
After I trace the problem, I found it is cause by write() with signal
11. then i use gdb to trace out the problem. follow is what i get from
gdb:
 
   Program received signal SIGSEGV, Segmentation fault.
   0x28121637 in _fd_lock_backout () from /usr/lib/libc_r.so.4

can anyone plz help with this problem? is there anything important I
missed?

thx!!
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: pthread and write()

2001-06-08 Thread Idea Receiver

 Program received signal SIGSEGV, Segmentation fault.
 0x28121637 in _fd_lock_backout () from /usr/lib/libc_r.so.4
 
 You're not running -current if you're using libc_r.so.4.
 We're at libc_r.so.5.  And fd locks have also been disabled
 in -current.
 

err~~ sorry about my stupid... i wasnt aware that i run it on the wrong
system

ok.. now i konw it is not working on the -stable :P .. ill give a try on
-current...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: about ppp..

2001-02-02 Thread Idea Receiver



On Fri, 2 Feb 2001, Julian Elischer wrote:

 Idea Receiver wrote:
  
  On Fri, 26 Jan 2001, Julian Elischer wrote:
   how 'current' are your systems?
   when did this behaviour start?
   (i.e. before or after the latest round of netgraph changes?)
  
  it is before new netgraph...
  i think the new netgraph cause the same problem as well..
 
 
 can you give more information on this problem?

i cant remember when the exact day the problem started.
i did a cvsup/make world recently, the problem is still exist.
btw, i am running PPPoE. but the problem also exists in simple
PPP (modem) connection as well.

btw, i have found, if I try to download something like 1G,
I havnt see any problem occer, the download speed is fairly constant.
however, the problem always happen when someone try to play on-line
game, or maybe try to receive/sent icq files, or reading web pages, or
even just doing  a dns request, then this lagging problem often happen.


the ppp.config is fairly stander shows as follow,
 set device PPPoE:rl0
 set mru 1454
 set mtu 1454
 set speed sync
 enable lqr
 set cd 4
 set authname xxx
 set authkey x
 set dial
 set login
 set redial 30






To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: about ppp..

2001-01-28 Thread Idea Receiver



On Fri, 26 Jan 2001, Julian Elischer wrote:
 how 'current' are your systems?
 when did this behaviour start?
 (i.e. before or after the latest round of netgraph changes?)

it is before new netgraph...
i think the new netgraph cause the same problem as well..



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



about ppp..

2001-01-25 Thread Idea Receiver


One of my current machines here are running PPPoE..
for some reason, it will some times become extramly lag of its PPPoE
connection. (for example, from 25ns ping time become 2500ns ping
time). And will back to normal in few mins..
However, i do not see the same problem on my 4.2 stable system.

is this a known problem or just me? plz help!

thx..



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



problem of load linux modules after new make world

2000-11-11 Thread Idea Receiver


my last working make world is about 2 weeks ago (i believe it is 28/10).
i receiver the following error msg after today's make world:

  link_elf: symbol makebdev undefined
  pid 221 (ldconfig), uid 0: exited on signal 11 (core dumped)

I think i read some thing about this from the mailing list not long ago..
however i can hardly remember anything or any solutions of fixing this
problem. Can someone plz help me with this!

thx!



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: strange problem of PPPoE + NAT

2000-10-25 Thread Idea Receiver


thx. that fix my problem ;)

the other problem i had after switch that system to -current
is that after a random time, the connection will frzzed.
the routing table still exist, connection is still up.
just cant connect to anywhere outside the network. no error
or anything been loged in ppp.log. the connection just simply
freezed. the only way to bring the connection back is to reboot
the system. (i try to just bring down the interface and bring
back up. but it seems doesnt help), otherwise it will give
an error of unable to connect to device..

at the moment, everytime i run ppp, follow error will appear

 module_register: module netgraph already exists!
 linker_file_sysinit "netgraph.ko" failed to register! 17

but i believe this has nothing to do with the problem connection
freezed.

plz help!


On Sat, 21 Oct 2000, Josh Tiefenbach wrote:

 On Sat, Oct 21, 2000 at 11:08:28PM +1000, Idea Receiver wrote:
  
  I just upgrade one of my server to -current. that server connect to ADSL
  and act as a gateway.
  
  however, after I upgrade that server to -current, all other clients
  (all windows 98) start acting really strange. clients was unable to 
  connect to more then 60% of web sites. for example, clients can not 
 
 Sounds like a PMTU-D problem. Either change the MTU of the machines behind the
 gateway to something like 1440, or try /usr/ports/net/tcpmssd.
 
 josh
 
 -- 
 "Watching those 2 guys [Bush and Gore] debate is like watching Ben Stein read
 'The Story of O'" -- Dennis Miller
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: strange problem of PPPoE + NAT

2000-10-25 Thread Idea Receiver



On Wed, 25 Oct 2000, Josh Tiefenbach wrote:
 Interestingly enough, I've been having the same problem with PPPoE ever since
 it hit the tree 'bout a year ago. It happens infrequently enough that I tend
 to blame my provider, rather than ppp.
 
 When it happens, killing ppp and restarting it is usually enough. 
 
 I have no idea what causes it.
 

kill ppp and restart it doesnt help at all.
will it make any different if i change a network card?
it happen so frequently, it is impossible to run a stable
server with PPPoE!


   module_register: module netgraph already exists!
   linker_file_sysinit "netgraph.ko" failed to register! 17
 
 Just a guess, but thats probably because you're trying to kldload netgraph.ko,
 but have already compiled it into your kernel with options NETGRAPH

nope. i didnt kldload netgraph.ko at all.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fail to compile kernel...

2000-08-14 Thread Idea Receiver



On Sun, 13 Aug 2000, Warner Losh wrote:

 In message [EMAIL PROTECTED] Idea 
Receiver writes:
 :  In message [EMAIL PROTECTED] 
Idea Receiver writes:
 :  : i have try to upgrade one of my 4.1 release to -current.
 :  : however, when i try to build the kernel, it failed as following 
 :  : message.
 :  
 :  Upgrade your sources and try again.
 :  
 :  Warner
 : 
 : cvsed this morning (8 hrs ago..)
 : and still doesnt work..
 
 Where did you get your sources?  As of 12:00 last night, the sources I 
 grabbed from cvsup8 completed both a make buildworld and make
 buildkernel in a fresh tree.
 

i got my sources from cvsup5..
i change it to cvsup2 this morning. now everything works fine.

thank you.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fail to compile kernel...

2000-08-13 Thread Idea Receiver



On Sat, 12 Aug 2000, Warner Losh wrote:

 In message [EMAIL PROTECTED] Idea 
Receiver writes:
 : i have try to upgrade one of my 4.1 release to -current.
 : however, when i try to build the kernel, it failed as following 
 : message.
 
 Upgrade your sources and try again.
 
 Warner

cvsed this morning (8 hrs ago..)
and still doesnt work..



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



fail to compile kernel...

2000-08-12 Thread Idea Receiver


i have try to upgrade one of my 4.1 release to -current.
however, when i try to build the kernel, it failed as following 
message.

please help! thanks in advance

=== oldcard
cc -O -pipe  -D_KERNEL -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual  -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-  -I. -I@
-I@/../include  -mpreferred-stack-boundary=2 -c
/mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pccard.c
cc -O -pipe  -D_KERNEL -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual  -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I-  -I. -I@
-I@/../include  -mpreferred-stack-boundary=2 -c
/mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c
/mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020:
`card_get_memory_offset_desc' undeclared here (not in a function)
/mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020:
initializer element is not constant
/mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020:
(near initialization for `pcic_methods[16].desc')
*** Error code 1

Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard.
*** Error code 1

Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules.
*** Error code 1

Stop in /usr/obj/mnt/ad4s1e/FreeBSD-CURRENT/src/sys/WHITESUN-LWY-00.
*** Error code 1

Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src.
*** Error code 1

Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Problems with PCM and ESS 1868

2000-06-11 Thread Idea Receiver


my SBLive just wont play any mp3.
it just simplye stop immediantly. It was ok before my recent make world.


On Sun, 11 Jun 2000, Donn Miller wrote:

 The recent commits to PCM, as of a few days back, have given me
 problems with my ESS 1868.  When I play MP3's with mpg123, I get a lot
 of loud pops and clicks during playback.  Otherwise, the MP3s DO play
 all the way through.  However, when I try to play MP3s with Real
 Player 7, it just hangs at the beginning, and doesn't play the MP3. 
 Before the commits to PCM, I was able to play MP3s OK with Real Player
 7.
  
 - Donn
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Old-style KLD file linuxelf found?

2000-05-02 Thread Idea Receiver


My mail server was down for pass few days. Hope I didnt miss anything 
important!

Today, I try to make world and then rebuild the kernel.
After I restart the machine, it shows "Old-style KLD file linuxelf found"
and "Old-style KLD file linuxaout found" and then core dumped.

I tried to brandelf. but same message appear...

Please help me!
I believe I miss out something really important in pass few days

thx



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Old-style KLD file linuxelf found?

2000-05-02 Thread Idea Receiver



On Tue, 2 May 2000, Donn Miller wrote:

 Donn Miller wrote:
  
  Idea Receiver wrote:
  
   My mail server was down for pass few days. Hope I didnt miss anything
   important!
  
   Today, I try to make world and then rebuild the kernel.
   After I restart the machine, it shows "Old-style KLD file linuxelf found"
   and "Old-style KLD file linuxaout found" and then core dumped.
  
  What you need to do is/
  
  brandelf -t Linux compat/linux/sbin/ldconfig
  
  and then reboot.
 
 Actually, I meant brandelf -t Linux /compat/linux/sbin/ldconfig.
 

as i said before. i did try to brandelf it. doesnt work.

anyway. i think maybe due to the modules not sync? but how can this
happen?



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



-current crash while mouting cd..

2000-03-22 Thread Idea Receiver


cvsup to 6 hours ago.


Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id = 0100
fault virtual address   = 0x0
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc021ad98
stack pointer   = 0x10:0xc87d0d88
frame pointer   = 0x10:0xc87d0d94
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 238 (mount_cd9660)
interrupt mask  = none - SMP: XXX
trap number = 12
panic: page fault
mp_lock = 0102; cpuid = 1; lapic.id = 0100
boot() called on cpu#1



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: install problem with 4.0 (spec_getpages)

2000-03-19 Thread Idea Receiver



On Sun, 19 Mar 2000, Thierry.herbelot wrote:

 Marc van Kempen wrote:
  
  Hi,
  
  While trying to boot from the 4.0 installation disks,
  I get the following error after the devices have been probed:
  
 
 [SNIP]
 
  root@localhost:/usr/src/sys/compile/SCHOPENHAUER
  Timecounter "i8254"  frequency 1193182 Hz
  CPU: Celeron (412.50-MHz 686-class CPU)
 
 412 MHz is a non-conventional speed for a Celly : if you are
 overclocking (I'm doing it, too), does the bug repeats itself when at
 the normal speed ?

yes it does.
anyway.. problem fixed this afternoon (australia time :P)!



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: install problem with 4.0 (spec_getpages)

2000-03-19 Thread Idea Receiver



On Sun, 19 Mar 2000, Marc van Kempen wrote:

 On Mon, Mar 20, 2000 at 01:55:11AM +1000, Idea Receiver wrote:
  
  
  On Sun, 19 Mar 2000, Thierry.herbelot wrote:
  
   Marc van Kempen wrote:

Hi,

While trying to boot from the 4.0 installation disks,
I get the following error after the devices have been probed:

   
   [SNIP]
   
root@localhost:/usr/src/sys/compile/SCHOPENHAUER
Timecounter "i8254"  frequency 1193182 Hz
CPU: Celeron (412.50-MHz 686-class CPU)
   
   412 MHz is a non-conventional speed for a Celly : if you are
   overclocking (I'm doing it, too), does the bug repeats itself when at
   the normal speed ?
  
  yes it does.
  anyway.. problem fixed this afternoon (australia time :P)!

oops.. sorry.. I try to reply a different mail in a different group with
a totally different topic and nothing to do with FreeBSD at all...
I dont know what my finger do.. I was think other thing and accidently
replied this mail... :^P



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



about XFree86-4

2000-03-19 Thread Idea Receiver


I take a look at the XFree86-4 patches.
I found in those patches, "zh_TW.big5" and "zh_CN.big5" maybe wrong.

the "zh_TW.big5" should be "zh_TW.BIG5"
and the "zh_CN.big5" should be "zhTW.BIG5"

hopefuly I am right about this..



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: port/XFree86-4 make install fail.

2000-03-18 Thread Idea Receiver



Finally! IT WORKS!

:-)



On Sun, 19 Mar 2000, ANAZAWA Akio wrote:

 Hi,
 
  In [EMAIL PROTECTED] 
  at Thu, 16 Mar 2000 14:41:53 +1000 (EST),
  Idea Receiver [EMAIL PROTECTED] wrote:
 
 
 IR "make all" success without any problem.
 IR however, make install fail ;(
 
 IR following are the error msg.
 
 IR anyway I can fix this problem?
 
 IR thx~
 
 This morning, I've encountered same problem. 
 (FreeBSD 5.0-CURRENT + XFree86 4.0)
 
 Probability, you can get around the problem with this patch.
 (Note that you are required "make World" again)
 
 bash$ diff -U2 FreeBSD.cf.orig FreeBSD.cf
 --- FreeBSD.cf.orig   Fri Feb 18 02:19:43 2000
 +++ FreeBSD.cfSun Mar 19 00:27:11 2000
 @@ -464,6 +464,7 @@
   * A hack to work around an optimisation problem with the compiler on
   * FreeBSD 4.0-current in late 1999/early 2000.
 + * (and FreeBSD 5.0-current in early 2000)
   */
 -#if OSMajorVersion == 4  OSMinorVersion == 0  OSTeenyVersion == 0
 +#if (OSMajorVersion == 4 || OSMajorVersion == 5)  OSMinorVersion == 0  
OSTeenyVersion == 0
  #define FreeBSDGccOptBug
  #endif
 
 
 Regards,
 Akio Anazawa
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: port/XFree86-4 make install fail.

2000-03-17 Thread Idea Receiver



On Sat, 18 Mar 2000, Matthew Thyer wrote:

 I had no problem.
 
 I tend to uninstall anything that uses X, build  install new X and
 then build new apps.  It doesnt take that long.  This is all using
 ports with CFLAG= -O -pipe

ok.. I just tried to reinstall the whole system with the SNAP from 8/Feb
and cvs up to the latest, and make world. and make a new kernel with SMP
support.
and then I tried to make XFree-4 again. Same problem.

What can I do? I dont want to make -k install. I need a full functional
X. :(



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: port/XFree86-4 make install fail.

2000-03-17 Thread Idea Receiver



tried. same problem.
what else I can do?

btw, is there any different between binary version and make from port?



On Sat, 18 Mar 2000, Jean-Marc Zucconi wrote:

  Idea Receiver writes:
 
   ok.. I just tried to reinstall the whole system with the SNAP from 8/Feb
   and cvs up to the latest, and make world. and make a new kernel with SMP
   support.
   and then I tried to make XFree-4 again. Same problem.
 
   What can I do? I dont want to make -k install. I need a full functional
   X. :(
 
 
 Try the following patch. It was necessary for XFree86-3.9.17
 
 --- programs/Xserver/Xext/Imakefile~  Sun Jan  2 03:09:36 2000
 +++ programs/Xserver/Xext/Imakefile   Sun Jan  2 21:42:40 2000
 @@ -133,3 +133,4 @@
  
  InstallDriverSDKNonExecFile(dgaproc.h,$(DRIVERSDKINCLUDEDIR))
  InstallDriverSDKNonExecFile(xvdix.h,$(DRIVERSDKINCLUDEDIR))
 +CDEBUGFLAGS=
 
 -- 
  Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED]
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: port/XFree86-4 make install fail.

2000-03-16 Thread Idea Receiver


On Thu, 16 Mar 2000, Jean-Marc Zucconi wrote:

  Idea Receiver writes:
 
   "make all" success without any problem.
 
 There was an error but "make all"  always complete.
 
   however, make install fail ;(
 
 What are your CFLAGS in /etc/make.conf ?

default only. CFLAG= -O -pipe

I have no problem of installing XFree-4.0 binary. Just not from
ports/x11/XFree-4 :(



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



make world fail!

2000-03-15 Thread Idea Receiver


just cvsup up 3 hrs ago.
try to make world, following error been given..

 

cc -O -pipe
-I/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/../../common
 -I/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/../btx/lib
-I/mnt/ad5s
1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT=0x3f8
-DCOMS
PEED=9600 -DTERM_EMU
-I/usr/obj/mnt/ad5s1e/FreeBSD-CURRENT/src/i386/usr/include
-c /mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/vidconsole.c -o
vidcons
ole.o
/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c: At top
level:
/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:301:
syntax err
or before `}'
/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:103:
warning: `
bd_printslice' used but never defined
/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:106:
warning: `
bd_strategy' used but never defined
/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:108:
warning: `
bd_open' used but never defined
/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:109:
warning: `
bd_close'
 used but never defined
/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:123:
warning: `
bd_opendisk' used but never defined
/mnt/ad5s1e/FreeBSD-CURRENT/src/sys/boot/i386/libi386/biosdisk.c:124:
warning: `
bd_closedisk' used but never defined
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



port/XFree86-4 make install fail.

2000-03-15 Thread Idea Receiver



"make all" success without any problem.
however, make install fail ;(

following are the error msg.

anyway I can fix this problem?

thx~

##
xf86vmode.c: In function `ProcXF86VidModeGetMonitor':
xf86vmode.c:1320: Unable to generate reloads for:
(insn 298 296 300 (parallel[
(set (reg:SI 0 %eax)
(fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -34 [0xffde])) 0))
(clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
(const_int -36 [0xffdc])) 0))
(clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
(const_int -40 [0xffd8])) 0))
(clobber (scratch:HI))
] ) 145 {fix_truncsfsi2+1} (insn_list 291 (nil))
(expr_list:REG_DEAD (reg:SI 0 %eax)
(expr_list:REG_UNUSED (scratch:HI)
(nil
*** Error code 1
Stop in
/mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc/programs/Xserver
/Xext.
*** Error code 1
Stop in
/mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc/programs/Xserver
.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc/programs.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4/work/xc.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4.
*** Error code 1
Stop in /mnt/ad5s1e/FreeBSD-CURRENT/ports/x11/XFree86-4.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: port/XFree86-4 make install fail.

2000-03-15 Thread Idea Receiver



On Wed, 15 Mar 2000, Donn Miller wrote:

 Idea Receiver wrote:
  
  "make all" success without any problem.
  however, make install fail ;(
  
  following are the error msg.
 
 [snip]
 
  xf86vmode.c: In function `ProcXF86VidModeGetMonitor':
  xf86vmode.c:1320: Unable to generate reloads for:
  (insn 298 296 300 (parallel[
  (set (reg:SI 0 %eax)
  (fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0
  (clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
  (const_int -34 [0xffde])) 0))
  (clobber (mem:HI (plus:SI (reg:SI 6 %ebp)
  (const_int -36 [0xffdc])) 0))
  (clobber (mem:SI (plus:SI (reg:SI 6 %ebp)
  (const_int -40 [0xffd8])) 0))
 
 This sounds like a problem with older 4.0-currents.  Did you make
 world and your kernel recently?

That is what i though before! so I just cvsup up to this morning,
and try to make install again. same problem.




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



some error got from make release this afternoon..

2000-03-12 Thread Idea Receiver



Just some error I got when I try to make release this afternoon.
(cvs up to the latest). Maybe it is worthful to anyone making 
release all the time :_) 


##

a - textlist.o
a - parsetag.o
ranlib libindep.a
cc -O -pipe  -I/usr/local/include -I. -o mktable mktable.o hash.o
-L/usr/local/lib -L. -lindep -lgc -lm  -lncurses
./mktable 100 tagtable.tab  tagtable.c
cc -O -pipe  -I/usr/local/include -I. -c tagtable.c
tagtable.c:8: syntax error before character 0340
tagtable.c:11: syntax error before character 0320
tagtable.c:11: warning: initialization makes integer from pointer without
a cast
tagtable.c:17: syntax error before character 0370
tagtable.c:17: warning: initialization makes integer from pointer without
a cast
tagtable.c:22: syntax error before character 0220
tagtable.c:22: warning: initialization makes integer from pointer without
a cast
tagtable.c:24: `tfoot' undeclared here (not in a function)
tagtable.c:24: syntax error before `x'
tagtable.c:24: warning: initialization makes integer from pointer without
a cast
tagtable.c:30: `HTML_N_COLGcolgroup' undeclared here (not in a function)
tagtable.c:30: initializer element is not constant
tagtable.c:30: (near initialization for `MyHashItem[25].value')
tagtable.c:41: syntax error before `,'
tagtable.c:41: warning: initialization makes integer from pointer without
a cast
tagtable.c:45: syntax error before character 07
tagtable.c:45: warning: initialization makes integer from pointer without
a cast
tagtable.c:49: syntax error before character 0200
tagtable.c:49: warning: initialization makes integer from pointer without
a cast
tagtable.c:55: syntax error before character 07
tagtable.c:56: `HTML_E' undeclared here (not in a function)
tagtable.c:56: `tbody' undeclared here (not in a function)
tagtable.c:56: syntax error before `HTML_N'
tagtable.c:56: warning: initialization makes integer from pointer without
a cast
tagtable.c:57: syntax error before character 07
tagtable.c:57: warning: initialization makes integer from pointer without
a cast
tagtable.c:69: `Hthead' undeclared here (not in a function)
tagtable.c:69: initializer element is not constant
tagtable.c:69: (near initialization for `MyHashItem[64].value')
tagtable.c:91: syntax error before character 07
tagtable.c:94: syntax error before character 07
tagtable.c:94: warning: initialization makes integer from pointer without
a cast
tagtable.c:105: syntax error before character 0270
tagtable.c:106: syntax error before `w'
tagtable.c:112: syntax error before character 07
tagtable.c:112: warning: initialization makes integer from pointer without
a cast
tagtable.c:118: syntax error before character 0250
tagtable.c:118: warning: initialization makes integer from pointer without
a cast
*** Error code 1 

Stop in /usr/ports/www/w3m/work/w3m.
*** Error code 1

Stop in /usr/ports/www/w3m/work/w3m.
*** Error code 1

Stop in /usr/ports/www/w3m.
*** Error code 1

Stop in /usr/ports/www/w3m.
*** Error code 1

Stop in /usr/ports/www/w3m.
*** Error code 1

Stop in /usr/ports/www/w3m.
*** Error code 1

Stop in /usr/ports/textproc/docproj.
*** Error code 1

Stop in /usr/ports/textproc/docproj.
*** Error code 1

Stop in /usr/ports/textproc/docproj.
*** Error code 1

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

Stop in /mnt/ad5s1e/FreeBSD-CURRENT/src/release. 






To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



more question about make release

2000-03-08 Thread Idea Receiver


hi,

Finallly I got make release work :^) thx to everyone who helping me about.

After make release, I believe nothing about X has been add into. I am just
woundring about how do I make a release which is just the same as those
SNAP released on the net? So I can use it to burn a CD, and use it to
install on a system with no NIC.


thanks in advance...



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 3.4 - 4.0 upgrade problems

2000-03-07 Thread Idea Receiver


On Tue, 7 Mar 2000, Kris Kennaway wrote:

 Okay, I did some testing on my new scratch box by first installing 3.4
 from the CD and then attempting a source upgrade to 4.0: buildworld
 completed fine, but following the directions in UPDATING was not enough to
 get the kernel built.
 
 1) genassym and config were complaining about not being able to find
 libc.so.4 when I installed them. Workaround: go back and rebuild with with
 CFLAGS="-static"

what i did is just go to genassym directory, do "make clean depend all
install". it will then fix the problem.

 
 2) When trying to build a GENERIC kernel, the build died with:
 
 Solution: 'make buildkernel' in /usr/src seemed to do the trick.

i was try to rebuild "config" and it will also fix the problem.
jus do "make clean depend all install" :-)


I dont know if "my solution" going to cause any problem, but it simply
sovle both GENERIC kernel and genassym problem.

btw, I have problem to make release, it kept complain about that i didnt
set the USA_RESIDENT, however, I did! both in /etc and /etc/defaults. Can 
please someone help me out with this as well..

thanks :)



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 3.4 - 4.0 upgrade problems

2000-03-07 Thread Idea Receiver



On Tue, 7 Mar 2000 [EMAIL PROTECTED] wrote:

 oN tUE, mAR 07, 2000 AT 05:05:40PM +0200, Ruslan Ermilov wrote:
  On Wed, Mar 08, 2000 at 01:02:29AM +1000, Idea Receiver wrote:
  [...]
   btw, I have problem to make release, it kept complain about that i didnt
   set the USA_RESIDENT, however, I did! both in /etc and /etc/defaults. Can 
   please someone help me out with this as well..
   
   thanks :)
  
  Set USA_RESIDENT in environment rather than in /etc.
 
 Or just put USA_RESIDENT=YES in /etc/make.conf

This is what i did before I come to the mailing-list and ask for help :)

anyway, set the USA_RESIDENT in environment helps :)



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message