Re: [MiNT] How program CWD can change during appl_init() call?

["Helmut Karlowski" <helmut.karlowski@ish.de>]

Eero Tamminen, 09.01.2013 15:33:36:

> I've wondered about that too, why it needs multiple Return presses.
> As you can see from the sources, it's just a normal form_alert() call.
>
> GCC, binutils, GEMlib and MiNTlib used to build testgcc.prg are
> the latest ones from Sparemint:
> http://sparemint.org/sparemint/html/packages/gcc.html
> http://sparemint.org/sparemint/html/packages/binutils.html
> http://sparemint.org/sparemint/html/packages/gemlib.html
> http://sparemint.org/sparemint/html/packages/mintlib-devel.html
>
> Does the same problem happen if you build test.c with newer
> GCC/GEMlib/MiNTlib?

Same with gcc 4.5.2 from Alan and some recent libgem. But only the  
gcc-compiled one, and also when launched by XaAES. The vbcc-version does  
it also when it succeeds (launched by XaAES), so it's the alert itself.

Guess it's the 0:

                if(rsrc_load(RSCFILE)) {
                        form_alert(1, DLG_RSC_OK);

This works.

> AFAIK VBCC (libraries) don't have any calls to Dsetpath()
> and the test program definitely doesn't have them, so
> these calls are being done on the OS side.

They are only in the vbccc-version, what does not mean they come from the  
OS.
Maybe it's something with unixmode from mintlib's startup?

I'll see what happens in XaAES later.

--
Helmut Karlowski