Hand-versioned symbols for frame_state changes

Alexandre Oliva oliva@lsd.ic.unicamp.br
Wed Dec 22 11:53:00 GMT 1999


On Dec 22, 1999, Chip Salzenberg <chip@valinux.com> wrote:

> According to Alexandre Oliva:
>> On Dec 21, 1999, Chip Salzenberg <chip@valinux.com> wrote:
>> > Now if I could only get libtool to understand what a version file is,
>> > I'd be golden.
>> 
>> Why does it have to?  Did you try -Wl,versionfilename ?

> No ... the docs for libtool claim that it would be ignored.

Indeed.  But it will only be ignored in libtool up to 1.3.4, and even
then, only when creating shared libraries, not when linking
executables.  In the next major release of libtool, -Wl and -Xlinker
will be supported, and will arrange for libtool to pass flags to the
linker (even if it calls the linker directly, instead of through the
compiler), and -Wc and -Xcompiler will be supported to do the
equivalent job of passing arguments to the compiler driver, unless it
is not used at all.

> After cogitating, though, I think I'd rather avoid the whole GLIBC_2.0
> issue by splitting frame.c into two parts, one of which is dependent
> on the layout of frame_state and one that isn't.

Sounds good.

> It would be even better if we could just revert frame_state to its old
> layout.

Indeed.

-- 
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them



More information about the Gcc-bugs mailing list