Re: Linux ABI no longer supports staroffice
"Yevmenkin, Maksim N, CSCIO" wrote: > [snip] > > same here :( i got original Sun CD with StartOffice 5.1a and tried to > install it. it failed. i used > > # make WITH_CDROM=yes USE_CDROM=yes install > > and everything was fine, but then i got exactly the same error. > XFree86-3.3.6 and XFree86-contrib-3.3.6 both working just fine. > ``xhost +'' did not resolve the problem. Should be fixed already. Please re-cvsup. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Linux ABI no longer supports staroffice
> Up until this weekend, I was able to use the staroffice52 port with > little problem (I had installed it earlier without benefit of the port > and it worked fine.) I did a 5.0-current kernel rebuild on > Thursday with > sources current on that day and things were fine. When I rebuilt my > kernel yesterday afternoon with sources from Saturday > morning, the port > stopped working. I get the following error messages > > I18N: X Window System doesn't support locale "C" > _X11TransSocketOpen: socket() failed for local > _X11TransSocketOpenCOTSClient: Unable to open socket for local > _X11TransOpen: transport open failed for local/dinolt1.bingdrive:0 > setup.bin: cannot open display ":0.0" > Please check your "DISPLAY" environment variable, as well as the > permissions to access that display (See "man X" resp. "man xhost" for > details) same here :( i got original Sun CD with StartOffice 5.1a and tried to install it. it failed. i used # make WITH_CDROM=yes USE_CDROM=yes install and everything was fine, but then i got exactly the same error. XFree86-3.3.6 and XFree86-contrib-3.3.6 both working just fine. ``xhost +'' did not resolve the problem. thanks, emax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux ABI no longer supports staroffice
"George W. Dinolt" wrote: > > I was wondering whether the setrlimit changes had something to do with > this. This seems to be the major change to the linux code in the last > few days. Apparently you were the one to make those changes, so I am > writing to you (Marcel) Can you track down which change caused the failure. I haven't experienced any problems so far. I'll try running SO myself in the mean time. -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
