cygport bug: doesn't understand "DOS" line endings

cygport bug: doesn't understand "DOS" line endings

[Steven Boswell II]

Hello, I was trying to build the waf cygport (i.e. http://sourceforge.net/p/cygwin-ports/waf/ci/master/tree/ ), and kept getting a cryptic error message:

*** ERROR: inherit: unknown cygclass python3

Since there was definitely a /usr/share/cygport/cygclass/python3.cygclass file, this made no sense to me.

I modified /usr/share/cygport/lib/inheritance.cygpart so that line 39 read

 error "inherit: unknown cygclass ${_privclassdir}/${classname}.cygclass WTF";

And got the interesting error message

.cygclass WTFherit: unknown cygclass /usr/share/cygport/cygclass/python3

That's when I realized that the CR character was being included in the module name.

I ran dos2unix on the .cygport file and all was well.

You may want to modify cygport to handle DOS-style line-endings.

Thanks,
Steven Boswell


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: cygport bug: doesn't understand "DOS" line endings

[Yaakov (Cygwin/X)]

On 2014-02-26 11:14, Steven Boswell II wrote:
> You may want to modify cygport to handle DOS-style line-endings.

cygport is a bash script, hence this applies:

http://cygwin.com/ml/cygwin-announce/2007-05/msg00003.html


Yaakov


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: cygport bug: doesn't understand "DOS" line endings

[Steven Boswell II]

>>*** ERROR: inherit: unknown cygclass python3
>>[...]
>> You may want to modify cygport to handle DOS-style line-endings.
>
>cygport is a bash script, hence this applies:
>
>http://cygwin.com/ml/cygwin-announce/2007-05/msg00003.html

Thanks for pointing that out.
I created a BASH_ENV environment variable in my .bashrc to point to "$HOME/.bash_env", then created a ".bash_env" file containing "set -o igncr", and now cygport doesn't error-out cryptically when presented with DOS-style line endings.

Sorry to trouble the mailing with with my dumb question.
If nothing else, anyone else running into this problem with cygport will be able to find a quick answer in a search engine.

Steven Boswell


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple