> How about this patch? Shouldn't this be handled in configure? It should *know* which libiberty we're going to need, right? The build would also do the right thing (i.e. stop) if libiberty.a is missing but *supposed* to be there. And if configure is handling it, why use -l at all? Why not just list ../libiberty/libiberty.a in LIBADD?