Re: XFree86-4-clients port broken.
David Gilbert wrote: I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports /lib/libfntstubs.a. Stop I ran into this on my amd64 box too. Is yours an i386? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XFree86-4-clients port broken.
On Mon, Oct 13, 2003 at 03:51:06PM -0700, Peter Wemm wrote: David Gilbert wrote: I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports /lib/libfntstubs.a. Stop I ran into this on my amd64 box too. Is yours an i386? The port is broken on all architectures. anholt is looking into it. Kris pgp0.pgp Description: PGP signature
Re: XFree86-4-clients port broken.
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: David Gilbert wrote: I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports /lib/libfntstubs.a. Stop I ran into this on my amd64 box too. Is yours an i386? This is a problem on ref5, too. I am testing a fix right now. The confusing part is I can't find any change I (or anyone else) has made that would have caused this. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XFree86-4-clients port broken.
Eric Anholt wrote: On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: David Gilbert wrote: I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exp orts /lib/libfntstubs.a. Stop I ran into this on my amd64 box too. Is yours an i386? This is a problem on ref5, too. I am testing a fix right now. The confusing part is I can't find any change I (or anyone else) has made that would have caused this. Does the port have any exposure to make(1) at all? Its been futzed with fairly recently. I know it's supposed to use gmake, but perhaps there are still some make references? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XFree86-4-clients port broken.
On Mon, 2003-10-13 at 16:05, Peter Wemm wrote: Eric Anholt wrote: On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: David Gilbert wrote: I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exp orts /lib/libfntstubs.a. Stop I ran into this on my amd64 box too. Is yours an i386? This is a problem on ref5, too. I am testing a fix right now. The confusing part is I can't find any change I (or anyone else) has made that would have caused this. Does the port have any exposure to make(1) at all? Its been futzed with fairly recently. I know it's supposed to use gmake, but perhaps there are still some make references? No, actually it uses the system (bsd) make. It generally is pretty resistant to differences with different types of make, though. Testing a new idea for a fix that will cut the build time/space required, too. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XFree86-4-clients port broken.
Peter == Peter Wemm [EMAIL PROTECTED] writes: Peter David Gilbert wrote: I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports Peter /lib/libfntstubs.a. Stop Peter I ran into this on my amd64 box too. Is yours an i386? Yes. I'm getting it on an intel centrino. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XFree86-4-clients port broken.
Peter == Peter Wemm [EMAIL PROTECTED] writes: Peter Eric Anholt wrote: On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: David Gilbert wrote: I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exp Peter orts /lib/libfntstubs.a. Stop I ran into this on my amd64 box too. Is yours an i386? This is a problem on ref5, too. I am testing a fix right now. The confusing part is I can't find any change I (or anyone else) has made that would have caused this. Peter Does the port have any exposure to make(1) at all? Its been Peter futzed with fairly recently. I know it's supposed to use Peter gmake, but perhaps there are still some make references? If you look at the port, it uses make fairly extensively now. The Makefile (from my limited understanding) seems to charge into building the port without calling gmake by adding sub directories much like the /usr/src makefile seems to do. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XFree86-4-clients port broken.
On Mon, 2003-10-13 at 14:54, David Gilbert wrote: I don't really have a clue where to look for this fix as there seems to be a serious amount of magic going into the divided XFree86-4 port builds, but my XFree86-4-clients port fails saying: make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop Dave. It should be fixed now. Please cvsup (in ~1hour) and try again. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XFree86-4-libraries build error
Peter Schultz [EMAIL PROTECTED] writes: Amazing, the obvious. Now I get this: Hmm, I didn't get any more trouble after I fixed the pragma problem. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4-libraries build error
Wilko Bulte wrote: On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote: FWIW: same here yesterday. I have not yet investigated what's up gcc-3.1 appears to have broken #pragma weak foo = bar Wilko I'm getting the following error on a just built -current, which was a fresh install of 5.0-CURRENT-20020519-JPSNAP: installing in lib/XThrStub... rm -f UIThrStubs.o LD_LIBRARY_PATH=../../exports/lib cc -c -O -pipe-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. -I../../exports/include -DCSRG_BASED -DFUNC PROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DM ALLOC_0_RETURNS_NULL-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith-I. ./.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHR EADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -fPI C UIThrStubs.c UIThrStubs.c:102: alias arg not a string UIThrStubs.c:103: alias arg not a string UIThrStubs.c:104: alias arg not a string UIThrStubs.c:105: alias arg not a string UIThrStubs.c:106: alias arg not a string UIThrStubs.c:107: alias arg not a string UIThrStubs.c:108: alias arg not a string UIThrStubs.c:109: alias arg not a string UIThrStubs.c:110: alias arg not a string UIThrStubs.c:111: alias arg not a string UIThrStubs.c:113: alias arg not a string UIThrStubs.c:114: alias arg not a string UIThrStubs.c:115: alias arg not a string UIThrStubs.c:131: warning: `_Xthr_self_stub_' defined but not used UIThrStubs.c:139: warning: `_Xthr_zero_stub_' defined but not used *** Error code 1 Stop in /usr/ports/x11/XFree86-4-libraries/work/xc/lib/XThrStub. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message ---end of quoted text--- -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4-libraries build error
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote: Wilko Bulte wrote: On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote: FWIW: same here yesterday. I have not yet investigated what's up gcc-3.1 appears to have broken #pragma weak foo = bar What's the correct way to do this now? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4-libraries build error
Alfred Perlstein wrote: * Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote: Wilko Bulte wrote: On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote: FWIW: same here yesterday. I have not yet investigated what's up gcc-3.1 appears to have broken #pragma weak foo = bar What's the correct way to do this now? I dont know. :-( There are hacks that can work around it, but I think this is unintentional breakage. I tried changing this: #pragma weak foo = bar to __weak_reference(bar, foo); But I didn't get much further since Xfree86 was provoking internal compiler errors. Turning off -O entirely got around it a few times, and then I had more failures with lack of c++ libraries. The end result of all the futzing around ended up with a set of binaries that were basically hosed and usually segfaulted on startup. Shortly after that point, I then managed to panic my system (running 5.x) and said to hell with it and did a pkg_add -r to install it instead. I'm in the middle of moving, so I haven't had much more of a chance to look at it. There are GCC bugs involved. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4-libraries build error
#pragma weak foo = bar What's the correct way to do this now? I dont know. :-( There are hacks that can work around it, but I think this is unintentional breakage. I tried changing this: #pragma weak foo = bar to __weak_reference(bar, foo); void f () __attribute__ ((weak, alias (__f))); (But that may come to the same thing). M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4-libraries build error
Alfred Perlstein [EMAIL PROTECTED] writes: * Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote: gcc-3.1 appears to have broken #pragma weak foo = bar What's the correct way to do this now? #pragma weak foo = bar as you'd have guessed if you'd bothered to read the error message and look at the code DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4-libraries build error
Dag-Erling Smorgrav wrote: Alfred Perlstein [EMAIL PROTECTED] writes: * Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote: gcc-3.1 appears to have broken #pragma weak foo = bar What's the correct way to do this now? #pragma weak foo = bar as you'd have guessed if you'd bothered to read the error message and look at the code DES Amazing, the obvious. Now I get this: rm -f ../../../../../lib/GL/mesa/src/translate.o unshared/../../../../../lib/GL/mesa/src/translate.o LD_LIBRARY_PATH=../../../../../exports/lib cc -c -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../../../../../exports/include/X11 -I../../../../../include/extensions -I../../../../../extras/Mesa/src/OSmesa -I../../../../../extras/Mesa/src -I../../../../../extras/Mesa/include -I../../../../.. -I../../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI -DMALLOC_0_RETURNS_NULL ../../../../../lib/GL/mesa/src/translate.c -o unshared/../../../../../lib/GL/mesa/src/translate.o Assembler messages: FATAL: can't create unshared/../../../../../lib/GL/mesa/src/translate.o: No such file or directory *** Error code 1 Stop in /usr/ports/x11/XFree86-4-libraries/work/xc/lib/GL/mesa/src/OSmesa. The make needs to go back one more level: unshared/../../../../../../lib/GL/mesa/src/translate.o How to do this, I do not know. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4-libraries build error
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote: I'm getting the following error on a just built -current, which was a fresh install of 5.0-CURRENT-20020519-JPSNAP: Yes, and if you'd been reading the mailing list like you're supposed to you would have already known about this. Kris msg39019/pgp0.pgp Description: PGP signature
Re: XFree86-4-libraries build error
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote: FWIW: same here yesterday. I have not yet investigated what's up Wilko I'm getting the following error on a just built -current, which was a fresh install of 5.0-CURRENT-20020519-JPSNAP: installing in lib/XThrStub... rm -f UIThrStubs.o LD_LIBRARY_PATH=../../exports/lib cc -c -O -pipe-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. -I../../exports/include -DCSRG_BASED -DFUNC PROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DM ALLOC_0_RETURNS_NULL-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith-I. ./.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHR EADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -fPI C UIThrStubs.c UIThrStubs.c:102: alias arg not a string UIThrStubs.c:103: alias arg not a string UIThrStubs.c:104: alias arg not a string UIThrStubs.c:105: alias arg not a string UIThrStubs.c:106: alias arg not a string UIThrStubs.c:107: alias arg not a string UIThrStubs.c:108: alias arg not a string UIThrStubs.c:109: alias arg not a string UIThrStubs.c:110: alias arg not a string UIThrStubs.c:111: alias arg not a string UIThrStubs.c:113: alias arg not a string UIThrStubs.c:114: alias arg not a string UIThrStubs.c:115: alias arg not a string UIThrStubs.c:131: warning: `_Xthr_self_stub_' defined but not used UIThrStubs.c:139: warning: `_Xthr_zero_stub_' defined but not used *** Error code 1 Stop in /usr/ports/x11/XFree86-4-libraries/work/xc/lib/XThrStub. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message ---end of quoted text--- -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Xfree86-4 problem
On Sat, Apr 20, 2002 at 12:02:11AM +0200, John Angelmo wrote: Kris Kennaway wrote: On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote: After yesterdays new build I found a problem Xfree86-4 can't start as regular user (exept root) Read the fine message you got at install-time and install the wrapper port. Kris Wrapper is installed it allways has been, X starts but not the windowmanager (fluxbox or tmw) Okay, well that's not what you said, is it? :-) Please post the exact error messages. Kris msg37452/pgp0.pgp Description: PGP signature
Re: Xfree86-4 problem
On Fri, Apr 19, 2002 at 08:56:50PM -0700, James Satterfield wrote: I've found that wrapper needs to be updated with XFree86-4. wrapper always needs to be rebuilt when you update X, yes. Kris msg37453/pgp0.pgp Description: PGP signature
Re: Xfree86-4 problem
Kris Kennaway wrote: On Sat, Apr 20, 2002 at 12:02:11AM +0200, John Angelmo wrote: Kris Kennaway wrote: On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote: After yesterdays new build I found a problem Xfree86-4 can't start as regular user (exept root) Read the fine message you got at install-time and install the wrapper port. Kris Wrapper is installed it allways has been, X starts but not the windowmanager (fluxbox or tmw) Okay, well that's not what you said, is it? :-) Please post the exact error messages. Kris Well X starts but just to the gray area, no windowmanager starts and the error I get(after I have exited) is: AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:15 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:17 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:19 2002: 16472 XFree86: client 1 rejected from local host /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Xfree86-4 problem
On Sat, Apr 20, 2002 at 10:39:22PM +0200, John Angelmo wrote: Well X starts but just to the gray area, no windowmanager starts and the error I get(after I have exited) is: AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:15 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:17 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:19 2002: 16472 XFree86: client 1 rejected from local host Do you have a hostname? I've found that X does this without one set. For the purposes of X, it doesn't appear to matter if it maps to an address or not. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg37455/pgp0.pgp Description: PGP signature
Re: Xfree86-4 problem
On Sat, 20 Apr 2002 13:35:32 -0700 Kris Kennaway [EMAIL PROTECTED] wrote: KK wrapper always needs to be rebuilt when you update X, yes. All you really need to do is reset the X symlink (unless you are upgrading from 3 to 4 in which case you need a new wrapper). -- C:WIN | Directable Mirrors The computer obeys and wins.|A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Xfree86-4 problem
On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote: After yesterdays new build I found a problem Xfree86-4 can't start as regular user (exept root) Read the fine message you got at install-time and install the wrapper port. Kris msg37428/pgp0.pgp Description: PGP signature
Re: Xfree86-4 problem
Kris Kennaway wrote: On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote: After yesterdays new build I found a problem Xfree86-4 can't start as regular user (exept root) Read the fine message you got at install-time and install the wrapper port. Kris Wrapper is installed it allways has been, X starts but not the windowmanager (fluxbox or tmw) /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Xfree86-4 problem
I've found that wrapper needs to be updated with XFree86-4. James. - Original Message - From: John Angelmo [EMAIL PROTECTED] To: current [EMAIL PROTECTED] Sent: Friday, April 19, 2002 1:13 PM Subject: Xfree86-4 problem After yesterdays new build I found a problem Xfree86-4 can't start as regular user (exept root) this is the error message I get: AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:15 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:17 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:19 2002: 16472 XFree86: client 1 rejected from local host Does anyone have any idea? /John 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: xfree86 4?
What are the plans about replacing XFree86 3.3.6 with XFree86 4? According to plan, FreeBSD 4.6-RELEASE will have XFree86 4, so sometime after this month and before the next release. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4 required?
On Fri, Oct 19, 2001 at 11:44:42AM -0700, David O'Brien wrote: On Thu, Oct 18, 2001 at 09:33:09PM +0200, Riccardo Torrini wrote: Is a real need for ports under -CURRENT to require (from a week or two, I don't remember) XFree86-libraries? Yes. To elaborate a bit, the default XFree86 version in -current was recently changed from 3 to 4. Thus, if you still want to go with your XFree86-3.x installation, you have to explicitly set XFREE86_VERSION to 3. G'luck, Peter -- This sentence no verb. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4 required?
On Thu, Oct 18, 2001 at 09:33:09PM +0200, Riccardo Torrini wrote: Is a real need for ports under -CURRENT to require (from a week or two, I don't remember) XFree86-libraries? Yes. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4 required?
On Thu, Oct 18, 2001 at 09:33:09PM +0200, Riccardo Torrini wrote: Is a real need for ports under -CURRENT to require (from a week or two, I don't remember) XFree86-libraries? They asks for XFree86-libraries-4.1.0, but I have 3.3.6_10 installed. Can I (safetly) mix 3.3.6 and 4.1.0? Is the upgrade from 3.3.6 to 4.1.0 really needed? Planned? I haven't set XFREE86_VERSION=4 (or anything else) in make.conf I updated again ports tree now, on my -STABLE and -CURRENT boxes, but xfree-4-libraries are still neeed (even imake-4) I believe current tries to install 4.1.0 now since 3.3.6 is really old. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4 can't start
"Michael L. Imamura" wrote: I haven't tried xfce, but I had some problems running Enlightenment 16.3, all related to shared memory. I disabled shared pixmaps in my Imlib configuration and that got rid of the random crashing, but is again not a very optimal solution :) I'm guessing it's a problem with the current GTK version and X4. Try starting xfce with "--no-xshm" and/or "--no-shm" and see if the problem clears up. Unfortunately those options aren't available, either at run time or compile time AFAICS. I'm in no hurry to migrate to X4 though, so I don't really mind. I've heard enough people give good reports about it that I thought it was worth a try, but I can wait. Thanks, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
On Sat, Mar 11, 2000 at 12:24:10PM -0800, Nawfal M. Rouyan wrote: Hi, I've installed XFree86 version 4 trough the ports collection but it won't start and I think it is because of the missing mouse module. Since I'm using lynx, I can't attached the /var/log/XFree86.0.log file for your reference. I can only paste the error I found in the file. . (II) LoadModule: "mouse" (WW) Warning, couldn't open module mouse (II) UnloadModule: "mouse" (EE) Failed to load module "mouse" (module does not exist, 0) . (EE) No Input driver matching `mouse' (II) Keyboard "Keyboard1" handled by legacy driver (WW) No core pointer registered No core pointer Fatal server error: failed to initialize core devices I fall into the same... with 3.9.17 everything was fine/ It seems that mouse_drv.o is not build automaticaly at least with the port. If I buld it myself it's working. I also got other problems with /usr/X11R6 linked to /vol/X11R6 which is automounted. Some of the build softlinks getting make install to fail. It was the link to /usr/X11R6/lib/X11/app-defaults. I put schg on /usr/X11R6/lib/X11 and installed with make -i. Netscape is also a problem: bash-2.03$ netscape ld.so failed: Undefined symbol "__Xglobal_lock" in navigator-4.7.bin:/usr/X11R6/lib/aout/libXext.so.6.3 -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 mouse?
On Sat, Mar 11, 2000 at 04:10:26PM -0500, Ted Sikora wrote: My problem is a little different. XFree86-4.0 loads fine looks great but the mouse does not work. There are no errors. I tried PS/2 , serial, etc same with them all. The pointer appears then moves to the upper right and dissappers. I tried moving it...Mouse1, etc. but nothing Any ideas? Yeah, I have it working under -CURRENT: XFree86 Version 4.0 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 8 March 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: FreeBSD 4.0-CURRENT i386 [ELF] [snip] (==) Mouse1: Protocol: "Auto" (**) Mouse1: Core Pointer (==) Mouse1: Buttons: 3 Relevant config in XF86Config: Identifier "Mouse1" Driver "mouse" Option "Device" "/dev/sysmouse" If you don't specify a protocol, XF86-4 will auto-probe the device and should pick it up no problem. This particular problem is mentioned in the documentation for XFree86 4.0 by the way, as well as how to resolve it. I should also note I didn't build mine from the ports (the port wasn't available when I built it) but from the raw source. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
I was able to get it working through a small patch to the
scripts/configure file. Probably not the most optimal solution, but it
works until the port is updated:
--- configure Fri Mar 10 19:20:34 2000
+++ configure.2 Sat Mar 11 18:19:55 2000
@@ -197,7 +197,7 @@
echo "#define BuildXInputExt NO" $F
else
echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \
-mutouch spaceorb wacom" $F
+mutouch spaceorb wacom mouse" $F
# XXX broken in 3.9.18
# if [ X${MACHINE} != X"alpha" ]; then
#echo "#define JoystickSupport YES" $F
Michael L. Imamura
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: [EMAIL PROTECTED]
On Sat, 11 Mar 2000, Nawfal M. Rouyan wrote:
Hi,
I've installed XFree86 version 4 trough the ports
collection
but it won't start and I think it is because of the
missing mouse module. Since I'm using lynx, I can't
attached the /var/log/XFree86.0.log file for your
reference. I can only paste the error I found in the
file.
.
(II) LoadModule: "mouse"
(WW) Warning, couldn't open module mouse
(II) UnloadModule: "mouse"
(EE) Failed to load module "mouse" (module does not
exist, 0)
.
(EE) No Input driver matching `mouse'
(II) Keyboard "Keyboard1" handled by legacy driver
(WW) No core pointer registered
No core pointer
Fatal server error:
failed to initialize core devices
I'm using NVidia RIVA 128ZX with 8MB RAM and the X
server
detects it successfully. Any suggestions to solve my problems?
__
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
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: XFree86-4 can't start
Nawfal M Rouyan writes:
Hi,
I've installed XFree86 version 4 trough the ports
collection
but it won't start and I think it is because of the
missing mouse module. Since I'm using lynx, I can't
attached the /var/log/XFree86.0.log file for your
reference. I can only paste the error I found in the
Yes, the mouse drive was not built :-(. TRy again with the following
patch to scripts/configure
Jean-Marc
Index: scripts/configure
===
RCS file: /home/ncvs/ports/x11/XFree86-4/scripts/configure,v
retrieving revision 1.58
diff -u -r1.58 configure
--- scripts/configure 2000/03/11 00:20:34 1.58
+++ scripts/configure 2000/03/12 00:23:57
@@ -196,7 +196,7 @@
echo "#undef BuildXInputExt" $F
echo "#define BuildXInputExt NO" $F
else
- echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \
+ echo "#define XInputDrivers mouse dynapro elo2300 elographics magellan microtouch \
mutouch spaceorb wacom" $F
# XXX broken in 3.9.18
# if [ X${MACHINE} != X"alpha" ]; then
--
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: XFree86-4 can't start
"Michael L. Imamura" wrote:
I was able to get it working through a small patch to the
scripts/configure file. Probably not the most optimal solution, but it
works until the port is updated:
--- configure Fri Mar 10 19:20:34 2000
+++ configure.2 Sat Mar 11 18:19:55 2000
@@ -197,7 +197,7 @@
echo "#define BuildXInputExt NO" $F
else
echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \
-mutouch spaceorb wacom" $F
+mutouch spaceorb wacom mouse" $F
# XXX broken in 3.9.18
# if [ X${MACHINE} != X"alpha" ]; then
#echo "#define JoystickSupport YES" $F
that got me to the point where I could start X, but xfce won't start. I
get the following errors:
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
serial 63 error_code 10 request_code 141 minor_code 1
Gdk-ERROR **: BadShmSeg (invalid shared segment parameter)
serial 64 error_code 143 request_code 141 minor_code 5
I have shared memory compiled into my kernel, not sure what this could
be if it's not an X 4 problem. xfwm does start though, odd.
Doug
--
"Welcome to the desert of the real."
- Laurence Fishburne as Morpheus, "The Matrix"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
I haven't tried xfce, but I had some problems running Enlightenment 16.3,
all related to shared memory. I disabled shared pixmaps in my Imlib
configuration and that got rid of the random crashing, but is again not a
very optimal solution :) I'm guessing it's a problem with the current GTK
version and X4.
Try starting xfce with "--no-xshm" and/or "--no-shm" and see if the
problem clears up.
Michael L. Imamura
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: [EMAIL PROTECTED]
On Sat, 11 Mar 2000, Doug Barton wrote:
"Michael L. Imamura" wrote:
I was able to get it working through a small patch to the
scripts/configure file. Probably not the most optimal solution, but it
works until the port is updated:
--- configure Fri Mar 10 19:20:34 2000
+++ configure.2 Sat Mar 11 18:19:55 2000
@@ -197,7 +197,7 @@
echo "#define BuildXInputExt NO" $F
else
echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \
-mutouch spaceorb wacom" $F
+mutouch spaceorb wacom mouse" $F
# XXX broken in 3.9.18
# if [ X${MACHINE} != X"alpha" ]; then
#echo "#define JoystickSupport YES" $F
that got me to the point where I could start X, but xfce won't start. I
get the following errors:
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
serial 63 error_code 10 request_code 141 minor_code 1
Gdk-ERROR **: BadShmSeg (invalid shared segment parameter)
serial 64 error_code 143 request_code 141 minor_code 5
I have shared memory compiled into my kernel, not sure what this could
be if it's not an X 4 problem. xfwm does start though, odd.
Doug
--
"Welcome to the desert of the real."
- Laurence Fishburne as Morpheus, "The Matrix"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 mouse?
Ted Sikora wrote: My problem is a little different. XFree86-4.0 loads fine looks great but the mouse does not work. There are no errors. I tried PS/2 , serial, etc same with them all. The pointer appears then moves to the upper right and dissappers. I tried moving it...Mouse1, etc. but nothing Any ideas? Note:XF86Config works well but XFree86 -configure gives a bad config Got it working. The new config takes a bit getting used to. The default xf86config generated script puts all devices at 1 as in "Mouse 1". When I changed the mouse to "0 "and set it at auto it worked. All others I left at "1". XFree86 -configure sets all at "0" but leaves a bit of info out rendering it useless without editing. It leaves the screen modes out. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] http://powerusersbbs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
