On Sat, Sep 07, 2002 at 04:12:54PM -0400, Jack Howarth wrote: > Hello, > As an aid to those arches which haven't yet clearly determined if > they need to add a libgcc-compat for run-time resolution of the newly > .hidden libgcc symbols, I have created a perl script to gather these > symbols. Whether you can find all the symbols with it may be effected > by how many binaries/libraries you have available to search. However > it should at least clarify which arches need a libgcc-compat file added. > The perl script is based on the following assumptions > > 1) that only defined internal symbols in libgcc_s.so.1 are of interest > 2) that "frame" related libgcc symbols can be ignored as they arrived > after the .hidden change > 3) that of the files to be searched for these symbols, those compiled > with c++ (as determined by libstdc++ linkage) can be ignored > 4) likewise libgcj.so and libstdc++ themselves as c++ code can be > ignored. > > To run the program, place it in a directory with write access and > execute it. When finished you will have a list of candidate symbols > for libgcc-compat in final.list and a list of their occurrences in > the files searched in found.list. If anyone finds any flaws in this > search approach let me know and I'll see if I can fix it.
Jack, While you're here, do you think you could make the script operate on .deb's? It's easy enough - accept a list of packages on STDIN, unpack them with dpkg-deb. Then we could run it over the archive directly. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
