On Wed, 23 Feb 2000, Kenneth Wayne Culver wrote:
That's odd... I just built it tonight, and I havn't had anything but this:
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat
That's odd... I just built it tonight, and I havn't had anything but this:
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86-Bigfont extension: shmat() failed, size = 4096, errno = 24
XFree86
SSIA, pretty much. I also installed /usr/ports/x11/XFree86-contrib
which doesn't contain that program, either. Did I do something wrong?
I installed a minimal 3.1 from CD (without X11), then made the
-CURRENT world, then installed the above mentioned ports. All of this
a week or so ago; I
On 11 Feb, Kai Großjohann wrote:
I installed a minimal 3.1 from CD (without X11), then made the
-CURRENT world, then installed the above mentioned ports. All of this
a week or so ago; I forgot the exact date.
XF86Setup needs tcl/tk. tcl/tk needs XFree86. If there's no tcl/tk
XF86Setup isn't
Alexander Leidinger [EMAIL PROTECTED] writes:
XF86Setup needs tcl/tk. tcl/tk needs XFree86. If there's no tcl/tk
XF86Setup isn't compiled. After installing tcl/tk and rebuilding XFree86
there should be a XF86Setup binary.
May I humbly suggest that this be put somewhere into the
documentation
Hi all!
I don't know if this has been addressed already, but the archives are
offline.
I started using current by installing 2127-SNAP of current.freebsd.org
including XFree86 3.3.6. The Xfree86 a.out libraries were missing
from the installtion tarballs, so e.g. Netscape would not run.
I
"Patrick M. Hausen" wrote:
Hi all!
I don't know if this has been addressed already, but the archives are
offline.
I started using current by installing 2127-SNAP of current.freebsd.org
including XFree86 3.3.6. The Xfree86 a.out libraries were missing
from the installtio
Hello,
I was installing the 4.0 snapshot of 1/27/2000
when it asked if I wanted to install the XFree86 stuff.. I kept getting
this error
lib/X11/XF86Setup/texts/ja/help_keyboard.tcl
lib/X11/XF86Setup/texts/ja/help_monitor.tcl
lib/X11/XF86Setup/texts/ja/help_mouse.tcl
lib/X11/XF86Setup/texts/ja
(trimmed the long cc:-list)
On Tue, Jan 18, 2000 at 07:51:22AM +0200, Vallo Kallaste wrote:
The problem with 3.3.5 was something to do with refreshing, example
after doing some ls -la in xterm the xterm screen got blank completely
or showed some lines of text in the bottom but otherwise
On Tue, Jan 18, 2000 at 07:51:22AM +0200, Vallo Kallaste [EMAIL PROTECTED]
wrote:
I can say that I tried building the 3.9.17 with both official compiler
in -current and also with gcc-devel, both built fine but didn't install.
Seems like my fault, nothing else. Time to try again.
It seems
Hi,
I succeeded in building XFree86 3.9.17 on 4.0-CURRENT w/o doing anything
special except removing doc from the list of subdirs...
-=-=-
./to_wfont -o Roman.phont Roman.src
./to_wfont -o Roman_M.phont Roman_M.src
[1] + done make World makeworld 2 1
Mon Jan 17 18:02:33 CET 2000
Full
On Mon, Jan 17, 2000 at 06:19:23PM +0100, Ollivier Robert [EMAIL PROTECTED]
wrote:
I succeeded in building XFree86 3.9.17 on 4.0-CURRENT w/o doing anything
special except removing doc from the list of subdirs...
-=-=-
./to_wfont -o Roman.phont Roman.src
./to_wfont -o Roman_M.phont
, Jan 17, 2000 at 06:19:23PM +0100, Ollivier Robert [EMAIL PROTECTED]
wrote:
I succeeded in building XFree86 3.9.17 on 4.0-CURRENT w/o doing anything
special except removing doc from the list of subdirs...
-=-=-
./to_wfont -o Roman.phont Roman.src
./to_wfont -o Roman_M.phont Roman_M.src
Vallo Kallaste wrote:
Have you tried to install it? It does builds but barfs at some point for
install process. Not that I care so much about it, 3.3.6 works for my
G400 now, thanks god.
What I did was: build it using the stock gcc-2.95.2 compiler, for
make World. During make install, I
?
3.3.5 (built from the port) lives quite happily on my G400?
I'm very eager to get my hands on a XFree86 with dual-head support
and truetype-rendering, therefor my interest in the XFree86 prereleases.
During make install, I switched compilers by setting
PATH=/usr/local/bin:$PATH.
ahhh
I've been reworking the FreeBSD configuration file for XFree86 3.9.17. At
the moment, I've only done Intel. (Don't despair Alpha folks -- I'll get
myself a Compaq testdrive account :-))
This file is a drop-in replacement for 'xc/config/cf/FreeBSD.cf' You don't
need any 'xc/config/cf/host.def
On Tue, Jan 18, 2000 at 01:17:53AM +0100, Andreas Braukmann wrote:
Is the gcc-2.96-current in the ports collection?
Yes. /usr/ports/lang/gcc-devel
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
On Tue, Jan 18, 2000 at 01:17:53AM +0100, Andreas Braukmann [EMAIL PROTECTED]
wrote:
... what was the problem with the G400 in earlier revisions?
3.3.5 (built from the port) lives quite happily on my G400?
I'm very eager to get my hands on a XFree86 with dual-head support
and truetype
Hi,
Does anybody successfully using any DGA-based programs on recently
recompiled Xfree 3.3.5? I have a problem with it and for me it seems
broken. For example standart XFree86 test program 'dga' returns
following error on my two -current machines (Mach64 and CT 65554
servers recompiled
I've just been doing a build test of the pre-3.3.6 version of
XFree86 on a recent FreeBSD 4.0-current, and I've noticed that
/usr/libexec/cpp doesn't predefine the symbol __FreeBSD__. imake
uses /usr/libexec/cpp. Is it intentional that /usr/libexec/cpp
not predefine any symbols like this? I've
On Wed, Jan 05, 2000 at 09:15:07PM -0800, David O'Brien wrote:
Correct. The change is due to philosophical changes by the GCC
development team. GCC 2.95.2's cpp built from cccp.c is now a pure
preprocessor and knows much less about the world than it previously did.
In 2.95.2 there is
I am using yesterday's snapshot (12-27). /etc/pam.conf is dated 12/21.
Tom Veldhouse
[EMAIL PROTECTED]
Mark Murray wrote:
I just got my box up and running Current 12-27. ATA works great for =
both drives now. However, I compiled XFree86 from the port and I chose =
the options
works great for both
drives now. However, I compiled XFree86 from the port and I chose the options for
RPC, Wraphelp.c, PAM and threads. When I start x (using startkde), I get many many
password prompts. I can only assume that the PAM module used for athentication by
XFree86 is broken
Hello,
I just got my box up and running
Current 12-27. ATA works great for both drives now. However, I
compiled XFree86 from the port and I chose the options for RPC, Wraphelp.c, PAM
and threads. When I start x (using startkde), I get many many password
prompts. I can only assume
Hello,
I just got my box up and running Current 12-27. ATA works great for
both drives now. However, I compiled XFree86 from the port and I chose the
options for RPC, Wraphelp.c, PAM and threads. When I start x (using
startkde), I get many many password prompts. I can only assume
On Mon, Dec 27, 1999 at 11:01:50PM -0600, Thomas T. Veldhouse wrote:
Hello,
I just got my box up and running Current 12-27. ATA works great for both drives
now. However, I compiled XFree86 from the port and I chose the options for RPC,
Wraphelp.c, PAM and threads. When I start x
I just got my box up and running Current 12-27. ATA works great for =
both drives now. However, I compiled XFree86 from the port and I chose =
the options for RPC, Wraphelp.c, PAM and threads. When I start x (using =
startkde), I get many many password prompts. I can only assume
Hi,
The latest XFree86 snapshot, 3.9.16f (which is about to become
the public 3.9.17 snapshot) does not build on FreeBSD -current.
It compains about fcvt, ecvt and gcvt.
The exact error log from building XFree86 3.9.16f follows.
It compiles ok on my 3.4 box (just CVSuped)
The next public
Hi,
The latest XFree86 snapshot, 3.9.16f (which is about to become
the public 3.9.17 snapshot) does not build on FreeBSD -current.
It compains about fcvt, ecvt and gcvt.
The exact error log from building XFree86 3.9.16f follows.
It compiles ok on my 3.4 box (just CVSuped)
The problem
On Fri, Dec 17, 1999 at 02:08:50PM -0800, Eric Anholt wrote:
The problem is that gcc 2.95.2 in -current does not include #define
The problem is that /usr/libexec/cpp ...
__FreeBSD__ any more. XF can't tell the OS, so it assumes you lack
A fix is on the way RSN.
--
-- David([EMAIL
Here is how i compiled XFree86 today (an additonal file for
/usr/ports/x11/XFree86/patches):
http://es-i2.fernuni-hagen.de/~jfh/FreeBSD_Documentation/node7.html
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany)
tel:+49 2331/987-1166 fax:987
This patch might be a bit heavy handed, but it seems to fix the
problem...
The KerberosIV bits can go; I have some cleanups that nuke that completely in favour
of PAM. Now all I need to do is make PAM work for xdm...
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To
Hi folks,
A sequence of silly mistakes and circumstances have conspired against me
to make it impossible for me to run XFree86. I understand that the
XFree86 build is broken in the face of recent signal-related changes.
I want to know how long I can expect to wait for XFree86 to build
Hi folks,
A sequence of silly mistakes and circumstances have conspired against me
to make it impossible for me to run XFree86. I understand that the
XFree86 build is broken in the face of recent signal-related changes.
I want to know how long I can expect to wait for XFree86 to build
-6326 has a strange problem with XFree86-3.3.5. I´ll try
some Options, in the XF86Config file tomorrow and then report it to
XFree86.org. Does anyone else have one of these running with 3.3.5?
I had what sound like similar problems with a SiS card (sorry, I don't
have the model number handy right now
and everything else the same.
Looks like the SiS-6326 has a strange problem with XFree86-3.3.5. I´ll try
some Options, in the XF86Config file tomorrow and then report it to
XFree86.org. Does anyone else have one of these running with 3.3.5?
I had what sound like similar problems with a SiS
This morning I made world, updated XFree86 and kde, which didn´t seem to
be a problem until I started X and nowI get revers Icon's - silhouettes
on the kde background. I get no text but a block where the text is and
the mouse will often change to a block. I have never seen anything like
it. I
I can only start my Xfree when ppp is up and running, is that a known problem ?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I can only start my Xfree when ppp is up and running, is that a known problem ?
It's known that your DNS setup is busted, yes.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph Merrick \\ [EMAIL PROTECTED]
yeah, thanks.
- Original Message -
From: Mike Smith [EMAIL PROTECTED]
To: Tomer Weller [EMAIL PROTECTED]
Cc: Current [EMAIL PROTECTED]; Questions [EMAIL PROTECTED]
Sent: Wednesday, September 08, 1999 8:34 PM
Subject: Re: weird Xfree86 Issue
I can only start my Xfree when ppp is up
, and it seems that
it isn't unusual for an Xserver to open all devices at server startup,
and not close them until server exit. There are provisions for delaying
the open until the device is referenced, and for closing it before the
server exits. The XFree86-specific XInput code does the former
David Dawes writes:
IMHO the problem is in the joystick driver and in your assumptions. By
configuring the joystick in your Xserver config file, you're giving the
server exclusive use of the device for the lifetime of the X server
process. Implementing more agressive closing might
devices, the fd is added to the list of
fds to select() on. For the joystick device, a timer callback is
installed to check the device at regular intervals. This is never
disabled once it has been started.
If someone has a fix for this, please submit it to pa...@xfree86.org
and it can be included
On Wed, May 19, 1999 at 01:20:01AM +0930, Matthew Thyer wrote:
I have confirmed that the problem occurs if I just do:
xsetpointer Joystick
sleep 1
xsetpointer pointer
So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest.
So the problem appears to be with XFree86
, Matthew Thyer wrote:
I have confirmed that the problem occurs if I just do:
xsetpointer Joystick
sleep 1
xsetpointer pointer
So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest.
So the problem appears to be with XFree86 not closing the joystick
device after I've
I have confirmed that the problem occurs if I just do:
xsetpointer Joystick
sleep 1
xsetpointer pointer
So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest.
So the problem appears to be with XFree86 not closing the joystick
device after I've used it as a pointer
since egcs went in, so I know it's working
ok. Anyway, I decided to update my XFree86 installation,
and found that the port no longer works. As it compiles
all binaries created report tons of missing symbols
from the various X library. The wierd thing
I know it's working
ok. Anyway, I decided to update my XFree86 installation,
and found that the port no longer works. As it compiles
all binaries created report tons of missing symbols
from the various X library. The wierd thing is that it
still installs most of the X
In article 199904271932.naa01...@zen.alb.khoral.com,
Steve Jorgensen st...@khoral.com wrote:
I cvsup'ed and installed yesterday morning it's the third
cvsup I've done since egcs went in, so I know it's working
ok. Anyway, I decided to update my XFree86 installation
I cvsup'ed and installed yesterday morning it's the third
cvsup I've done since egcs went in, so I know it's working
ok. Anyway, I decided to update my XFree86 installation,
and found that the port no longer works. As it compiles
all binaries created
. Anyway, I decided to update my XFree86 installation,
and found that the port no longer works. As it compiles
all binaries created report tons of missing symbols
from the various X library. The wierd thing is that it
still installs most of the X binaries anyway
In article 199904271932.naa01...@zen.alb.khoral.com,
Steve Jorgensen st...@khoral.com wrote:
I cvsup'ed and installed yesterday morning it's the third
cvsup I've done since egcs went in, so I know it's working
ok. Anyway, I decided to update my XFree86 installation
Hello,
On Apr10 I rebuilt the XFree86 Port with aout compatibility libraries
running current of Apr04. Immediately following Netscape Communicator
would dump core with a bus error.
I'm not sure if this is relevant or not, but when it dumps core the core
file name is truncated.
ca...@vanessa
On Mon, 12 Apr 1999, Kevin G. Eliuk wrote:
I installed linux-netscape-4.08 and it opens with bus error or signal 10.
That should be without
--
Regards,
Kevin G. Eliuk
Box 67, Granthams Landing, BC VON 1X0 (604)886-4040
Discover Rock Solid,
)
problem with our crappy antique a.out gas. After rebuilding egcs, and
rebuilding the a.out XFree86 libraries, netscape works again. I was having
the same problem as you until then.
Cheers,
-Peter
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
Hello!
I've recently fetched and built XFree86 3.3.3.1, and some programs (most
notably xterm and xemacs 20.4, built from ports also) fails to input Russian
letters, using either locale or .xmodmap method.
What should I set up? I've tried config file from my (_working_) XFree 3.3.3
Is anyone able to build or even link a single program with XFree86 3.3.5
building system ? The damn things defines CppCmd to /lib/cpp and the
Makefiles generated are completely fscked up.
This is under CURRENT.
I tried the 3.x binaries but xinit is dumping core (!!).
401 [15:56] root
401 - 457 of 457 matches
Mail list logo
