Benjamin Reed <[EMAIL PROTECTED]> wrote:
> tom sgouros wrote:
>
> > I also tried this:
> > ~> cd /usr/lib
> > /usr/lib> find . -type f -exec otool -Iv \{\} \; -print >~/trash1
> > /usr/lib> cd /sw/lib
> > /sw/lib> find . -type f -exec otool -Iv \{\} \; -print>>~/trash1
> > /sw/lib> cd
> > ~> grep qInitImages_designercore trash1
> > ~>
>
> there was a bad qt way back in the day that installed things in /lib --
> might want to check there as well...
No /lib on this system, but I also looked in /usr/local/lib, with the
same negative result. What is the theory behind thinking that having a
bad library would cause an "undefined symbol" error? I'm not sure I get
that. Is the idea that some early stage of the compile would find that
symbol and therefore not include it in some library?
Thanks,
-tom
--
------------------------
tomfool at as220 dot org
http://sgouros.com
http://whatcheer.net
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
