Re: Request for option to disable building of static library

2003-07-22 Thread Peter O'Gorman
On Tuesday, July 22, 2003, at 11:32 PM, Nick Hudson wrote: OK, a better question is does anyone run an operating system that needs this feature still? I don't know the answer to this particular question, so I'll answer a different one :) This feature, if used more widely, would have been great

Re: Request for option to disable building of static library

2003-07-22 Thread Peter O'Gorman
On Tuesday, July 22, 2003, at 09:37 PM, Sander Niemeijer wrote: In our situation it is not possible to just disable building of static libraries on a global level for our package, since our package provides multiple libraries and some of them need to be provided in both static and shared vers

Re: Is libtool being maintained at all?

2003-07-14 Thread Peter O'Gorman
On Monday, July 14, 2003, at 07:12 AM, Bob Friesenhahn wrote: Becoming a maintainer involves signing a contract with the FSF (takes two or three weeks) and being set up with CVS commit privileges. Is this contract the same as the copyright assignment? I'd like a commit bit to apply darwin specif

Re: Libtool 1.5 on MacOS X

2003-06-02 Thread Peter O'Gorman
On Monday, June 2, 2003, at 01:48 PM, Bill Northcott wrote: Because of the way things are set up, adding fsf gcc support is essentially adding a completely different compiler. Depending on my available free time, I may decide to revisit this issue, do you really think it is required? With stock G

Re: Libtool 1.5 on MacOS X

2003-06-01 Thread Peter O'Gorman
On Saturday, May 31, 2003, at 11:54 PM, Marcus G. Daniels wrote: Peter O'Gorman wrote: Because of the way things are set up, adding fsf gcc support is essentially adding a completely different compiler. Depending on my available free time, I may decide to revisit this issue, do you r

Re: Libtool 1.5 on MacOS X

2003-05-31 Thread Peter O'Gorman
Well, the FSF gcc is explicitly not supported, that is why the check for Apple. I assumed (obviously wrongly) that you were using Apple's gcc-3.3 from darwin cvs 1314 Because of the way things are set up, adding fsf gcc support is essentially adding a completely different compiler. Depending on

Re: Libtool 1.5 on MacOS X

2003-05-30 Thread Peter O'Gorman
Could you possible run this again in this directory (preferably with all the .o's present in the .libs dir) using `"make SHELL=/bin/sh -x" >& log.txt' and send me the log. Thanks, Peter On Friday, May 30, 2003, at 01:34 PM, Bill Northcott wrote: *** libtool 1.5*

Re: release schedule

2003-03-20 Thread Peter O'Gorman
Well, Ben Reed just pointed out a problem with kde and current libtool on darwin. There is one other thing I want to fix too. Should have a patch this weekend, if a snapshot is released after that, I'd be happy too :-) Peter On Friday, March 21, 2003, at 11:16 AM, Guido Draheim wrote: I did j

zsh and echo tests

2003-03-16 Thread Peter O'Gorman
Well, in trying to find an echo test to discover zsh echo's removal of \ escapes, I came up with this: if test "X`($echo '\t') 2>/dev/null`" = 'X\t' && eval echo_test_var=`$echo '\\\t'` && test "X$echo_test_var" = "X\t" && Okay to include this with my next try at a darwin patch? It wou

Re: relinking broken on macosx?

2003-02-25 Thread Peter O'Gorman
Ben, I have a patch to disable relinking, for some reason on current libtool, _LT_AC_TAGVAR(hardcode_direct, $1)=yes This is wrong, and makes libtool think relinking is required, set it to no. I am not sure if you also need to set _LT_AC_TAGVAR(hardcode_libdir_flag_spec, $1)='-L$libdir' I haven't

[Q] what to do with unknown flags

2003-02-22 Thread Peter O'Gorman
Hi, There are quite a few Makefiles in packages which add flags without -Wl, or -Xlinker to LDADD and expect them to work (on darwin the most common is -framework name_of_framework), they don't appear in the link line for shared libs. I am unsure if this is by design or accident. They appear wh

Re: [Fink-devel] OS/X Libtool && -bundle

2003-02-06 Thread Peter O'Gorman
On Thursday, February 6, 2003, at 04:19 PM, Ben Hines wrote: btw, i think the bind_at_load two-step stuff is only need for C++. It shouldn't be in the C part of libtool. pogma? Yes, I posted to the libtool list recently (last week?) asking why it is done two step and -bind at load for all t

Re: Pending release of 1.5

2003-02-04 Thread Peter O'Gorman
On Tuesday, February 4, 2003, at 04:10 PM, Robert Boehne wrote: Hello, I'm just about to make the release of Libtool 1.5. If anyone would like to test the current CVS on their favorite platform and report any problems, please do so! If not, your woes may have to wait for 1.5.1. Okay, then

Re: flat namespaces redux

2003-02-03 Thread Peter O'Gorman
On Tuesday, February 4, 2003, at 12:01 AM, Benjamin Reed wrote: cc -multiply_defined suppress -prebind blah || cc -flat_namespace -undefined suppress blah 1. libkdeui's LIBADD is "-lkdecore" 2. the first half of the link complains that -lqt-mt is indirectly referenced 3. it builds the librar

Re: flat namespaces redux

2003-02-03 Thread Peter O'Gorman
On Monday, February 3, 2003, at 01:27 AM, Benjamin Reed wrote: This would make libtool default to making twolevel libraries (which is darwin's linker default, in fact), but you could still pass "-flat_namespace -undefined suppress" to the command-line if you have a poorly behaving app. W

darwin -bind_at_load only required for the CXX tag?

2003-02-01 Thread Peter O'Gorman
Hi, I note that for darwin for all tags libraries are linked using ld -r, followed by cc ... -bind_at_load .. etc. I don't believe that all this is necessary for any tag other than CXX, but I am not sure. I don't like the idea that absolutely everything linked with current libtool is non lazil

<    1   2   3   4   5