Date: Fri, 20 Dec 2002 17:00:29 +0100 From: Emiel Kollof <coolvibe@hackerheaven.org> To: Stijn Hoop <stijn@win.tue.nl> Cc: freebsd-stable@freebsd.org Subject: Re: The plot thickens (problem solved!) (was Re: More information ...) Message-ID: <20021220160029.GB81599@hackerheaven.org> In-Reply-To: <20021220153518.GC23803@pcwin002.win.tue.nl> References: <20021220013445.GA75547@hackerheaven.org> <20021220020545.GC75547@hackerheaven.org> <200212200333.04276.coolvibe@hackerheaven.org> <20021220113825.GA80454@hackerheaven.org> <20021220152828.GA81599@hackerheaven.org> <20021220153518.GC23803@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
* Stijn Hoop (stijn@win.tue.nl) wrote: > On Fri, Dec 20, 2002 at 04:28:28PM +0100, Emiel Kollof wrote: > > Allright, who broke XFree86? Fess up! :) > > Nobody. I think your system is broken somehow. Hm weird. > > After removing _every_ trace of X-related stuff off of my system, X just > > completely fails to build. XFree86-4-libraries builds fine, but then when > > building the XFree86-4-clients it bombs, same pthread/XthrStub related > > error I have been meandering about all day. > > And sent 20 mails in the process. Yes, because nobody gave me any feedback or reports in any form. Which (for me at least) results in me digging and reporting anything I find. At least the archives of this mailing list will be aware of my attempts to find a workaround for this problem. It might help other people. > > I stronly suspect that the patch-UIThrStubs.c in the X-4-libs port must > > be bogus. After removing it the problems were gone. > > It isn't. At least not on my system. The funny thing is (and it's also part of why I was delving so deeply) that a related issue was in the archives. Also, needing -pthread for *every* X11 app seemed a bit, well, weird to me. > > Removing the patch-UIThrStubs.c in the files/ dir of the > > XFree86-4-libraries port made things sane again... > > I didn't do anything like that. > > I can understand that you're not happy being told that something on your system > is broken, and maybe it is even a ports issue, but before broadcasting this > 20 times over the -STABLE lists please try to recompile etc. without > CPU optimizations, by using portupgrade -fR etc. Later attempts _without_ optimalisations resulted in the same errors. I did use portupgrade -fR, and I _do_ keep a clean and tidy system. I cvsup religiously, rebuild world/kernel when needed, and read UPDATING etc. etc. There's absolutely no reason why this couldn't have affected someone else as well. Even from a clean environment (everything X related removed, as in pkg_delete all of X and nuking what's left as in rm -rf /usr/X11R6) this glitch occured *again*. Odd, no? Oh, I must've recompiled the whole (and parts) of X like 10 times today. I also rebuild world and kernel again just to make sure my toolchain and evironment was pristine. > I can guarantee that if the XFree-4-libraries port was broken there would > be much more people who have the same problem. I might be the first to have noticed. What if suddenly 20 more people in the span of the next 24 hours report that X or X apps won't build? At least there's a workaround that worked at least for me. It might also work for someone else. The only thing that the offending (well, for me at least) patch added was some stub info for gcc3. STABLE users won't bleed for removing that patch (unless they compile ports with gcc3 of course). > Have you removed the imake port when rebuilding all of X? Yes, of course. I even axed the entire /usr/X11R6 dir after deinstalling with the pkg_* tools to make sure nothing conflicting was left behind. Cheers, Emiel -- "Man invented language to satisfy his deep need to complain." -- Lily Tomlin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021220160029.GB81599>