Re: [Freemint-discuss] Debugging a problem in gcc-14

[Eero T. <oa...@he...>]

Hi,

On 3.6.2024 14.08, Thorsten Otto wrote:
> On Montag, 3. Juni 2024 11:50:57 CEST Eero Tamminen wrote:
>> tried "gcc hello.c" and it failed due to missing execve().
> 
> Actually mintlib tries its best to simulate the vfork()/execve thing even for
> TOS, but i think its not good enough for gcc's purpose. Amongst others, it
> also uses pipes for redirection. Most of the code for this is in libiberty
> (https://github.com/th-otto/m68k-atari-mint-gcc/blob/mint/gcc-13/libiberty/
> pex-unix.c)

The actual error is:
GEMDOS 0x4B Pexec(200, 0x3ef8a6, 0x3ef827, 0x3f051e) at PC 0x137C02
: error trying to exec '/usr/lib/gcc/m68k-atari-mintelf/14/collect2': 
execv: Function not implemented


> Another problem may be the symlinks for as, ld etc. in /usr/m68k-atari-
> mintelf/bin

Why they would be a problem?  With GEMDOS HD, all files appear as normal 
ones, and those names are unique within 8+3 chars.

As to content under /usr/lib/gcc/m68k-atari-mintelf/14/, "libstdc++.a" 
and "libstdc++exp.a" map to same 8+3 name, but if one knows whether code 
is built with exceptions, one can remove the non-relevant.

Compiling anything than minimal C++ code is unlikely to work though 
because there seem to be a lot of C++ headers which are not unique with 
first 8+3 chars.


	- Eero