Hello Markus,
sorry for the long delay.
* Duft Markus wrote on Mon, Oct 20, 2008 at 08:48:48AM CEST:
> > * Duft Markus wrote on Fri, Oct 17, 2008 at 09:26:44AM CEST:
> > > It happens when:
> > >
> > > *) configuring automake 1.9.6 with ./configure
> --cache-file=../cache
> > > *) bootstrapping
>
> * Duft Markus wrote on Fri, Oct 17, 2008 at 09:26:44AM CEST:
> > It happens when:
> >
> > *) configuring automake 1.9.6 with ./configure
--cache-file=../cache
> > *) bootstrapping libtool 1.5.24 or 26 with autoconf 2.59
> > *) configuring libtool with the same cache: ./configure
> > --cache
* Duft Markus wrote on Fri, Oct 17, 2008 at 09:26:44AM CEST:
> It happens when:
>
> *) configuring automake 1.9.6 with ./configure --cache-file=../cache
> *) bootstrapping libtool 1.5.24 or 26 with autoconf 2.59
> *) configuring libtool with the same cache: ./configure
> --cache-file=../cache
On 2008-10-17, Eric Blake <[EMAIL PROTECTED]> wrote:
> According to Olly Betts on 10/16/2008 7:40 PM:
>> On 2008-10-16, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
>>> How do you get two concurrent configure scripts updating the same
>>> config.cache file?
>>
>> Open terminal (or screen) windows fo
>
> * Duft Markus wrote on Fri, Oct 17, 2008 at 09:00:16AM CEST:
> > > I haven't been able to do so yet. Here's what I tried. Please
> modify
> > > the example so that it shows the failure (maybe it only needs
> different
> > > flags passed to configure?)
> >
> > Hehe, the problem occured when u
> I recently posted a patch to do just this. It wasn't applied, one
> reason being that we didn't see a way how two configure scripts could be
> running simultaneously; with AC_CONFIG_SUBDIRS at least (the GCC tree
> uses a different way but uses per-configure cache files). How do you
> get two
* Duft Markus wrote on Fri, Oct 17, 2008 at 09:00:16AM CEST:
> > I haven't been able to do so yet. Here's what I tried. Please modify
> > the example so that it shows the failure (maybe it only needs different
> > flags passed to configure?)
>
> Hehe, the problem occured when using the same cach
>
> Hello Markus,
>
> thanks for the reports.
>
[snip]
>
> FWIW, I'm not yet sure whether this is a valid problem. Even if it
is,
> you should be able to work around it by adding AC_CANONICAL_HOST to
the
> toplevel configure.ac. But anyway, before discussing validity let's
> try
> to reproduc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Olly Betts on 10/16/2008 7:40 PM:
Hello Olly,
> On 2008-10-16, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
>> How do you get two concurrent configure scripts updating the same
>> config.cache file?
>
> Open terminal (or screen) windows f
On 2008-10-16, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> How do you get two concurrent configure scripts updating the same
> config.cache file?
Open terminal (or screen) windows for two subdirectories of the combined
tree and in each modify a file which causes configure to be rerun (e.g.
Makefi
Hello Markus,
thanks for the reports.
* Duft Markus wrote on Thu, Oct 16, 2008 at 03:46:51PM CEST:
> >
> > I just noticed, that when i enable a config.cache that is used by more
> > than one package is problematic, when the first on checks for the build
> > system type only, and the second for b
>
> Hi!
>
> I just noticed, that when i enable a config.cache that is used by more
> than one package is problematic, when the first on checks for the
build
> system type only, and the second for both build and host system type.
> This is, because the host system type check uses ac_cv_build_alias
12 matches
Mail list logo
