Linux, PowerPC and -fvtable-thunks

H.J. Lu hjl@lucon.org
Sat Nov 22 00:42:00 GMT 1997


> are if you had bothered to take the time to do the same, then this problem
> would have been fixed by now.
> 

If I were asked directly about that patch, I would have
explained it. But I thought it was quite obvious that
--enable-shared would include the seond config file on
many platforms.

One more thing, will there be a libstdc++ 2.8 for gcc
2.8? If the answer is yes, $(CC) should be used for
making libstdc++.so in libstdc++/Makefile.in, instead
of $(CXX).


> It's definitely too late to go back and include your patch for the release.
> 
> 
> Can we come up with a less intrusive way to fix this problem?
> 
> Seems to me that we could add something like this after the alpha/linux
> line in the shared case
> 
>    *-*-linux*)	target_makefile_frag=config/mt-${target_cpu}linuxpic
> 
> Or something similar.  We then need a few linuxpic files.
> 

I am not sure if it is a good idea. I tend to think it may
cause more trouble than my old patch. The problem happens
when you have more than one config files. In my case, it
is --enable-shared. You don't want linuxpic if --enable-shared
is not used. To do it right, you should support multiple
config files.

BTW, if you take time to have a close look at my patch, you
may find it quite reasonable. My patch just allows multiple
config files.


H.J.



More information about the Gcc mailing list