Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Martin Blapp wrote: Hi, I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. is it enough to setenv GCC=/usr/local/bin/gcc31, then make install ? TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Fri, Jun 21, 2002 at 06:50:49PM +0200, Thierry Herbelot wrote: I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. is it enough to setenv GCC=/usr/local/bin/gcc31, then make install ? No. make CC=gcc31 CXX=g++31 clean install To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[Patch] Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On 2002-06-21 14:33 +0200, Stefan Esser [EMAIL PROTECTED] wrote: Following up to my own mail: Seems that translate.c is built from other directories as well, not just from within OSmesa. See the following patch, which is files/patch-GL_mesa_src_Imakefile on my system: --- lib/GL/mesa/src/Imakefile.orig Wed May 2 17:06:02 2001 +++ lib/GL/mesa/src/Imakefile Fri Jun 21 15:49:39 2002 @@ -51,6 +51,13 @@ #include Library.tmpl +#if defined(__GNUC__) __GNUC__ = 3 +#define ObjectCompile(options) RemoveFile($@) @@\ + ClearmakeOSName \ + $(CC) -c $(CFLAGS) options $*.c -o $@ || \ + $(CC) -c $(CFLAGS) options -O0 $*.c -o $@ +#endif + LibraryObjectRule() SubdirLibraryRule($(OBJS)) Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On 2002-06-21 16:35 +0200, Martin Blapp [EMAIL PROTECTED] wrote: I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. Sorry, but the compiler bug has been present in the port version of GCC-3.1 as well, a few weeks ago, and existed in the version to become GCC-3.1.1 ... I opened a PR at gcc.org, didn't get any feedback, yet. Why mess around with a buggy compiler if a working one is around ? Only a single source file triggers the optimizer bug, and the work-around should be appropriate until the compiler is fixed, IMHO. Why don't we update the pre 3.1 gcc in CURRENT to a working one ? I'm sure that there is a lot of work being done to keep up with the latest gcc versions. It just isn't that simple to upgrade such a crucial build tool (if compiling a new gcc fails, then make world doesn't have much of a chance of succeeding ...) Yes, I turned on -O and O2 again ;-) Did the GCC-3.1 from ports compile translate.c with optimization turned on ??? It didn't, just one or two weeks ago. Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Hi Stefan, Did the GCC-3.1 from ports compile translate.c with optimization turned on ??? It didn't, just one or two weeks ago. GCC3.1.1 Prerelease. Yes it did. I removed the patch andd added -O and -O2 again. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Hi, make CC=gcc31 CXX=g++31 clean install This currently doesn't work with the Xfree86 ports. CC is hardcoded there. Could the maintainer please fix this ? I also had to fix OO to work with this. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
XFree86-4-libraries build problem on -current
i can't install XFree86-4-libraries using -current cvsupped and copmiled a day ago. it builds fine, but the installations fails with the following diags: 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 *** Error code 1 Stop in /garbage/ports/x11/XFree86-4-libraries/work/xc/lib/GL/mesa/src/OSmesa. *** Error code 1 Stop in /garbage/ports/x11/XFree86-4-libraries/work/xc/lib/GL. *** Error code 1 Stop in /garbage/ports/x11/XFree86-4-libraries/work/xc/lib. *** Error code 1 Stop in /garbage/ports/x11/XFree86-4-libraries/work/xc. *** Error code 1 Stop in /garbage/ports/x11/XFree86-4-libraries/work/xc. *** Error code 1 Stop in /garbage/ports/x11/XFree86-4-libraries. *** Error code 1 i have seen an 'unofficial' patch announce (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=7709+0+current/freebsd-current), but i couldn't find the exact fix. could you please re-post it or commit necessary changes right into the port? thanks in advance. -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Kris Kennaway [EMAIL PROTECTED] wrote: I got around this problem by (indirectly) fixing the .c.o rule in the Imakefile. This patch was part of my previous mail to you regarding the XFree86 library build process (new version of patch-z32). Thanks for looking into this; I'd appreciate it if someone could commit a fix, but the patch below is suboptimal because it affects all versions of FreeBSD. Can you modify it so it only disables optimization on (recent) 5.0? Here is one example of new ports/x11/XFree86-4-libraries/files/patch-z32c. -- Motoyuki Konno [EMAIL PROTECTED] (Home) [EMAIL PROTECTED] (FreeBSD Project) http://www.freebsd.org/~motoyuki/ (WWW) -- --- lib/GL/mesa/src/OSmesa/Imakefile.orig Tue Jun 5 05:43:30 2001 +++ lib/GL/mesa/src/OSmesa/ImakefileFri Jun 21 18:21:25 2002 @@ -8,6 +8,19 @@ #define DoDebugLib DebugLibGlx #define DoProfileLib ProfileLibGlx +#if defined(FreeBSDArchitecture) (OSMajorVersion = 5) + +#define LibObjCompile(dir,options) RemoveFiles($@ $(@:C!([^/]+)$!dir/\1!)) @@\ + ClearmakeOSName \ + $(CC) -c $(CCOPTIONS) $(THREADS_CFLAGS) $(ALLDEFINES) \ + options $*.c -o $(@:C!([^/]+)$!dir/\1!) + +#define ObjectCompile(options) RemoveFile($@) @@\ + ClearmakeOSName \ + $(CC) -c $(CFLAGS) options -O0 $*.c -o $@ + +#endif + #include ../Imakefile.inc #ifdef i386Architecture #include ../X86/Imakefile.inc @@ -58,7 +71,7 @@ LIBNAME = OSMesa SOREV = 3.3 - +#if !defined(LibInstall) || LibInstall || (!defined(ModInstall) || ModInstall) #if DoNormalLib NormalLibraryTarget($(LIBNAME), $(UOBJS)) InstallLibrary($(LIBNAME),$(USRLIBDIR)) @@ -77,6 +90,7 @@ #if DoProfileLib ProfiledLibraryTarget($(LIBNAME), $(POBJS)) InstallLibrary($(LIBNAME)_p,$(USRLIBDIR)) +#endif #endif DependTarget()
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On 2002-06-16 02:39 -0700, Kris Kennaway [EMAIL PROTECTED] wrote: On Sat, Jun 08, 2002 at 11:29:26AM +0200, Stefan Esser wrote: I got around this problem by (indirectly) fixing the .c.o rule in the Imakefile. This patch was part of my previous mail to you regarding the XFree86 library build process (new version of patch-z32). Thanks for looking into this; I'd appreciate it if someone could commit a fix, but the patch below is suboptimal because it affects all versions of FreeBSD. Can you modify it so it only disables optimization on (recent) 5.0? File: /usr/ports/x11/XFree86-4-libraries/files/patch-z32 --- lib/GL/mesa/src/OSmesa/Imakefile.orig Tue Apr 3 11:29:33 2001 +++ lib/GL/mesa/src/OSmesa/ImakefileWed Jun 5 12:28:26 2002 Ok, here is an improved patch: 1) I've made the redefinition of the compiler command dependent on __GCC__ = 3. 2) The actual rule that is generated for GCC-3.x is now of the form cc -O ... || cc -O0 ... That way, only those files that could not be compiled with optimization enabled are tried again without optimization: #if defined(__GNUC__) __GNUC__ = 3 #define ObjectCompile(options) RemoveFile($@) @@\ ClearmakeOSName \ $(CC) -c $(CFLAGS) options $*.c -o $@ || \ $(CC) -c $(CFLAGS) options -O0 $*.c -o $@ #endif The GCC bug is triggered building XFree86-4-libraries and XFree86-4-Server. I include uni-diffs for patch patch-z32 to fix the former, and a new patch-OSmesa-Imake for the latter (both to be applied from /usr/ports/). I'm currently rebuilding both the libraries and server ports with those patches, but it will take some time on my ancient system at home (still a Celeron 300A ...). Regards, STefan RCS file: /usr/cvs/ports/x11/XFree86-4-libraries/files/patch-z32,v retrieving revision 1.3 diff -u -3 -r1.3 patch-z32 --- x11/XFree86-4-libraries/files/patch-z32 12 Jun 2001 14:59:51 - 1.3 +++ x11/XFree86-4-libraries/files/patch-z32 21 Jun 2002 12:04:17 - @@ -1,5 +1,24 @@ --- lib/GL/mesa/src/OSmesa/Imakefile.orig Tue Apr 3 11:29:33 2001 -+++ lib/GL/mesa/src/OSmesa/Imakefile Thu Jun 7 02:58:09 2001 lib/GL/mesa/src/OSmesa/Imakefile Fri Jun 21 13:55:44 2002 +@@ -8,6 +8,18 @@ + #define DoDebugLib DebugLibGlx + #define DoProfileLib ProfileLibGlx + ++#define LibObjCompile(dir,options) RemoveFiles($@ $(@:C!([^/]+)$!dir/\1!))@@\ ++ ClearmakeOSName \ ++ $(CC) -c $(CCOPTIONS) $(THREADS_CFLAGS) $(ALLDEFINES) \ ++ options $*.c -o $(@:C!([^/]+)$!dir/\1!) ++ ++#if defined(__GNUC__) __GNUC__ = 3 ++#define ObjectCompile(options) RemoveFile($@) @@\ ++ ClearmakeOSName \ ++ $(CC) -c $(CFLAGS) options $*.c -o $@ || \ ++ $(CC) -c $(CFLAGS) options -O0 $*.c -o $@ ++#endif ++ + #include ../Imakefile.inc + #ifdef i386Architecture + #include ../X86/Imakefile.inc @@ -58,7 +58,7 @@ LIBNAME = OSMesa SOREV = 3.3 --- /dev/null Fri Jun 21 14:14:52 2002 +++ x11-servers/XFree86-4-Server/files/patch-OSmesa-Imakefile Fri Jun 21 13:59:36 +2002 @@ -0,0 +1,16 @@ +--- lib/GL/mesa/src/OSmesa/Imakefile.orig Fri Jun 21 11:23:42 2002 lib/GL/mesa/src/OSmesa/Imakefile Fri Jun 21 13:55:44 2002 +@@ -8,6 +8,13 @@ + #define DoDebugLib DebugLibGlx + #define DoProfileLib ProfileLibGlx + ++#if defined(__GNUC__) __GNUC__ = 3 ++#define ObjectCompile(options) RemoveFile($@) @@\ ++ ClearmakeOSName \ ++ $(CC) -c $(CFLAGS) options $*.c -o $@ || \ ++ $(CC) -c $(CFLAGS) options -O0 $*.c -o $@ ++#endif ++ + #include ../Imakefile.inc + #ifdef i386Architecture + #include ../X86/Imakefile.inc
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Hi, I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. Why mess around with a buggy compiler if a working one is around ? Why don't we update the pre 3.1 gcc in CURRENT to a working one ? Yes, I turned on -O and O2 again ;-) Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Fri, Jun 21, 2002 at 02:33:51PM +0200, Stefan Esser wrote: #if defined(__GNUC__) __GNUC__ = 3 #define ObjectCompile(options) RemoveFile($@) @@\ ClearmakeOSName \ $(CC) -c $(CFLAGS) options $*.c -o $@ || \ $(CC) -c $(CFLAGS) options -O0 $*.c -o $@ #endif It would be better to use __FreeBSD_cc_version=53 as I believe the problem only exists with the system gcc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Fri, Jun 21, 2002 at 04:35:47PM +0200, Martin Blapp wrote: I still wonder why we make workarounds like this if one could just use /usr/local/bin/gcc31 to have it fixed. Why mess around with a buggy compiler if a working one is around ? Why don't we update the pre 3.1 gcc in CURRENT to a working one ? You are free to do so. I won't stop you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Sat, Jun 08, 2002 at 11:29:26AM +0200, Stefan Esser wrote: I got around this problem by (indirectly) fixing the .c.o rule in the Imakefile. This patch was part of my previous mail to you regarding the XFree86 library build process (new version of patch-z32). Thanks for looking into this; I'd appreciate it if someone could commit a fix, but the patch below is suboptimal because it affects all versions of FreeBSD. Can you modify it so it only disables optimization on (recent) 5.0? File: /usr/ports/x11/XFree86-4-libraries/files/patch-z32 --- lib/GL/mesa/src/OSmesa/Imakefile.orig Tue Apr 3 11:29:33 2001 +++ lib/GL/mesa/src/OSmesa/Imakefile Wed Jun 5 12:28:26 2002 [...] Kris msg39688/pgp0.pgp Description: PGP signature
Re: More X breakage in XFree86-4-Servers ...
Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 Stop in /usr/local/ports/usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src. *** Error code 1 I'm getting this as well. -- 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: More X breakage in XFree86-4-Servers ...
On Sat, Jun 15, 2002 at 01:39:08PM -0500, David W. Chapman Jr. wrote: Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 Stop in /usr/local/ports/usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src. *** Error code 1 I'm getting this as well. Has anyone actually submitted a bug report to GCC yet? Kris msg39666/pgp0.pgp Description: PGP signature
Re: More X breakage in XFree86-4-Servers ...
Has anyone actually submitted a bug report to GCC yet? I don't believe so. I'm not sure exactly what is broken or the circumstances that cause the problem. My lack of c knowledge is preventing me from saying much more than X-Servers won't build. Would you be willing to help me figure out what is going on so I can file a proper report or were you offering to file it? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Mon, Jun 10, 2002 at 09:18:32PM +0200, Szilveszter Adam wrote: Sorry David, but I experienced the same thing. No matter if I used the base system c++ compiler, or the latest gcc31 port. The problem is all the more interesting, because X worked for me fine, no matter what compiler I used to build it (with a few patches from the XFree86-4-libraries port) and libGLU is the only part of XFree that is wirtten in C++. If I specify -lstdc++ on the link line of any programs that use libGLU, it works (see xc/programs/glxinfo). My -CURRENT is from Saturday (8th), NO_CXX is *not* set. me too. current from sunday, and i had to link libstdc++ manually to it, for it to work. after that - no probs -tacho To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Mon, Jun 10, 2002 at 12:02:41PM -0500, Michael D. Harnois wrote: The libraries build for me without incident. However, anything which tries to link against libGLU generates this error for me: Your current is too old. Please do a fresh build. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Mon, Jun 10, 2002 at 12:15:40PM -0500, Michael D. Harnois wrote: On Mon, 2002-06-10 at 12:13, David O'Brien wrote: On Mon, Jun 10, 2002 at 12:02:41PM -0500, Michael D. Harnois wrote: The libraries build for me without incident. However, anything which tries to link against libGLU generates this error for me: Your current is too old. Please do a fresh build. Since 6:30 last night? You must have NO_CXX or something -- you aren't linking with the C++ support libs for some reason. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Mon, Jun 10, 2002 at 10:26:36AM -0700, David O'Brien wrote: On Mon, Jun 10, 2002 at 12:15:40PM -0500, Michael D. Harnois wrote: On Mon, 2002-06-10 at 12:13, David O'Brien wrote: On Mon, Jun 10, 2002 at 12:02:41PM -0500, Michael D. Harnois wrote: The libraries build for me without incident. However, anything which tries to link against libGLU generates this error for me: Your current is too old. Please do a fresh build. Since 6:30 last night? You must have NO_CXX or something -- you aren't linking with the C++ support libs for some reason. Sorry David, but I experienced the same thing. No matter if I used the base system c++ compiler, or the latest gcc31 port. The problem is all the more interesting, because X worked for me fine, no matter what compiler I used to build it (with a few patches from the XFree86-4-libraries port) and libGLU is the only part of XFree that is wirtten in C++. If I specify -lstdc++ on the link line of any programs that use libGLU, it works (see xc/programs/glxinfo). My -CURRENT is from Saturday (8th), NO_CXX is *not* set. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Sat, Jun 08, 2002 at 10:11:13PM +0900, Yamada Ken Takeshi wrote:
Thank you! Your patch-z32 made me happy a little.
When can I compile XFree86-4-Server-4.2.0_2 with -current?
It gives me internal compiler error, too as below. I had
thought it uses XFree86-4-libraries port which was wrong.
The build in XFree86-Server has -O -pipe on the commandline, which I
presume you have in /etc/make.conf. The one in XFree86-Libraries didn't
(as demonstrated by your earlier mail). Hence the first didn't hit the
compiler bug and this one does. The work-around: build this file without
-O.
::: (snip)
rm -f translate.o
LD_LIBRARY_PATH=../../../../exports/lib cc -c -O -pipe-ansi -pedantic
-Dasm=__asm -Wall -Wpointer-arith -I../../../../exports/include
-I../../../../exports/include/X11 -I../../../../include/extensions
-I../../../../extras/Mesa/src -I../../../../lib/GL/dri -I../../../..
-I../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS
-DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI
-DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA-DUSE_X86_ASM
-DUSE_MMX_ASM -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith
-I../../../../exports/include -I../../../../exports/include/X11
-I../../../../include/extensions -I../../../../extras/Mesa/src
-I../../../../lib/GL/dri -I../../../.. -I../../../../exports/include -DCSRG_BASED
-DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI
-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN
-DGLX_USE_MES!
A-DUSE_X86_ASM -DUSE_MMX_ASM-fPIC translate.c
In file included from translate.c:779:
../../../../extras/Mesa/src/trans_tmp.h: In function `trans_1_GLdouble_1ub_elt':
../../../../extras/Mesa/src/trans_tmp.h:124: could not find a spill register
(insn 96 94 97 (set (subreg:SF (reg:QI 75) 0)
(plus:SF (reg:SF 8 st(0) [76])
(reg:SF 9 st(1) [80]))) 525 {*fop_sf_comm_nosse} (insn_list 87 (nil))
(expr_list:REG_DEAD (reg:SF 8 st(0) [76])
(nil)))
../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in
failed_reload, at reload1.c:5050
Please submit a full bug report,
with preprocessed source if appropriate.
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Sat, Jun 08, 2002 at 05:13:12PM +0900, Yamada Ken Takeshi wrote: I have the following error when I try to install it. Is it unique only to me? I didn't get that when I built it on ref5. That's the only place I've tried it. Kris msg39367/pgp0.pgp Description: PGP signature
Re: Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On 2002-06-08 01:39 -0700, Kris Kennaway [EMAIL PROTECTED] wrote: On Sat, Jun 08, 2002 at 05:13:12PM +0900, Yamada Ken Takeshi wrote: I have the following error when I try to install it. Is it unique only to me? I didn't get that when I built it on ref5. That's the only place I've tried it. I got around this problem by (indirectly) fixing the .c.o rule in the Imakefile. This patch was part of my previous mail to you regarding the XFree86 library build process (new version of patch-z32). The problem is that unshared is meant to be a prefix to a file name, but $@ happens to be a path name including directory components. E.g. $@ = dir/file.o = unshared/dir/file.o The correct path is dir/unshared/file.o and the modified definition of LibObjCompile uses that filename: File: /usr/ports/x11/XFree86-4-libraries/files/patch-z32 --- lib/GL/mesa/src/OSmesa/Imakefile.orig Tue Apr 3 11:29:33 2001 +++ lib/GL/mesa/src/OSmesa/ImakefileWed Jun 5 12:28:26 2002 @@ -8,6 +8,16 @@ #define DoDebugLib DebugLibGlx #define DoProfileLib ProfileLibGlx +#define LibObjCompile(dir,options) RemoveFiles($@ $(@:C!([^/]+)$!dir/\1!)) @@\ + ClearmakeOSName \ + $(CC) -c $(CCOPTIONS) $(THREADS_CFLAGS) $(ALLDEFINES) \ + options $*.c -o $(@:C!([^/]+)$!dir/\1!) + +#define ObjectCompile(options) RemoveFile($@) @@\ + ClearmakeOSName \ + $(CC) -c $(CFLAGS) options -O0 $*.c -o $@ + + #include ../Imakefile.inc #ifdef i386Architecture #include ../X86/Imakefile.inc @@ -58,7 +68,7 @@ LIBNAME = OSMesa SOREV = 3.3 - +#if !defined(LibInstall) || LibInstall || (!defined(ModInstall) || ModInstall) #if DoNormalLib NormalLibraryTarget($(LIBNAME), $(UOBJS)) InstallLibrary($(LIBNAME),$(USRLIBDIR)) @@ -77,6 +87,7 @@ #if DoProfileLib ProfiledLibraryTarget($(LIBNAME), $(POBJS)) InstallLibrary($(LIBNAME)_p,$(USRLIBDIR)) +#endif #endif DependTarget() (The redefinition of ObjectCompile() disables optimization because it triggers an internal bug in gcc-3.1 in the case of the PCI object.) Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Sat, Jun 08, 2002 at 10:11:13PM +0900, Yamada Ken Takeshi wrote: snip/ (expr_list:REG_DEAD (reg:SF 8 st(0) [76]) (nil))) ../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in failed_reload, at reload1.c:5050 Please submit a full bug report, with preprocessed source if appropriate. interesting enough, if you compile that file WITHOUT optimizations, everything works fine. -tacho To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
More X breakage in XFree86-4-Servers ...
BRARY_PATH=../../../../exports/lib cc -c -O -pipe -D_OLD_STDIO -ansi -pedantic
-Dasm=__asm -Wall -Wpointer-arith -I../../../../exports/include
-I../../../../exports/include/X11 -I../../../../include/extensions
-I../../../../extras/Mesa/src -I../../../../lib/GL/dri -I../../../..
-I../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS
-DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI
-DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA-DUSE_X86_ASM
-DUSE_MMX_ASM -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith
-I../../../../exports/include -I../../../../exports/include/X11
-I../../../../include/extensions -I../../../../extras/Mesa/src
-I../../../../lib/GL/dri -I../../../.. -I../../../../exports/include -DCSRG_BASED
-DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI
-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_REND
ERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -DUSE_X86_ASM -DUSE_MMX_ASM-fPIC
translate.c
In file included from translate.c:779:
../../../../extras/Mesa/src/trans_tmp.h: In function `trans_1_GLdouble_1ub_elt':
../../../../extras/Mesa/src/trans_tmp.h:124: could not find a spill register
(insn 96 94 97 (set (subreg:SF (reg:QI 75) 0)
(plus:SF (reg:SF 8 st(0) [76])
(reg:SF 9 st(1) [80]))) 525 {*fop_sf_comm_nosse} (insn_list 87 (nil))
(expr_list:REG_DEAD (reg:SF 8 st(0) [76])
(nil)))
../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in failed_reload,
at reload1.c:5050
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
*** Error code 1
Stop in
/usr/local/ports/usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src.
*** Error code 1
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Tue, Jun 04, 2002 at 09:43:59PM +0900, Motoyuki Konno wrote: Please try the following patch. Thanks, this fixed the XFree86-4-libraries build. I've committed the patch. Kris msg39291/pgp0.pgp Description: PGP signature
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Hi, Michael D. Harnois [EMAIL PROTECTED] wrote: if __GNUC__ = 3 int foo() __attribute__ ((weak, alias (bar))); #endif /* __GNUC__ */ . I tried the quotation mark fix, and all it does is change the error message to UIThrStubs.c:102: warning: malformed #pragma weak, ignored [snip] UIThrStubs.c:139: warning: `_Xthr_zero_stub_' defined but not used which doesn't really seem to be a solution. Please try the following patch. -- Motoyuki Konno [EMAIL PROTECTED] (Home) [EMAIL PROTECTED] (FreeBSD Project) http://www.freebsd.org/~motoyuki/ (WWW) --- lib/XThrStub/UIThrStubs.c.old Mon Nov 19 06:13:26 2001 +++ lib/XThrStub/UIThrStubs.c Tue Jun 4 11:39:19 2002 @@ -99,6 +99,21 @@ #else #include pthread.h typedef pthread_t xthread_t; +#if __GNUC__ = 3 +xthread_t pthread_self()__attribute__ ((weak, alias (_Xthr_self_stub_))); +int pthread_mutex_init()__attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_mutex_destroy() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_mutex_lock()__attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_mutex_unlock() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_cond_init() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_cond_destroy() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_cond_wait() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_cond_signal() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_cond_broadcast() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_key_create()__attribute__ ((weak, alias (_Xthr_zero_stub_))); +void *pthread_getspecific() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +int pthread_setspecific() __attribute__ ((weak, alias (_Xthr_zero_stub_))); +#else /* __GNUC__ */ #pragma weak pthread_self = _Xthr_self_stub_ #pragma weak pthread_mutex_init = _Xthr_zero_stub_ #pragma weak pthread_mutex_destroy = _Xthr_zero_stub_ @@ -113,6 +128,7 @@ #pragma weak pthread_key_create = _Xthr_zero_stub_ #pragma weak pthread_getspecific = _Xthr_zero_stub_ #pragma weak pthread_setspecific = _Xthr_zero_stub_ +#endif /* __GNUC__ */ #if defined(_DECTHREADS_) || defined(linux) #pragma weak pthread_equal = _Xthr_equal_stub_ /* See Xthreads.h! */ int
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Tue, Jun 04, 2002 at 07:08:32AM -0500, Michael D. Harnois wrote: #pragma weak foo = bar with either #pragma weak foo = bar /* this is easier */ snip/ I tried the quotation mark fix, and all it does is change the error message to UIThrStubs.c:102: warning: malformed #pragma weak, ignored snip/ which doesn't really seem to be a solution. are you sure that you're with the right gcc? mine compiles this fine. but regardless which one I use (__attribute__ or the quotation), later on the process i get the internal compiler error in Mesa. not that I think the two are related, though. -tacho -- [a lie is my shield] | [http://daemonz.org/ || [EMAIL PROTECTED]] 0x44fc3339 || [02b5 798b 4bd1 97fb f8db 72e4 dca4 be03 44fc 3339] msg39153/pgp0.pgp Description: PGP signature
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Tue, 4 Jun 2002, Stanislav Grozev wrote: On Tue, Jun 04, 2002 at 07:08:32AM -0500, Michael D. Harnois wrote: #pragma weak foo = bar with either #pragma weak foo = bar /* this is easier */ snip/ I tried the quotation mark fix, and all it does is change the error message to UIThrStubs.c:102: warning: malformed #pragma weak, ignored snip/ which doesn't really seem to be a solution. are you sure that you're with the right gcc? mine compiles this fine. but regardless which one I use (__attribute__ or the quotation), later on the process i get the internal compiler error in Mesa. not that I think the two are related, though. I tried here too, latest GCC in 5.0-CURRENT from this weekend, and get the same 'ignored' stuff, after which it does continue onto the Mesa where it does fail ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
Hello, For what it's worth, I set out and successfully compiled the latest from the XFree86 CVS with the latest gcc31 snapshot (May 27th). I needed to do the following: - I had to apply the fix that has been mentioned several times on this list to libXThrStub. - I had to fix a typo in one header file under xc/programs/Xserver/PEX5/ddpex/mi/include/miStruct.h in a prperocessor statement - I applied the patch-ioctl from ports/x11/XFree86-4-libraries (alternatively, you could disable the drm part), also I applied the patch-startx from the same place because I wanted consistent behaviour of startx from what I was used to. There was (after these) a bunch of problems that I worked around with hacks: - There was one file, xc/lib/X11/lcUTF8.c which the gcc from ports did not like. It produced an internal compiler error like this: LD_LIBRARY_PATH=../../exports/lib /usr/local/bin/gcc31 -c -ansi -pedantic -Dasm= __asm -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-d eclarations -Wredundant-decls -Wnested-externs -Wundef -pthread -I../.. -I../. ./exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_RE ENTRANT -D_THREAD_SAFE -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI -DMALLOC_0_RETUR NS_NULL -DHAS_SNPRINTF -DLIBX11 -O -pipe -march=pentiumpro lcUTF8.c -o unshared/lcUTF8.o lcUTF8.c: In function `charset_wctocs': lcUTF8.c:582: unrecognizable insn: (insn 251 70 252 (set (reg:CC 17 flags) (compare:CC (mem:QI (reg/v/f:SI 63) [0 S1 A8]) (const_int 128 [0x80]))) -1 (nil) (expr_list:REG_DEAD (reg/v/f:SI 63) (nil))) lcUTF8.c:582: Internal compiler error in extract_insn, at recog.c:2132 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 (continuing) (Sorry for cutpaste) However, when I compiled this only one file with the base system gcc, it worked and linked. - In xc/programs/glxinfo/Makefile, I had to manually define the path to the libstdc++.a in /usr/local/lib/gcc-lib/i386-portbld-freebsd5.0/3.1.1/ because otherwise it was not found. (I suspect this is because it uses the gcc31 frontend, not g++31.) After this, I now have a new X that appears to work at first sight. I somehow managed to mess it up though because now it seems to ignore the Xwrapper port although I have it installed and so only works if I make the X server suid root. But it is probably me... Also, stability remains to be seen, since the original reason for upgrading was that 4.2.0 was regularly freezing with my Virge GX2 card, and supposedly some fixes were prepared for this problem... we'll see. This is just an FYI for all having problems with X building now. Note: I did not try the base system compiler for building yet, apart from that quick hack indicated above. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
GCC3.1 internal compiler error when compiling XFree86-4-libraries
Hello,
I have a -CURRENT system (world from yesterday, ports from today).
I'm trying to compile the XFree86-libraries-4.2.0 from ports, but
I have troubles. After resolving the one with the #pragma weak,
and also one with a missing ../ from one of the Mesa Makefiles,
now I get the following:
-
LD_LIBRARY_PATH=../../../../../exports/lib cc -c -O -pipe -Wp,-w -march=pentium -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 -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
-fPIC ../../../../../lib/GL/mesa/src/translate.c
In file included from ../../../../../lib/GL/mesa/src/translate.c:779:
../../../../../extras/Mesa/src/trans_tmp.h: In function `trans_1_GLdouble_1ub_elt':
../../../../../extras/Mesa/src/trans_tmp.h:124: could not find a spill register
(insn 96 94 97 (set (subreg:SF (reg:QI 75) 0)
(plus:SF (reg:SF 8 st(0) [76])
(reg:SF 9 st(1) [80]))) 525 {*fop_sf_comm_nosse} (insn_list 87
(nil))
(expr_list:REG_DEAD (reg:SF 8 st(0) [76])
(nil)))
../../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in
failed_reload, at reload1.c:5050
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
*** Error code 1
Stop in /home/scratch/ports/x11/XFree86-4-libraries/work/xc/lib/GL/mesa/src/OSmesa.
logrus#
-
I don't have any idea what to do to fix it. Any help would be appreciated.
If any further info, or details, or testing are needed, I'll be glad
to provide it. Thanks.
-tacho
--
[a lie is my shield] | [http://daemonz.org/ || [EMAIL PROTECTED]]
0x44fc3339 || [02b5 798b 4bd1 97fb f8db 72e4 dca4 be03 44fc 3339]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
stupid question, but what is the fix for the #pragma weak issue? :(
On Mon, 3 Jun 2002, Stanislav Grozev wrote:
Hello,
I have a -CURRENT system (world from yesterday, ports from today).
I'm trying to compile the XFree86-libraries-4.2.0 from ports, but
I have troubles. After resolving the one with the #pragma weak,
and also one with a missing ../ from one of the Mesa Makefiles,
now I get the following:
-
LD_LIBRARY_PATH=../../../../../exports/lib cc -c -O -pipe -Wp,-w -march=pentium
-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
-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
-fPIC ../../../../../lib/GL/mesa/src/translate.c
In file included from ../../../../../lib/GL/mesa/src/translate.c:779:
../../../../../extras/Mesa/src/trans_tmp.h: In function `trans_1_GLdouble_1ub_elt':
../../../../../extras/Mesa/src/trans_tmp.h:124: could not find a spill register
(insn 96 94 97 (set (subreg:SF (reg:QI 75) 0)
(plus:SF (reg:SF 8 st(0) [76])
(reg:SF 9 st(1) [80]))) 525 {*fop_sf_comm_nosse} (insn_list 87
(nil))
(expr_list:REG_DEAD (reg:SF 8 st(0) [76])
(nil)))
../../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in
failed_reload, at reload1.c:5050
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
*** Error code 1
Stop in /home/scratch/ports/x11/XFree86-4-libraries/work/xc/lib/GL/mesa/src/OSmesa.
logrus#
-
I don't have any idea what to do to fix it. Any help would be appreciated.
If any further info, or details, or testing are needed, I'll be glad
to provide it. Thanks.
-tacho
--
[a lie is my shield] | [http://daemonz.org/ || [EMAIL PROTECTED]]
0x44fc3339 || [02b5 798b 4bd1 97fb f8db 72e4 dca4 be03 44fc 3339]
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: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote: stupid question, but what is the fix for the #pragma weak issue? :( you replace #pragma weak foo = bar with either #pragma weak foo = bar /* this is easier */ or if __GNUC__ = 3 int foo() __attribute__ ((weak, alias (bar))); #endif /* __GNUC__ */ . :-) but that only gets you to the Mesa mess;-( -tacho To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
On Mon, Jun 03, 2002 at 05:06:23PM +0200, Stanislav Grozev wrote: On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote: stupid question, but what is the fix for the #pragma weak issue? :( you replace #pragma weak foo = bar with either #pragma weak foo = bar /* this is easier */ or if __GNUC__ = 3 err, i meant #if, not if. :-) mondays... int foo() __attribute__ ((weak, alias (bar))); #endif /* __GNUC__ */ . :-) -tacho To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries
has any of this been reported to the XFree86 folk? I just CVSup'd the latest XFree86 source code and this #pragma condition appears to still exist :( On Mon, 3 Jun 2002, Stanislav Grozev wrote: On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote: stupid question, but what is the fix for the #pragma weak issue? :( you replace #pragma weak foo = bar with either #pragma weak foo = bar /* this is easier */ or if __GNUC__ = 3 int foo() __attribute__ ((weak, alias (bar))); #endif /* __GNUC__ */ . :-) but that only gets you to the Mesa mess;-( -tacho To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
XFree86-4-libraries compile fails in UIThrStubs.c ... GCC 3.1 issue?
I'm running 5.0-CURRENT, with gcc 3.1: mobile# gcc -v Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.1 [FreeBSD] 20020509 (prerelease) Is this an issue with GCC 3.1, or something else I'm not thinking of ... ? -- Line102: #pragma weak pthread_self = _Xthr_self_stub_ rm -f UIThrStubs.o LD_LIBRARY_PATH=../../exports/lib cc -c -O -pipe -D_OLD_STDIO -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI -DMALLOC_0_RETURNS_NULL-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -fPIC 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/local/ports/usr/ports/x11/XFree86-4-libraries/work/xc/lib/XThrStub. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
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
XFree86-4-libraries build error
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
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: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
Fluid [EMAIL PROTECTED] wrote: How about signal 4? I was rebuilding my -current the other day and I kept getting mostly signal 4 errors (in different places) with a couple of signal 10's and 11's. I tried finding a run-down of what the various errors meant, but I couldn't find a thing. The signal number mapping is in /usr/include/sys/signal.h. [ Um, if you don't know what the signals mean, you might not want to be running -current. ] SIGILL (signal 4) is usually not good (e.g., bad RAM, IDE data corruption, etc.). The weird thing is that when I switched terminals in KDE (i.e. opened a new Konsole window), my build problems ceased. Possible bad RAM: the new window allocated enough memory such that a bad spot in memory was allocated to the new Konsole's process, and not randomly to the build processes. Windows XP runs on the same box with no problems (i.e. will run for weeks without a reboot) so I'm a little hesitant to blame my hardware. This doesn't necessarily mean much. Windows will either not stress the hardware as much, or will use RAM in different ways. I seem to recall hearing rumors that Windows allocates memory from the top down. If so, and if FreeBSD allocates memory from the bottom up (I don't know), that could explain why you do not appear to be seeing the problem under xp. However, as other people are having mysterious problems with -current, it could be a software problem. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
On Tue, Apr 30, 2002 at 06:24:14PM -0400, Forrest Aldrich wrote: I've experienced this same problem today; but only after installing 5.0-current on the system in question. It compiled fine with FreeBSD_4.5. This is a 1.2ghz Pentium with 1gb of RAM. No problems with other things (large compile projects with 4.5 before). I have been building XFree86 without problems, until I updated my -CURRENT system (I did the previous update three months ago). I don't think that this is a hardware related problem. My -CURRENT system is running on an 800 MHz Duron (KT133 chipset), and performs flawlessly otherwise, including large builds such as make worlds. The kernel has all debugging options removed, and the malloc.conf options are aj. -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
On Wed, 1 May 2002 13:32:35 +0200, Jose M. Alcaide [EMAIL PROTECTED] said: I have been building XFree86 without problems, I just rebuilt both -current (Friday or Saturday timeframe) and all of X (last night) without a problem. (Well, other than all of the old binaries I need to recompile now...) -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
On Tue, 2002-04-30 at 10:35, Ian wrote: cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 I have seen cc1 die like this many many times, and have only ever seen 2 root causes for the death: 1) bad ram 2) you overclocked the cpu or bus just a bit too much How about signal 4? I was rebuilding my -current the other day and I kept getting mostly signal 4 errors (in different places) with a couple of signal 10's and 11's. I tried finding a run-down of what the various errors meant, but I couldn't find a thing. The weird thing is that when I switched terminals in KDE (i.e. opened a new Konsole window), my build problems ceased. Windows XP runs on the same box with no problems (i.e. will run for weeks without a reboot) so I'm a little hesitant to blame my hardware. -Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
I am getting this error while building XFree86-Server-4.2.0_2 on a recently updated -CURRENT (Mon Apr 29 10:55:43 GMT): LD_LIBRARY_PATH=../../../../../../exports/lib cc -c -O -pipe-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../../../../../../exports/include/X11 -I../../../../../../include/extensions -I../../../../../../extras/Mesa/src -I../../../../../../lib/GL/mesa/src/drv/common -I../../../../../../lib/GL/mesa/src/drv/i810 -I../../../../../../lib/GL/dri -I../../../../../../lib/GL/glx -I../../../../../../exports/include -I../../../../../../exports/include/GL -I../../../../../../lib/GL/mesa/dri -I../../../../../../programs/Xserver/GL/dri -I../../../../../../programs/Xserver/hw/xfree86/os-support -I../../../../../../programs/Xserver/hw/xfree86/drivers/i810 -I../../../../../../lib/GL/dri/drm -I../../../../../.. -I../../../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -DUSE_X86_ASM -DUSE_MMX_ASM -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../../../../../../exports/include/X11 -I../../../../../../include/extensions -I../../../../../../extras/Mesa/src -I../../../../../../lib/GL/mesa/src/drv/common -I../../../../../../lib/GL/mesa/src/drv/i810 -I../../../../../../lib/GL/dri -I../../../../../../lib/GL/glx -I../../../../../../exports/include -I../../../../../../exports/include/GL -I../../../../../../lib/GL/mesa/dri -I../../../../../../programs/Xserver/GL/dri -I../../../../../../programs/Xserver/hw/xfree86/os-support -I../../../../../../programs/Xserver/hw/xfree86/drivers/i810 -I../../../../../../lib/GL/dri/drm -I../../../../../.. -I../../../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -DUSE_X86_ASM -DUSE_MMX_ASM -fPIC i810tris.c In file included from /usr/include/pthread.h:43, from ../../../../../../exports/include/X11/Xthreads.h:199, from ../../../../../../extras/Mesa/src/glthread.h:176, from ../../../../../../extras/Mesa/src/types.h:36, from i810tris.c:30: /usr/include/sys/time.h: In function `timespec2bintime': /usr/include/sys/time.h:154: warning: ANSI C forbids long long integer constants /usr/include/sys/time.h: In function `timeval2bintime': /usr/include/sys/time.h:172: warning: ANSI C forbids long long integer constants cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 This cc1 SIGBUS is triggered by different source files at different times. But it happens while building XFree86-Server sooner or later, and always with SIGBUS. I did not have problems building the rest of the XFree86-4 ports, or making the world, neither. I commented out CFLAGS (and also CPUTYPE) from /etc/make.conf, but it seems that the XFree86 build system uses -O -pipe anyway. Any ideas? Cheers, JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
On Tue, Apr 30, 2002 at 11:28:48AM +0200, Jose M. Alcaide wrote: cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 This cc1 SIGBUS is triggered by different source files at different times. But it happens while building XFree86-Server sooner or later, and always with SIGBUS. I did not have problems building the rest of the XFree86-4 ports, or making the world, neither. I commented out CFLAGS (and also CPUTYPE) from /etc/make.conf, but it seems that the XFree86 build system uses -O -pipe anyway. More info: removing -O and/or -pipe from CFLAGS does not improve the situation: cc1 keeps crashing at random places with SIGBUS while building XFree86-Server-4.2.0_2. I found a message from Kris Kennaway telling that this is a widely experienced problem: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1049089+1051787+/usr/local/www/db/text/2002/freebsd-current/20020310.freebsd-current However, disabling optimizations does not work for me. -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
From: Jose M. Alcaide [EMAIL PROTECTED] Date: Tue, 30 Apr 2002 11:28:48 +0200 To: [EMAIL PROTECTED] Subject: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 I am getting this error while building XFree86-Server-4.2.0_2 on a recently updated -CURRENT (Mon Apr 29 10:55:43 GMT): [snip] cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 I have seen cc1 die like this many many times, and have only ever seen 2 root causes for the death: 1) bad ram 2) you overclocked the cpu or bus just a bit too much cc1 dying on a long complex source module when you've overclocked beyond what your silicon can handle is so reliable a test that it's the first thing I use when trying to find the true speed a new system will run at. If you're not overclocking, then bad ram would make a good second suspect, I had a failing DIMM a couple years ago first manifest as signal 10 and 11 errors in cc1. -- Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
I've experienced this same problem today; but only after installing 5.0-current on the system in question. It compiled fine with FreeBSD_4.5. This is a 1.2ghz Pentium with 1gb of RAM. No problems with other things (large compile projects with 4.5 before). _F From: Jose M. Alcaide [EMAIL PROTECTED] Date: Tue, 30 Apr 2002 11:28:48 +0200 To: [EMAIL PROTECTED] Subject: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 I am getting this error while building XFree86-Server-4.2.0_2 on a recently updated -CURRENT (Mon Apr 29 10:55:43 GMT): [snip] cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 I have seen cc1 die like this many many times, and have only ever seen 2 root causes for the death: 1) bad ram 2) you overclocked the cpu or bus just a bit too much cc1 dying on a long complex source module when you've overclocked beyond what your silicon can handle is so reliable a test that it's the first thing I use when trying to find the true speed a new system will run at. If you're not overclocking, then bad ram would make a good second suspect, I had a failing DIMM a couple years ago first manifest as signal 10 and 11 errors in cc1. -- Ian 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: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
Found that cc1 also has a problem with this on a buildworld for FreeBSD-5.0-CURRENT. FYI. I can reinstall 4.5 and attempt the same, but I recall no problems with 4.5. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
To follow up on my previous post: I did reinstall FreeBSD-4.5 (updated with cvsup), did a buildworld etc., then build XFree86-4 with no troubles at all. So looks like the problem may be with FreeBSD-5.0-CURRENT. _F 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
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
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
Mouse in Xfree86 4.2.0
Hello When I start XFree86 I get the error that /dev/mouse can't be found, OK devfs seems to be installd so MAKEDEV dosn't exist anymore, is there anyway to get /dev/mouse working as in FreeBSD 4? Thanks /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mouse in Xfree86 4.2.0
On Mon, Apr 15, 2002 at 10:02:33AM +0200, John Angelmo wrote: Hello When I start XFree86 I get the error that /dev/mouse can't be found, OK devfs seems to be installd so MAKEDEV dosn't exist anymore, is there anyway to get /dev/mouse working as in FreeBSD 4? Thanks /John Set your mouse as being /dev/sysmouse in your XF86Config. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mouse in Xfree86 4.2.0
Whats about editing /etc/rc.devfs and inserting a symlink from /dev/mouse to /dev/sysmouse ? On Mon, 2002-04-15 at 08:26, Munish Chopra wrote: On Mon, Apr 15, 2002 at 10:02:33AM +0200, John Angelmo wrote: Hello When I start XFree86 I get the error that /dev/mouse can't be found, OK devfs seems to be installd so MAKEDEV dosn't exist anymore, is there anyway to get /dev/mouse working as in FreeBSD 4? Thanks /John Set your mouse as being /dev/sysmouse in your XF86Config. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org 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: Mouse in Xfree86 4.2.0
I had this similiar problem. Sysinstall - post configure and re-do your mouse. The only workaround I have found. /ges At 10:02 AM 4/15/2002 +0200, John Angelmo wrote: Hello When I start XFree86 I get the error that /dev/mouse can't be found, OK devfs seems to be installd so MAKEDEV dosn't exist anymore, is there anyway to get /dev/mouse working as in FreeBSD 4? Thanks /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: Mouse in Xfree86 4.2.0
--- Gary Stanley [EMAIL PROTECTED] wrote: Sysinstall - post configure and re-do your mouse. The only workaround I have found. The other way, is to edit your XF86Config to point to /dev/pcm0 (if you are using a PS2 mouse), or /dev/sioN (N being the COM port number), which gives XFree86 direct access to your mouse. But remember, if you do this, you will need to disable the moused from Sysinstall. When I start XFree86 I get the error that /dev/mouse can't be found, OK devfs seems to be installd so MAKEDEV dosn't exist anymore, is there anyway to get /dev/mouse working as in FreeBSD 4? Technically the MAKEDEV script still exists in src/etc/MAKEDEV*, but it is only copied to /dev if you have disabled the DEVFS k-option, afaik. -- Hiten Pandya -- [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mouse in Xfree86 4.2.0
Hiten Pandya wrote: --- Gary Stanley [EMAIL PROTECTED] wrote: Sysinstall - post configure and re-do your mouse. The only workaround I have found. The other way, is to edit your XF86Config to point to /dev/pcm0 (if you are using a PS2 mouse), or /dev/sioN (N being the COM port number), which gives XFree86 direct access to your mouse. But remember, if you do this, you will need to disable the moused from Sysinstall. When I start XFree86 I get the error that /dev/mouse can't be found, OK devfs seems to be installd so MAKEDEV dosn't exist anymore, is there anyway to get /dev/mouse working as in FreeBSD 4? Technically the MAKEDEV script still exists in src/etc/MAKEDEV*, but it is only copied to /dev if you have disabled the DEVFS k-option, afaik. -- Hiten Pandya -- [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message /dev/sysmouse woked best for me since I have both a USB mouse and a touchpad so with /dev/sysmouse both works. /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mouse in Xfree86 4.2.0
On Mon, Apr 15, 2002 at 10:02:33AM +0200, John Angelmo wrote: When I start XFree86 I get the error that /dev/mouse can't be found, OK devfs seems to be installd so MAKEDEV dosn't exist anymore, is there anyway to get /dev/mouse working as in FreeBSD 4? I have requested of both the XFree86-4 Server and of Portmgr to make the default mouse device /dev/sysmouse. But my emails have gone unanswered. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mouse in Xfree86 4.2.0
On Mon, Apr 15, 2002 at 03:25:12PM -0700, David O'Brien wrote: I have requested of both the XFree86-4 Server and of Portmgr to make the default mouse device /dev/sysmouse. But my emails have gone unanswered. They did not go unanswered. I said it was a good idea and that I would do it, but due to lack of time I haven't done it yet. This does not stop you from doing. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cdefs and XFree86
The recent changes to /usr/include/sys/cdefs.h have broken the build of XFree86-Server. The problem is with the _XOPEN_SOURCE macro. At line cdefs.h it's checked i.e. #if _XOPEN_SOURCE = 600 but in XFree86 it's defined as #define _XOPEN_SOURCE Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cdefs and XFree86
Le 2002-04-04, Paul Richards écrivait : #if _XOPEN_SOURCE = 600 Could be changed to #if (_XOPEN_SOURCE - 0) = 600 -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cdefs and XFree86
Paul Richards [EMAIL PROTECTED] writes: The recent changes to /usr/include/sys/cdefs.h have broken the build of XFree86-Server. The problem is with the _XOPEN_SOURCE macro. At line cdefs.h it's checked i.e. #if _XOPEN_SOURCE = 600 but in XFree86 it's defined as #define _XOPEN_SOURCE Peter fixed this a day or so ago; see rev 1.51. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 and -CURRENT crashing
On Wed, 3 Apr 2002, Coleman Kane wrote: Its usb. Someone with working serial console need look at this. I have been having major issues with XFree86 recently. It seems to just completely halt the machine hard whenever I try starting it. If I run it from a remote terminal with -verbose all the way up, it seems to halt at the section just after it says it's loading the RENDER module. I was wondering if anyone else knew of or has the same problem. Basically, it is a typical Athlon system running a Radeon DDR 32MB card, but the server even crashes if I force the vga driver instead. If I run Xvfb, it seems to work fine. Thew only real odd thing about my system is that I am using a USB keyboard and mouse instead of their AT,PS/2 counterparts. -- coleman 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 and -CURRENT crashing
On Wed, Apr 03, 2002 at 03:14:43AM -0500, Coleman Kane wrote: I have been having major issues with XFree86 recently. It seems to just completely halt the machine hard whenever I try starting it. If I run it from a remote terminal with -verbose all the way up, it seems to halt at the section just after it says it's loading the RENDER module. I was wondering if anyone else knew of or has the same problem. Basically, it is a typical Athlon system running a Radeon DDR 32MB card, but the If DRI is enabled in your XF86Config, try commenting out 'Section DRI' and start XFree again. If it fixes the crash, I bet you are using the DRI kernel module stuff (port drm-kmod). I'm using it for a Radeon card, and I need to recompile/reinstall it almost every time I update my kernel to avoid crashes when starting XFree. -- Pierre Beyssac [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 and -CURRENT crashing
Yeah, I rememver that. I think it is the USB though, it crashes right at the point where it attempts to attach Input devs. -- coleman On Wed, Apr 03, 2002 at 02:35:50PM +0200, Pierre Beyssac wrote: On Wed, Apr 03, 2002 at 03:14:43AM -0500, Coleman Kane wrote: I have been having major issues with XFree86 recently. It seems to just completely halt the machine hard whenever I try starting it. If I run it from a remote terminal with -verbose all the way up, it seems to halt at the section just after it says it's loading the RENDER module. I was wondering if anyone else knew of or has the same problem. Basically, it is a typical Athlon system running a Radeon DDR 32MB card, but the If DRI is enabled in your XF86Config, try commenting out 'Section DRI' and start XFree again. If it fixes the crash, I bet you are using the DRI kernel module stuff (port drm-kmod). I'm using it for a Radeon card, and I need to recompile/reinstall it almost every time I update my kernel to avoid crashes when starting XFree. -- Pierre Beyssac[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 and -CURRENT crashing
That's what I suspected. I may try setting up the serial console on that box and see what I can find. -- coleman On Wed, Apr 03, 2002 at 11:33:40AM +0300, Andrew Bliznak wrote: On Wed, 3 Apr 2002, Coleman Kane wrote: Its usb. Someone with working serial console need look at this. I have been having major issues with XFree86 recently. It seems to just completely halt the machine hard whenever I try starting it. If I run it from a remote terminal with -verbose all the way up, it seems to halt at the section just after it says it's loading the RENDER module. I was wondering if anyone else knew of or has the same problem. Basically, it is a typical Athlon system running a Radeon DDR 32MB card, but the server even crashes if I force the vga driver instead. If I run Xvfb, it seems to work fine. Thew only real odd thing about my system is that I am using a USB keyboard and mouse instead of their AT,PS/2 counterparts. -- coleman 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
XFree86 and -CURRENT crashing
I have been having major issues with XFree86 recently. It seems to just completely halt the machine hard whenever I try starting it. If I run it from a remote terminal with -verbose all the way up, it seems to halt at the section just after it says it's loading the RENDER module. I was wondering if anyone else knew of or has the same problem. Basically, it is a typical Athlon system running a Radeon DDR 32MB card, but the server even crashes if I force the vga driver instead. If I run Xvfb, it seems to work fine. Thew only real odd thing about my system is that I am using a USB keyboard and mouse instead of their AT,PS/2 counterparts. -- coleman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4.2.0 ioctl question [-current ioccom.h __P related]
On Fri, Mar 22, 2002 at 01:01:57AM -0600, Eric Liedtke wrote: While trying to build the XFree86-4-Server port this evening(cvsuped today around 1PM CST) the build died due to a redefinition of xf86ioctl. The file /usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/include/xf86_ansic.h Yes, this is a problem recently identified on the -current mailing list that someone else is looking into. When they have a patch, I will integrate it ASAP. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
XFree86 4.2.0 with G200 fail to start with signal 10
With last update of world and ports I'm unable to start XFree86. I have a matrox G200 (agp) and I have tryed with and without the WITH_MATROX_GXX_DRIVER=yes but I got only a signal 10, core dump when starting X. At the same time I switched my MoBo from tyan trinity with k6 to a asus p2b-ds dual processor p3/500. I have a recent system (fresh compile with SMP enabled): # uname -v FreeBSD 5.0-CURRENT #24: Sun Mar 17 00:32:04 CET 2002 and I double check all update cycle (make update, buildworld, buildkernel, installkernel, installworld, mergemaster, reboot) I removed also _all_ ports and reinstalled them. Also tryed to recreate a config for XFree from screatch but it crash always with signal 10 (and sometimes with signal 6). At this time I am not sure where is (can be?) the problem, mobo, graphic card, -current or xfree. Any hint? TIA, Riccardo. PS: My previous message with ACPI info get lost, neither bounced nor accepted. And I am using correct local masquerading and my ISP that has record for reverse resolution also. Spam from .kr instead is accepted to list. Exists any other method for _serious_ user/tester to send to list? Thanks again. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 4.2.0 with G200 fail to start with signal 10
On Wed, Mar 20, 2002 at 11:29:46AM +0100, Riccardo Torrini wrote: With last update of world and ports I'm unable to start XFree86. I have a matrox G200 (agp) and I have tryed with and without the WITH_MATROX_GXX_DRIVER=yes but I got only a signal 10, core dump when starting X. At the same time I switched my MoBo from tyan trinity with k6 to a asus p2b-ds dual processor p3/500. I have a recent system (fresh compile with SMP enabled): What is your pkg_info -Ia? I committed an updated version of the Matrox driver for XFree86-4-Server, maybe you don't have that? BTW, it's not very well tested and I certainly can't test it myself w/o Matrox hardware. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
XFree86-4-Libraries-4.2.0 install failures
Any idea why a fairly up-to-date CURRENT system would fail the installation of XFree86-4-Libraries (4.2.0) with the following error? 224 [14:39] root@caerdonn:X11/doc# pwd /usr/X11R6/lib/X11/doc 225 [14:39] root@caerdonn:X11/doc# ll -d html drwxr-xr-x 2 root wheel 512 Mar 19 14:37 html/ Thanks... 266 [14:37] root@caerdonn:x11/XFree86-4-libraries# portupgrade -fw XFree86-libraries-4.1.0_1 ... (cd programs/Xserver/hw/xfree86/xf86cfg /usr/bin/install -c -m 0444 card.xbm keyboard.xbmmonitor.xbm mouse.xbm left.xbmright.xbm up.xbm down.xbmwider.xbm narrower.xbmshorter.xbmtaller.xbm /usr/X11R6/include/X11/bitmaps/usr/bin/install -c -m 0444 card.xpm computer.xpmkeyboard.xpmmonitor.xpm mouse.xpm /usr/X11R6/include/X11/pixmaps) === Generating temporary packing list /usr/X11R6/lib/X11/doc/html:Permission denied *** Error code 1 Stop in /src/ports/x11/XFree86-4-libraries. *** Error code 1 Stop in /src/ports/x11/XFree86-4-libraries. *** Error code 1 Stop in /src/ports/x11/XFree86-4-libraries. *** Error code 1 Stop in /src/ports/x11/XFree86-4-libraries. ** Command failed: make -DFORCE_PKG_REGISTER -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #46: Wed Jan 3 15:52:00 CET 2001 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current/XFree86 w/gnome or kde coredumps.
I had the same problem with the version of XFree86 that is now in the ports collection, I installed an earlier version of XFree86-4.1.) that I had from last Fall last week and it appears to work fine...something that changed recently in XFree86 (or Current) appears to be causing the problem At 07:28 PM 2/14/2002 -0800, Edwin Culp wrote: I just realized that current/XFree86-4.1.0_12,1 core dumps with either kde or gnome. I seems to work fine with twm. It dumps at the same place when starting x with both. (II) XINPUT: Adding extended input device Mouse1 (type: MOUSE) Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Bus error - core dumped Any suggestions would be appreciated. I haven't rebooted for several days so I don't know when it started. thanks, ed --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Glenn Gombert [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current/XFree86 w/gnome or kde coredumps.
I suspected that because I just upgraded to the latest and greatest:-) unless 4.2 comes back soon. I've found that several other programs like mplayer are also coredumping. I guess my decision is now to go forward to 4.2 or back. Thanks for confirming that I'm not the only one. :-) ed Quoting Glenn Gombert [EMAIL PROTECTED]: I had the same problem with the version of XFree86 that is now in the ports collection, I installed an earlier version of XFree86-4.1.) that I had from last Fall last week and it appears to work fine...something that changed recently in XFree86 (or Current) appears to be causing the problem At 07:28 PM 2/14/2002 -0800, Edwin Culp wrote: I just realized that current/XFree86-4.1.0_12,1 core dumps with either kde or gnome. I seems to work fine with twm. It dumps at the same place when starting x with both. (II) XINPUT: Adding extended input device Mouse1 (type: MOUSE) Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Bus error - core dumped Any suggestions would be appreciated. I haven't rebooted for several days so I don't know when it started. thanks, ed --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Glenn Gombert [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Never attribute to malice that which is adequately explained by stupidity.:-) --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Current/XFree86 w/gnome or kde coredumps.
I just realized that current/XFree86-4.1.0_12,1 core dumps with either kde or gnome. I seems to work fine with twm. It dumps at the same place when starting x with both. (II) XINPUT: Adding extended input device Mouse1 (type: MOUSE) Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Bus error - core dumped Any suggestions would be appreciated. I haven't rebooted for several days so I don't know when it started. thanks, ed --- 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
xfree86 4?
What are the plans about replacing XFree86 3.3.6 with XFree86 4? The -current archives have a message saying this replacement already took place last October, but the JP SNAP I installed last November certainly wasn't aware of that fact, and the current.freebsd.org snapshot from January 6 still lists 3.3.6 as well. Two more months and it will be two years since XFree86-4.0... Looking at xfree86.org's comparisons of supported video cards, it seems quite obvious that XFree86 4 supports almost everything 3 did, and a lot more. I just got a computer with a nvidia GeForce2 GTS - not exactly a new card, but completely unsupported in 3.3.6 - but well supported in 4.1.0. 3.3.6 is over two years old, and none of the ATI or nvidia cards (and that's just about all desktops, no?) made since then are supported. There's always the port, but integration would be a much more friendly solution. I must be growing lazy :) Out-of-the-box XFree86 4 and easy PPPoE setup led me to use RedHat (desk top only - the server's still FreeBSD, of course), but I'm missing FreeBSD. Apologies if this has already been discussed to death, but such discussions aren't in the -current or -stable archives :) -David To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 3.3.6 dying
On 2001-Nov-30 10:55:39 +0200, Maxim Sobolev [EMAIL PROTECTED] wrote: Peter Jeremy wrote: With a recently re-built XFree86, running on -current from last Sunday, whenever I hit one of the keypad keys, the X server crashes. This is somewhat disconcerting... ... Apply the following patch and rebuild/reinstall your kernel: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/include/psl.h.diff?r1=1.10r2=1.11 My kernel/userland is newer than that - it was built with psl.h v1.11 so that's not the problem. (In any case, PSL_ID is 0x0020 which isn't in the reported EFLAGS). Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 3.3.6 dying
Peter Jeremy wrote: With a recently re-built XFree86, running on -current from last Sunday, whenever I hit one of the keypad keys, the X server crashes. This is somewhat disconcerting... The kernel prints sigreturn: eflags = 0x13282, was 0x256 (the old eflags value an addition I made to that printf whilst tracking down another problem). These values are consistent. The X server reports that it received SIGBUS and will core dump, but instead goes into a tight loop and needs kill -ABRT or kill -9 to recover. This happens whether or not I'm logged in, after I use xmodmap to unmap the relevant keycodes and when the screen is locked. ktrace on the Xserver shows the server reading a keycode from the keyboard, checking the mouse and getting EWOULDBLOCK then receiving a SIGBUS. Has anyone else seen anything like this? Apply the following patch and rebuild/reinstall your kernel: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/include/psl.h.diff?r1=1.10r2=1.11 -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
XFree86 3.3.6 dying
With a recently re-built XFree86, running on -current from last Sunday, whenever I hit one of the keypad keys, the X server crashes. This is somewhat disconcerting... The kernel prints sigreturn: eflags = 0x13282, was 0x256 (the old eflags value an addition I made to that printf whilst tracking down another problem). These values are consistent. The X server reports that it received SIGBUS and will core dump, but instead goes into a tight loop and needs kill -ABRT or kill -9 to recover. This happens whether or not I'm logged in, after I use xmodmap to unmap the relevant keycodes and when the screen is locked. ktrace on the Xserver shows the server reading a keycode from the keyboard, checking the mouse and getting EWOULDBLOCK then receiving a SIGBUS. Has anyone else seen anything like this? Peter 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
XFree86-4 required?
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) STABLE# cd /usr/ports/graphics/xv make clean === Cleaning for libtool-1.3.4_2 === Cleaning for jpeg-6b === Cleaning for png-1.2.0 === Cleaning for tiff-3.5.5 === Cleaning for XFree86-3.3.6_10 === Cleaning for xv-3.10a_2 CURRENT# cd /usr/ports/graphics/xv make clean === Cleaning for gettext-0.10.35 === Cleaning for gmake-3.79.1 === Cleaning for imake-4.1.0 ## (SEE NOTE) === Cleaning for libtool-1.3.4_2 === Cleaning for jpeg-6b === Cleaning for png-1.2.0 === Cleaning for tiff-3.5.5 === Cleaning for freetype2-2.0.4 === Cleaning for XFree86-libraries-4.1.0 ## (SEE NOTE) === Cleaning for xv-3.10a_2 NOTE: are taken from /usr/ports/distfiles/xc/X410src*, over 40MB of compressed archive. Yes, my -STABLE box is very slow P75 :( Riccardo. 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: Current XFree86
On 31 Jul, David Wolfskill wrote: Sounds like you're running moused. I don't think XFree86 4.1 can use /dev/sysmouse and interact with moused like 3.3.6 could. I'm running XFree86 4.1.0_4 on my laptop (tracking both -STABLE and -CURRENT daily), and I use moused just fine. However, the Device (in /etc/XF86Config) is listed as /dev/mouse, and in (-CURRENT's) /etc/rc.devfs, I have ln -fs /dev/sysmouse /dev/mouse I've seen no problems attributable to mouse interactions. I just installed 4.1.0 and am wondering why you make a link instead of replacing /dev/mouse with /dev/sysmouse in der XF86Config? Bye, Alexander (with a working mouse, but without the symlink). -- One world, one web, one program -- Microsoft promotional ad Ein Volk, ein Reich, ein Fuehrer -- Adolf Hitler http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current XFree86
Date: Sun, 19 Aug 2001 17:58:44 +0200 (CEST) From: Alexander Leidinger [EMAIL PROTECTED] I'm running XFree86 4.1.0_4 on my laptop (tracking both -STABLE and -CURRENT daily), and I use moused just fine. However, the Device (in /etc/XF86Config) is listed as /dev/mouse, and in (-CURRENT's) /etc/rc.devfs, I have ln -fs /dev/sysmouse /dev/mouse I've seen no problems attributable to mouse interactions. I just installed 4.1.0 and am wondering why you make a link instead of replacing /dev/mouse with /dev/sysmouse in der XF86Config? In the absence of any information (that I could see) to do anything else, I tried to mimic the configuration in -STABLE, which has: dhcp-135[2] ls -l /dev/*mouse* lrwx-- 1 root wheel13 Aug 8 17:04 /dev/mouse - /dev/sysmouse crw--- 1 root wheel 12, 128 Aug 11 07:09 /dev/sysmouse (And since I'm running both -STABLE -CURRENT on the same machine, and using the same flavor of XFree86 in each environment, I thought it would be a nice touch to keep the XF86Config files the same.) Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Current XFree86
Upgraded my laptop to current the other day, just to get the cardbus cards working (which works like a charm). Found a problem though related to XFree86. When I run startx X initiates for a short while, but dies with the message: (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. And then it's over :) What am I missing? (of course XFree86 ran on the box (4.3-STABLE) before the upgrade) -- __o regards, Gunnar ---_ \,_ email: [EMAIL PROTECTED] (_)/ (_) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
