Dave Yeo | 4 May 2009 02:12

Re: Re: GCC 4.4.0 & binutils v2.19.1 available

On Sun, 03 May 2009 19:01:19 +1000, Andrew MacIntyre wrote:

>
>Dave Yeo wrote:
>
>> I'm still trying to get the fate suite to run on OS/2 and have got
>> quite a bit further then last we talked about it. Python doesn't seem
>> to like cmd.exe builtin commands
>
>Are you able to spell out a bit more about this issue?

The scripts etc are located at http://fate.multimedia.cx/running.html.
We need a newer python then yours for sqlite3 support.
I tried changing the compile line in fateconfig.py-example so the
beginning was
"rm -rf %BUILD_PATH% && mkdir %BUILD_PATH% && cd %BUILD_PATH% ...
The build would fail and %BUILD_PATH% was never created. Replacing
mkdir with /bin/mkdir fixed that. Unluckily it will not cd into
%BUILD_PATH%
I have tried various shells, different directory seperators and quoting
with a ^ without luck.
Finally had success by breaking the cd into multiple commands each not
having a path seperator ... cd fate && cd build ...

>
>BTW, anyone got any useful pointers to docs about the quoting rules used
>by cmd.exe?
>

Dave
(Continue reading)

Andrew MacIntyre | 5 May 2009 14:01
Picon
Picon

Re: Re: GCC 4.4.0 & binutils v2.19.1 available

Dave Yeo wrote:
> On Sun, 03 May 2009 19:01:19 +1000, Andrew MacIntyre wrote:
> 
>> Dave Yeo wrote:
>>
>>> I'm still trying to get the fate suite to run on OS/2 and have got
>>> quite a bit further then last we talked about it. Python doesn't seem
>>> to like cmd.exe builtin commands
>> Are you able to spell out a bit more about this issue?
> 
> The scripts etc are located at http://fate.multimedia.cx/running.html.
> We need a newer python then yours for sqlite3 support.
> I tried changing the compile line in fateconfig.py-example so the
> beginning was
> "rm -rf %BUILD_PATH% && mkdir %BUILD_PATH% && cd %BUILD_PATH% ...
> The build would fail and %BUILD_PATH% was never created. Replacing
> mkdir with /bin/mkdir fixed that. Unluckily it will not cd into
> %BUILD_PATH%
> I have tried various shells, different directory seperators and quoting
> with a ^ without luck.
> Finally had success by breaking the cd into multiple commands each not
> having a path seperator ... cd fate && cd build ...

Having been inside Python's subprocess standard library module recently,
I'm fairly confident that Python isn't the problem unless it relates to
choice of path separator.

I'm actually surprised in several ways by what you report:

- If I understand correctly, Paul's Python builds don't include any
(Continue reading)


Gmane