Re: tweak for documentation of how to create universal binaries

Hi Bruno, * Bruno Haible wrote on Sun, Apr 19, 2009 at 05:39:06PM CEST: > Ralf Wildenhues wrote: > > In the > > patch that I sent, there is an "icc" case match. If you omit that match > > from the patch, does not specifying --enable-dependency-tracking still > > cause depmode=none for gcc in univ

Re: tweak for documentation of how to create universal binaries

Ralf Wildenhues wrote: > In the > patch that I sent, there is an "icc" case match. If you omit that match > from the patch, does not specifying --enable-dependency-tracking still > cause depmode=none for gcc in universal mode? Yes. Without --enable-dependency-tracking: depmode=none. With --enable

Re: tweak for documentation of how to create universal binaries

Hi Bruno, * Bruno Haible wrote on Sun, Apr 19, 2009 at 05:15:19PM CEST: > Ralf Wildenhues wrote: > > The patch below (against Automake) should do the trick. > > Can you try it out, and report back the depmode chosen with and without > > --enable-dependency-tracking and whether the depmode works (i

Re: tweak for documentation of how to create universal binaries

Ralf Wildenhues wrote: > depend.m4 could detect universal builds, and in > that case discard any problematic dependency extractors. That means, in > effect that only "slow" extraction mechanisms are eligible (and will > thus be chosen only if --enable-dependency-tracking was passed > explicitly).

Re: tweak for documentation of how to create universal binaries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 4/18/2009 10:44 AM: > I'm still not quite ready to give up. Glad to hear it. > Can you try it out, and report back the depmode chosen with and without > --enable-dependency-tracking and whether the depmode works (in ca

Re: tweak for documentation of how to create universal binaries

[ adding automake-patches; this is ] Hello Bruno, Peter, * Bruno Haible wrote on Sat, Apr 11, 2009 at 12:29:10PM CEST: > Ralf Wildenhues wrote: > > AIUI, the nature of the issue seems to be that one process scribbles > > into the