On Mon, Feb 22, 2010 at 7:17 AM, Brian Paul <brian.e.p...@gmail.com> wrote:
> On Sun, Feb 21, 2010 at 5:54 PM, Dan Nicholson <dbn.li...@gmail.com> wrote:
>> On Sun, Feb 21, 2010 at 2:33 PM, Keith Packard <kei...@keithp.com> wrote:
>>> The bash 'cd' command tends to emit random stuff to stdout when the
>>> CDPATH variable is set, so clear it to keep extra filenames from being
>>> emitted from the expand_archive function, which would otherwise cause
>>> mklib to fail.
>>>
>>> Signed-off-by: Keith Packard <kei...@keithp.com>
>>
>> Congratulations on wading in to mklib, it's not a friendly place. :)
>
> Heh, I guess you've never had to debug libtool then.  mklib is a walk
> in the park by comparison.

Sorry, didn't mean to imply that it's simplicity is not a virtue. On
the other hand, it doesn't get a ton of love, so it tends to be pretty
incoherent. libtool debugging is an absolute nightmare, but thankfully
it's been a long time since most people had to deal with that.

--
Dan

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to