Eric Blake ebb9 at byu.net writes:
I've got a pending patch series to add m4_set_* where I wanted to use
m4_join, but not have the empty argument omitted. I'm borrowing this from
the m4 manual, and committing.
It turns out that m4_joinall is quadratic on m4 1.4.x (just as any other
Eric Blake ebb9 at byu.net writes:
I've got a pending patch series to add m4_set_* where I wanted to use
m4_join, but not have the empty argument omitted. I'm borrowing this from
the m4 manual, and committing.
It turns out that m4_joinall is quadratic on m4 1.4.x (just as any other
Are you talking about autotools like `autoscan' and `autoconf', or the
generated ./configure itself?
I was thinking about autotools and ./configure itself.
For end user ./configure itself is more important (more ofen used).
Each is dependent on many things, such as m4 and whatever /bin/sh
On Wed, 23 Jul 2008 10:16:20 +0200
litlle girl [EMAIL PROTECTED] wrote:
Ok,
maybe turn ./configure more SMP will be easier?
What about split ./configure to n files
(n=2 for dualcore)
./configure == ./configure1 + ./configure2
and then
/bin/sh ./configure1
/bin/sh ./configure2
How do you split
2008/7/23 [EMAIL PROTECTED]:
How do you split existing configure into 2 parts:
configrue1 and configure2?
Yes, this can be a problem, you're right.
But what about second idea: in ./configure
odd commands run normally
and even with
Last 3 (5?) commands run normally to have sure that tasks at
On Wed, 2008-07-23 at 11:21 +0200, litlle girl wrote:
2008/7/23 [EMAIL PROTECTED]:
How do you split existing configure into 2 parts:
configrue1 and configure2?
Yes, this can be a problem, you're right.
But what about second idea: in ./configure
odd commands run normally
and even
Hey folks,
We've switched the default version of Libtool in our development version
to 2.2, and are doing such migrations as are necessary to permit this.
In the progress, we've encountered an interesting difference between the
behaviour of autoreconf and libtoolize that leaves you with a broken
2008/7/23 Tim Post [EMAIL PROTECTED]:
That would be _really_ racey. Odd would often have to block while
waiting for something even needs to do, or vice-versa.
This is the reason to split configure to two files witch
sh scripts in 1st file not depending on 2nd file scripts result
and check only
