On 10/08/2010 07:36 PM, Daniel Herring wrote:
> So it appears that spaces in directory names are strongly discouraged.
> An authoritative answer would have to come from the autoconf list. Its
> possible this changed in the recently released autoconf 2.68, but I doubt
> it.
You might find it inte
Daniel Herring
writes:
> On Sun, 3 Oct 2010, Juan Jose Garcia-Ripoll wrote:
>
>> It seems that "configure" does not work when one of the directories contains
>> a space in the name. Is this a known limitation?
>
> Here's output from a recent GNU package's configure script.
>
> # ../a\ space/libt
On Sun, 3 Oct 2010, Juan Jose Garcia-Ripoll wrote:
> It seems that "configure" does not work when one of the directories contains
> a space in the name. Is this a known limitation?
Here's output from a recent GNU package's configure script.
# ../a\ space/libtool-2.4/configure
../a space/libtool
On 4 October 2010 00:16, Juan Jose Garcia-Ripoll
wrote:
> On Mon, Oct 4, 2010 at 12:09 AM, Michael Wood 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"'
On Sun, Oct 3, 2010 at 3:16 PM, Juan Jose Garcia-Ripoll
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 the configure script with a rela
On Sun, 3 Oct 2010 20:22:13 -0400
Matthew Mondor 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 Mon, 04 Oct 2010 01:52:45 +0200
p...@informatimago.com (Pascal J. Bourguignon) wrote:
> Juan Jose Garcia-Ripoll
> 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 w
Juan Jose Garcia-Ripoll
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 bug. At least, the Y2K bug was lim
On Mon, Oct 4, 2010 at 12:09 AM, Michael Wood 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
Packages
On 3 October 2010 22:41, Juan Jose Garcia-Ripoll
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
>> wrote:
>> > It seems that "configure" does not work when one of the directories
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 that "configure" does not work when one of the directories
> contains
> > a space in the
On Sun, 3 Oct 2010 22:16:21 +0200, Juan Jose Garcia-Ripoll
wrote:
> It seems that "configure" does not work when one of the directories contains
> a space in the name. Is this a known limitation?
I have never /ever/ tried to run configure with --prefix having spaces
in it.
On Linux due to cultu
12 matches
Mail list logo
