* Kyle Sallee wrote on Sat, Oct 21, 2006 at 08:31:05PM CEST:
> On 10/21/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
>
> >> > I understand that you are strongly against using forks
> >> > where the equivilent can be coded without it.
> >
> >Not so. Forking in order to invoke faster tools or to
* Kyle Sallee wrote on Sat, Oct 21, 2006 at 07:52:17PM CEST:
> Okay, the 26M trace was probably typical of almost any
> of the libtool invocations during the long parts of compiling koffice.
Thanks for the trace. First, could you grab a new CVS HEAD snapshot of
Libtool (from the web page), build
Hello folks
It seems that libtool removes the -F's passed to GCC when linking a library on
Darwin that uses MacOSX' framework thingy:
$ make
/bin/sh ../../../libtool --tag=CXX --mode=link g++ -Wall -W -Weffc++
-Wold-style-cast -pipe -g -O2 -o libfsm_xml_parser.la -rpath /usr/local/lib
-headerpad
On Oct 22, 2006, at 9:15 PM, SIGOURE Benoit wrote:
Hello folks
It seems that libtool removes the -F's passed to GCC when linking a
library on
Darwin that uses MacOSX' framework thingy:
Okay, I'll add -F to the list of flags that get passed through, in
the meantime, you can use -XCClinker
On Oct 22, 2006, at 9:15 PM, SIGOURE Benoit wrote:
Hello folks
It seems that libtool removes the -F's passed to GCC when linking a
library on
Darwin that uses MacOSX' framework thingy:
I just applied these patches.
Peter
80-peter-dashF.patch
Description: Binary data
66-peter-dashF-b1
