Re: pbms on freebsd w/ threads
- From: Owen Taylor <otaylor redhat com>
- To: Jeremy Lea <reg shale csir co za>
- Cc: gtk-list redhat com, Emmanuel DELOGET <pixel DotCom FR>, wilhelmi ira uka de
- Subject: Re: pbms on freebsd w/ threads
- Date: 05 May 1999 11:31:39 -0400
Jeremy Lea <reg@shale.csir.co.za> writes:
> Could you please detail this problem, because I'm not seeing any
> problems. Are you linking the app correctly (with -pthread)? Glib's
> configure is broken for FreeBSD. I submitted patches but they seemed to
> be ignored. See patch-ad in the devel/glib12 port.
Well, they weren't ignored (we traded a few messages
on the subject, IIRC), but no, they were never applied.
For a couple of reasons:
1) I got confused with the FreeBSD v2 vs. FreeBSD v3;
-lc_r vs. pthreads... etc...
2) There were a number of issues involved, and it p
a) libtool patches. I believe that the equivalent patches
have gone into libtool since and if they aren't
in GLib now, will certainly be in the next release,
which is libtool-1.3 based.
b) Some configuration tests to deal with libc_r oddities.
These probably were OK to go in.
c) library name issues. There are known issues with
the way we do shared-library naming on platforms
like FreeBSD and SunOS. Some fixes are definitely
needed here, but getting all the tests right is
not easy for someone like me who only has ELF-based
platforms. (And FreeBSD is the worst part of the
confusion because of a switch from a.out to
ELF.)
I understood at the time that this part of the
patch wasn't meant to be submitted because the
FreeBSD policy was to invent completely new shared
library names (!) ... (though I've heard different
stories from different people)
So, anyways the advice is to resubmit the patch in
small independent pieces.
3) The patches was sent to me personally; this is a good
way of getting them forgotten. If you don't want
your patches to get forgotten, either upload them
to ftp://ftp.gtk.org/pub/incoming/ or submit them
to the bug tracking system. (The former, or a combination
of the two is preferred for patches that are more
than a couple of lines long.)
Thanks!
Owen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]