Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Craig McGeachie" To: cygwin AT cygwin DOT com Date: Mon, 09 Dec 2002 19:06:06 +1300 MIME-Version: 1.0 Subject: GDB version of libbfd.a links to libintl.a incorrectly Message-ID: <3DF4E99E.28514.BA9608F@localhost> Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body I have been building cygwin, and after a reinstall of the complete toolkit, I have run into problems rebuilding. Only dumper.exe had problems. I have resolved it, sort of. In the process of linking dumper.exe, libbfd.a gets brought in, and it brings in _dcgettext from libintl.a. Or rather that's what it should bring in. In fact it brings in _dcgettext__, which used to be the internal name which was aliased to _dcgettext__. (note for pedents, I am playing fast and loose with the fact that the leading _ is an artifact of the compiler the standard C calling convention) The resolution is that libbfd.a is included in both the gdb-20010428-3 and binutils-20021117-1 packages. The gdb version of libbfd.a wrongly imports _dcgettext__, and the binutils version correctly imports _dcgettext. By reinstalling the binutils package, and overwriting the gdb version of libbfd.a, problem solved. ----------------+------------------------------------------------- Craig McGeachie | #include +64(21)037-6917 | while (!inebriated) c2h5oh=(++bottle)->contents; ----------------+------------------------------------------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/