Hi there,
I've been trying to build gnustep-make inside a separate directory.
The directory where the sources are contains spaces in its name and
configure fails. This seems to be a bug in autoconf. Some of the
macros lack quotes (") that are needed is this where to function.
Has someb
On May 25, 2005, at 1:48 PM, David Lázaro Saz wrote:
Hi there,
I've been trying to build gnustep-make inside a separate directory.
The directory where the sources are contains spaces in its name and
configure fails. This seems to be a bug in autoconf. Some of the
macros lack quotes (") t
On 26/05/2005, at 1:00, Adam Fedor wrote:
It might be nice to fix autoconf, but then you'll run into make.
'make' doesn't like spaces in directories either - and this is a
fundamental design issue.
But doesn't make always run in the same directory? Anyway I'm
placing this on the back bu
On May 26, 2005, at 12:04 PM, David Lázaro Saz wrote:
On 26/05/2005, at 1:00, Adam Fedor wrote:
It might be nice to fix autoconf, but then you'll run into make.
'make' doesn't like spaces in directories either - and this is a
fundamental design issue.
But doesn't make always run in the sa
On May 26, 2005, at 12:36 PM, Adam Fedor wrote:
if test $cross_compiling = no; then
AC_FUNC_SETPGRP
else
#set a default value
fi
I was working on that, but the default for MingW is not what the
normal default would be, but I wasn't entirely sure.
Actually, now I look at the code, it
On 26/05/2005, at 20:52, Adam Fedor wrote:
Actually, now I look at the code, it could probably just be:
if test $cross_compiling = no; then
AC_FUNC_SETPGRP
fi
I'll try that; I think that would be sufficient too.
___
Gnustep-dev mailing list
G
Adam Fedor wrote:
On May 26, 2005, at 12:04 PM, David Lázaro Saz wrote:
On 26/05/2005, at 1:00, Adam Fedor wrote:
It might be nice to fix autoconf, but then you'll run into make.
'make' doesn't like spaces in directories either - and this is a
fundamental design issue.
But doesn't make
> > It might be nice to fix autoconf, but then you'll run into make.
> > 'make' doesn't like spaces in directories either - and this is a
> > fundamental design issue.
>
> But doesn't make always run in the same directory? Anyway I'm
> placing this on the back burner for some time, and it'
On 27/05/2005, at 13:54, Nicola Pero wrote:
The make syntax uses spaces to separate filenames in list of
targets or
requisites, or everywhere really ... it's a basic design decision
in the
make syntax.
Thanks for the explanation. This also explains why Apple developed a
completely new
On May 27, 2005, at 9:34 AM, David Lázaro Saz wrote:
On 27/05/2005, at 13:54, Nicola Pero wrote:
The make syntax uses spaces to separate filenames in list of targets
or
requisites, or everywhere really ... it's a basic design decision in
the
make syntax.
Thanks for the explanation. This
BTW, first they moved to JAM, then they internalized JAM's code into
Xcode so it's not invoked as a separate process. It's possible that
JAM is able to handle spaces, though maybe Apple had to modify it for
this.
Jam handles spaces (and a number of other things)
Regards,
Sheldon
11 matches
Mail list logo
