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

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

Hi Perry,
I definately appreciate your feedback and help. =20

   #if !defined(_STANDALONE) && !defined(_KERNEL)
         #ifdef __GNUC__
           #define __RENAME(x)     ___RENAME(x)
        #else
            #ifdef __lint__
               #define __RENAME(x)     __symbolrename(x)
             #else
                #error "No function renaming possible"
           #endif /* __lint__ */
       #endif /* __GNUC__ */
     #else /* _STANDALONE || _KERNEL */
        #define __RENAME(x)     no renaming in kernel or standalone environm=
ent
    #endif

At 10:57 PM -0400 7/19/06, Perry E. Metzger wrote:
>Congratulations. You've hit NetBSD's symbol renaming stuff.
>
>Unfortunately, in order to handle API versioning, it is kind of
>necessary for whatever compiler one uses under NetBSD to be able to
>deal with symbol renaming in order to select the appropriate version
>of the C library call in question -- no versioning support means you
>have no hope at all of linking against our C library.

Is this specific to NetBSD?  Is there a POSIX-like standard that could be=
 applied to the solution, short of defining _STANDALONE?  I would like to=
 avoid implementing any *BSD specific code, to the exclusion of the other=
 BSDs (or additional work for them).  I'm also surmising that anything that=
 breaks ACK (TACK?) on Linux isn't going to get into the tree.

thanks,
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