Re: [Tack-devel] ACK compiles on NetBSD-macppc, sort of...

[Gregory T. (t. K. <gt...@di...>]

At 9:52 AM -0400 7/21/06, Perry E. Metzger wrote:
>> Ok, I understood the chain of events to be GNUC was not defined and
>> neither was __lint__, thereby coming to "No function renaming
>> possible." 
>
>Correct. We're not running something GCC compatible, and we're not
>running lint, so there is no implemented version of the symbol
>renaming macros. If you implemented enough of the GCC stuff to do
>symbol renaming, you could lie and define __GNUC__. Really, though,
>that is only safe if you define all the gcc extensions. However, if
>ACK handled renaming, it would be fine to edit the include file to say
>__GNUC__ or __ACK__ or something similar.

Now, is this occuring because at this point (when the compiler messages occur), ACK has taken over and is starting to build the toolchain (bootstrapped)?  If so, then I understand the need for ELF output at this point.

If the answer is yes, and ACK take over so soon, my next question would be to David Given, asking how was this handled in the Linux port?

thanks for your patience,
tim

Gregory T. (tim) Kelly
Owner
Dialectronics.com

P.O. Box 606
Newberry, SC 29108

"Anything war can do, peace can do better."  -- Bishop Desmond Tutu