Re: path separator

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 23, 2007 at 07:47:09PM +0100, Ralf Wildenhues wrote:
> * Paul Eggert wrote on Tue, Jan 23, 2007 at 12:34:47AM CET:
> > Ralf Wildenhues <Ralf.Wildenhues@xxxxxx> writes:
> > > Maybe we can agree on some suitable header snippet and put that in the
> > > Autoconf documentation?
> > 
> > This is an instance of a more general problem: the choice of shell on
> > the build host as opposed to the target host.  It's kind of a messy
> > area now.  I suspect it's better to work on the more-general problem
> > than worry only about the path separator.
> 
> Agreed.  Keith's (very nice!) explanation about the relationship of the
> different w32 shell environments (why don't you, after hashing out the
> details, put up a page in the MinGW wiki like that?) makes me want to
> call the MinGW/MSYS combo as a semi-cross-compile environment, where
> things at run time are slightly different from things at build time.
> Yeah, I know, it's not a good analogy and a bit far fetched, but still.

Hi,

Yes, thanks Keith!

For the simple minded like myself, does this boil down to the fact that
the PATH_SEPARATOR is different if an application is run from a cmd or
msys shell?

If so, how can autoconf possibly help in this situation?

Thanks,
Bob Rossi


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux