At Mon, 31 Mar 2003 23:10:35 +0900,
Naofumi Yasufuku wrote:
>
> [1 ]
> At Mon, 31 Mar 2003 05:52:47 +0900,
> Naofumi Yasufuku wrote:
> >
> > Hi,
> >
> > libtool uses '~' as IFS in some commands (ex. $archive_expsym_cmds),
> > so that win32 short name which includes '~' (ex. c:/progra~1/foo/...)
At Mon, 31 Mar 2003 05:52:47 +0900,
Naofumi Yasufuku wrote:
>
> Hi,
>
> libtool uses '~' as IFS in some commands (ex. $archive_expsym_cmds),
> so that win32 short name which includes '~' (ex. c:/progra~1/foo/...)
> causes a problem. For example, if we want to build DLL which is linked
> with -Lc:
Naofumi Yasufuku wrote:
At Mon, 31 Mar 2003 00:10:10 +0200,
Guido Draheim wrote:
I have a similar problem on a different account: the version
management system at my employer uses "~" in directory names
to flag different branches and subversions of projects and
their checkout areas. The libtool h
At Mon, 31 Mar 2003 00:10:10 +0200,
Guido Draheim wrote:
>
> I have a similar problem on a different account: the version
> management system at my employer uses "~" in directory names
> to flag different branches and subversions of projects and
> their checkout areas. The libtool has the tendency
I have a similar problem on a different account: the version
management system at my employer uses "~" in directory names
to flag different branches and subversions of projects and
their checkout areas. The libtool has the tendency to
resolve some symlinks, so it does not help to put some
directori
