You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

43 lines
1.4 KiB

From: aa8vb at vislab.epa.gov (Randall Hopper)
Date: Sat, 17 Apr 1999 15:23:44 GMT
Subject: Bug with makesetup on FreeBSD
In-Reply-To: <19990416215633.C2020@ipass.net>; from Randall Hopper on Fri, Apr 16, 1999 at 09:56:33PM -0400
References: <19990416143607.B1546743@vislab.epa.gov> <19990416215633.C2020@ipass.net>
Message-ID: <19990417112344.A1624668@vislab.epa.gov>
X-UID: 17
Andrew Csillag:
|Randall Hopper wrote:
|> Andrew Csillag:
|> |makesetup in Python 1.5.1 and 1.5.2 bombs on lines in the Setup file
|> |that use backslash continuation to break a module spec across lines on
|> |FreeBSD.
|>
|> BTW FWIW, I just built 1.5.2 last night on 3.0-RELEASE using the 1.5.2c1
|> port. Worked fine. But it may not invoke makesetup under the hood.
|
|It does invoke makesetup (that's how the Makefile in Modules gets
|written). I'm also running FreeBSD 2.2.8, so it may be a bug in /bin/sh
|that has been subsequently fixed... The quick test is to try this on
|your 3.0 machine
|
|$ read line
|some text here\
|
|On my 2.2.8 machine after I hit return after the \, I get a command line
|prompt, not a "blank prompt" that would mean that the read wasn't done.
It must be something else then, because here with stock Bourne shell:
|$ read line
|some text here\
|$ echo $line
|some text here\
I get the same behavior you describe, but no build breakage.
Randall