http://bugs.codeweavers.com/show_bug.cgi?id=577
*** shadow/577 Tue Apr 16 04:27:35 2002 --- shadow/577.tmp.11572 Tue Apr 16 04:27:35 2002 *************** *** 0 **** --- 1,37 ---- + +============================================================================+ + | messup in ./tools/wineinstall -- hangs/dies | + +----------------------------------------------------------------------------+ + | Bug #: 577 Product: Wine | + | Status: UNCONFIRMED Version: unspecified | + | Resolution: Platform: | + | Severity: normal OS/Version: All | + | Priority: P1 Component: wine-tools | + +----------------------------------------------------------------------------+ + | Assigned To: wine-bugs@winehq.com | + | Reported By: sgeier@caltech.edu | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | Milestone: TargetMilestone: --- | + | URL: | + +============================================================================+ + | DESCRIPTION | + This is in re: wine-20020411 -- the documentation suggests using ./tools/wineinstall instead of a manual + config/make. Running this seems to work OK until it tells me that it has created a local conf-file but that I + should check it that it's OK. Then it hangs. No response to a return or anything. + + Reason is line 581 in in the wineinstall-script: + + CROOT=`sed -n '/^[Drive C]$/,/^[.*]$/ s/^Path=(.*)/\1/p' $CONF` + + This is screwed in more than one way, the most obvious being that there is no variable with the name $CONF, + there's a reference to a global and a local conf file $LCONF and $GCONF but there's no $CONF. This means that + sed will wait for input from stdin and hence the user can type whatever he wants... + + There's also something fishy with the sed-expression itself - I don't really speak sed, but piping my + ~/.wine/config file which contains the following two lines + [Drive C] + "Path" = "/dos" + into that sed-statement returns an empty string, not "/dos" as one would expect. + + I did a "make install" by hand at that point and it seems mostly OK. Buncha stuff still buggy, but I'll do a + real bug-report for that... \ No newline at end of file