On 3 October 2010 22:41, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
On Sun, Oct 3, 2010 at 10:31 PM, Samium Gromoff
_deepf...@feelingofgreen.ru wrote:
On Sun, 3 Oct 2010 22:16:21 +0200, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
It seems
On Mon, Oct 4, 2010 at 12:09 AM, Michael Wood esiot...@gmail.com wrote:
I've just tried with curl, since I have the sources on my machine and
it uses autoconf. I copied it to '/tmp/some where' and then ran
'./configure --prefix=/tmp/some path'.
The configure step worked without complaint
Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com writes:
It seems that configure does not work when one of the directories
contains a space in the name. Is this a known limitation?
Allowing spaces in pathnames would require an effort superior to that of
the correction of the Y2K
On Mon, 04 Oct 2010 01:52:45 +0200
p...@informatimago.com (Pascal J. Bourguignon) wrote:
Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com writes:
It seems that configure does not work when one of the directories
contains a space in the name. Is this a known limitation?
On Sun, 3 Oct 2010 20:22:13 -0400
Matthew Mondor mm_li...@pulsar-zone.net wrote:
use the special option a processing command might support, such as -X
option to grep for piping through xargs, etc.
Err, I meant -print0 option to find, perl -0, sort -z, grep -Z etc.
--
Matt
On Sun, Oct 3, 2010 at 3:16 PM, Juan Jose Garcia-Ripoll
juanjose.garciarip...@googlemail.com wrote:
It seems that configure does not work when one of the directories contains
a space in the name. Is this a known limitation?
Juanjo
Hmm, I don't understand what you mean...
But, I usually invoke
