#184 Environment variable problems

MSYS (75)

Using MingW 2.0.0 and msys 1.0.8. OS: XP.

Output from "export" appended.

It's easiest to see the problem when starting cmd and
looking at the environment with set.

With the environment as given, the environment of cmd
will only hold a small subset, and will also have
garbage. (Also appended.)

After "export -n GNUSTEP_PATHPREFIX_LIST", cmd will get
a pretty much accurate copy of the environment.


  • Kai Henningsen

    Kai Henningsen - 2002-09-11

    Environment in Bash

  • Kai Henningsen

    Kai Henningsen - 2002-09-11

    Logged In: YES

    Here's the damaged environment

  • Kai Henningsen

    Kai Henningsen - 2002-09-11

    Damaged environment

  • Luke Dunstan

    Luke Dunstan - 2002-09-11

    Logged In: YES

    There is likely a bug or two here, but apart from that you
    seem to have many strange variable values. Firstly,
    CLASSPATH contains a Win32 path with embedded quotes
    (which seems incorrect and unnecessary), but the rest of
    the paths are POSIX and separated by colons. Since the
    JRE is a Windows program, it makes sense to only use
    Win32 paths with semicolon separators in the variable, or if
    you are relying on MSYS to translate it you need to at least
    use all POSIX paths.

    Your GNUSTEP_PATHPREFIX_LIST starts with "/C//msys":
    the double slash is incorrect so you might try changing it.
    GNUSTEP_USER_ROOT also contains double slashes, but
    in a Win32 path. GUILE_LOAD_PATH is made up of Win32
    paths with colon separators, which is also wrong: either
    change them to semicolons or POSIX paths (but not
    both :). LD_LIBRARY_PATH has the same problem. I
    expect many of these are based on GNUSTEP_USER_ROOT
    or something, so it explains why PATH again has double
    slashes. Finally, QTJAVA has embedded quotes too.

    If fixing any of these changes the output, it may help with
    finding bugs in MSYS.

  • Kai Henningsen

    Kai Henningsen - 2002-09-11

    Logged In: YES

    Further testing shows that *any* environment variable which
    contains what looks like a msys-format PATH will cause this
    behaviour. It does not seem to happen if it does not contain
    a ":" path separator.

    Puzzling is that all these will be translated to Windows
    format, but looking into the mingw/msys sources I can't find
    a corresponding source. The source there suggests that only
    selected variables should be translated.

    As to the weird Windows variables, well, these happen to be
    in the generic Windows environment before msys starts. I
    really doubt they have anything to do with this - it is too
    obviously connected to path translation.

  • Earnie Boyd

    Earnie Boyd - 2003-01-03

    Logged In: YES

    As far as I know this has been resolved. If not, please reopen.


  • Earnie Boyd

    Earnie Boyd - 2003-01-03
    • labels: --> MSYS
    • assigned_to: nobody --> earnie
    • status: open --> closed-fixed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks