default_secondary_reload: class vs scratch_class
DJ Delorie
dj@redhat.com
Wed May 10 21:26:00 GMT 2006
> I'd hesitate to apply patches to default_secondary_reload.
Even if it's wrong?
> If your port triggers any of the sanity checks, convert it to the
> new infrastructure, as it provides a much better interface.
In my case, I'm just trying to get the am33 port to function, because
I have some patches I need to test. I don't currently have the
resources to do that kind of change, and there are a *lot* of ports
that still use the macros.
More information about the Gcc
mailing list