[gccsdk] [GCCSDK commit] lee - r2575 - trunk/gcc4/recipe/files/libunixlib

John Tytgat John.Tytgat at aaug.net
Sat Mar 31 06:45:49 PDT 2007


In message <E1HXO3L-0007vh-Rh at riscos.info> you wrote:

> Added: trunk/gcc4/recipe/files/libunixlib/vscript
> ===================================================================
> --- trunk/gcc4/recipe/files/libunixlib/vscript	                        (rev 0)
> +++ trunk/gcc4/recipe/files/libunixlib/vscript	2007-03-30 20:50:30 UTC (rev 2575)
> @@ -0,0 +1,160 @@
> +VERSION {
> +    /* The following symbols are global in the library, but they
> +    shouldn't be visible outside it as they are not part of its
> +    API. This is the equivalent of declaring them hidden and means
> +    that an entry is not generated for them in the PLT. */
> +
> +    local:
> +     __addenv;
> +     __addenv_to_env;
> [...]

What about the following idea: to have this file automatically generated
based on a macro in the c & s source files in the neighberhood where those
symbols are defined.  And those macros expand to nothing (so during building
there is no effect).  Would be easier to keep this file up-to-date, no ?

In case we're persuing this idea further: I would move the Perl script
reconf-libunixlib-01 to recipe/files/libunixlib and have this and the
above mentioned suggestion for a new script be called by a new
reconf-libunixlib-01.  I don't think it was a good idea of me to have that
Perl script living outside the libunixlib directory.

John.
-- 
John Tytgat, in his comfy chair at home                                 BASS
John.Tytgat at aaug.net                             ARM powered, RISC OS driven




More information about the gcc mailing list