[MacPorts] #42375: i386-elf-gcc error while compiling: cannot find crt0.o

[MacPorts]

#42375: i386-elf-gcc error while compiling:  cannot find crt0.o
----------------------------+----------------------
  Reporter:  waves_no.13@…  |      Owner:  (none)
      Type:  defect         |     Status:  assigned
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.2.1
Resolution:                 |   Keywords:
      Port:  i386-elf-gcc   |
----------------------------+----------------------
Changes (by ryandesign):

 * cc: raimue (added)


Comment:

 What I'm getting at is: why are the different cross-compiler ports so
 different from another? Why is x86_64-w64-mingw32-gcc set up with so many
 different dependency ports whereas i386-elf-gcc is self-contained? Is it
 just that different maintainers have been interested in only some of the
 cross-compiler ports, and so some of them have evolved in ways that others
 haven't? Intuitively, I had expected all of the cross-compiler ports to be
 set up more or less identically, and the existence of the crossgcc-1.0
 portgroup reinforced that expectation for me. But now that I look into it
 I see that 4 of the 5 arm-*-gcc* ports, for example, don't even use that
 portgroup. And i386-elf-gcc, the port I'm interested in and which uses the
 portgroup in what looks like an extremely straightforward way and which I
 had hoped would be the way that all of the cross-compiler ports would be
 set up, is one of the ones that doesn't actually work.

 Rainer, it looks like you're the one developed the crossgcc-1.0 portgroup
 and switched i386-elf-gcc over to using it in
 [791eb1dd78775905d3614bff20303d9fb6005ecd/macports-ports] (#37260). Do you
 remember whether the port still worked correctly after this change back
 then? Do you have any suggestions on how to fix it now?

-- 
Ticket URL: <https://trac.macports.org/ticket/42375#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS