Subject:
|
Re: BricxCC-brickOS (bash) interoperability problems
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Tue, 19 Feb 2008 16:01:00 GMT
|
Viewed:
|
20420 times
|
| |
|
|
In lugnet.robotics.rcx, Paco Balbas wrote:
> After some investigation I have discovered the reason for that: a new behaviour
> of bash in the new cygwin together with the contents of the intermediate
> file.cmd.
Thank you very much for investigating this problem. I looked into it a while
back and was very puzzled as to why it no longer worked after I upgraded my
cygwin install. If I delete the EOL at the end of the command line it will
work?
> John (Hansen), I am wondering if you will be able to adapt BricxCC to the
> behaviour of current bash.
> Meanwhile I am still using the old one with BricxCC.
I will definitely fix BricxCC to work with the more recent bash version. Can
you verify that without the line ending character it still works with the old
version of bash?
John Hansen
|
|
Message has 1 Reply:
 | | Re: BricxCC-brickOS (bash) interoperability problems
|
| (...) Yes, I have verified that removing the end of line char in the command line, the old bash is also working normaly. To test that I am executing the following in a windows command terminal: D:>bash file.cmd I am not sure if BricxCC is executing (...) (17 years ago, 20-Feb-08, to lugnet.robotics.rcx)
|
Message is in Reply To:
| | BricxCC-brickOS (bash) interoperability problems
|
| Hi all. I am using BicxCC versión 3.3.7.17 with my RCX and brickOS. Recently I have updated my cygwin versión and now I am experiencing problems: I got the following general error trying to compile: "Compile Failed Unknown GNU error code (-1)" After (...) (17 years ago, 17-Feb-08, to lugnet.robotics.rcx)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
