Mail Archives: cygwin/2003/12/29/02:22:59
--- "Blair P. Houghton" <blair AT houghton DOT net> wrote:
> I think I've found the problem.
>
> By more careful use of the -d=flags option to make, I traced it down to the
> second of two "subdirs"
> targets, and then turned off the NOECHO command (by taking it out of the
> script line in the Makefile
> under the second subdirs target).
>
> Then, making only in the .../ext/B directory (as Yitzchak suggested), I got
> this output:
>
> % make -f Makefile all
> cd C && make -f Makefile all LIB="C:\Program Files\Microsoft Visual Studio
> .NET\Vc7\lib\;C:\Program Files\Microsoft.NET\FrameworkSDK\Lib\"
> LIBPERL_A="libperl"
> LINKTYPE="dynamic" PREFIX="" OPTIMIZE="-O2" PASTHRU_DEFINE="" PASTHRU_INC=""
> Syntax error: Unterminated quoted string
> make: *** [subdirs] Error 2
>
> Note the LIB variable. It's not the spaces that are glaring, it's that
> trailing backslash before
> the closing double-quote. Leave it to Microsoft to confuse a path with a
> string that is part of the
> computation of a path (they shoulda left the last slash off; it's only there
> as step-saving cruft
> for some string catenation that would probably be better written to do the
> slash insertion itself
> anyway; lamers).
>
> LIB comes from the calling shell environment, which is a default xterm
> running bash under XFree86.
>
> So here's the question:
>
> What sets LIB in the cygwin environment? It comes verbatim from the DOS
> environment list but I
> don't see the importation in any of the layered rc files (but I could've
> missed it). And is there a
> way to automatically make cygwin translate these paths from backslash to
> forward slash when
> importing? You'd think that would be the default. Is there a way to suppress
> all importation or all
> but a list of explicitly named variables? Obviously I can exclude some by
> redefining them in the
> bashrc files, but what I'd rather do is exclude all except those I want
> included, in case some
> software installs new ones.
>
The trailing backslashes aren't necessary. I've removed them in my LIB and
INCLUDE environment variables and VC works just fine. You could try removing
them and see if that fixes the perl build.
--Rick
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -