|
From: | Vadim V. Zhytnikov |
Subject: | Re: [Gcl-devel] Re: GCL problems with binutils 2.14.90.0.8 |
Date: | Sat, 21 Feb 2004 11:57:24 +0300 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU; rv:1.5) Gecko/20031006 |
Camm Maguire ?????:
Greetings! "Vadim V. Zhytnikov" <address@hidden> writes:Camm Maguire ?????:Greetings! Vadim, I'm rather suspect that binutils is the problem. This code is completely idle outside of 'load. Your problems are rather in compilation and running compiled code. Are you sure gcc/libc were not changed in the upgrade? In any case, I cannot reproduce this with the latest toolchain in Debian unstable, verified today. Try --enable-debug, see if the problem persists, then post a backtrace under gdb if so. If not, then its a gcc bug.I'm perfectly sure that only binutils are involved. Before upgrade I made backup copy of the system. So when I diskovered new troubles with GCL I restored the state before upgrade. Checked that GCL builds without trouble. Upgraded binutils/libbfd/libiberty _only_ and got the problem back. I'm especially puzzled by the filure of --enable-locbfd build. What parts of binutils are involved is such build? Only ld?Good question. I suppose you've checked that the locally compiled libs appear on the linker command line. If so, then yes, the only effect could be C compiler programs (dynamically) linking against lbfd and friends. You can pursue the gdb backtrace in this case if you wish. If for some reason the locally compiled libs are not used for you with --enable-locbfd, please let me know. Take care,
Some extra observations. I took directory with successful GCL build which was made before binutils upgrade (bunitils 2.14.90.0.6), and tried rebuild it but not from very beginning but starting with pcl. In other words I use old saved_gcl to build pcl and finally saved_ansi_gcl. Build succeeded. So problem lies already in saved_gcl not in later compile/link stages as it may seems at first. I've checked that lockbfd and custreloc GCL builds work to me as expected - locbfd is linked with locally compiled libbfd.a/libiberty.a and custreloc without libbfd/libiberty at all. But in spite of this all these types of GCL ANSI build - statsysbfd, locbfd, custreloc fail to me exactly at the same place if I use binutils 2.14.90.0.8. I'd be glad if someone with binutils 2.14.90.0.8 could confirm the problem. Unfortunately it seems that this binutils version is available only for Fedora 2 beta. I don't have this distro near at hand. The latest binutils in Debian testing/unstable are 2.14.90.0.7. I'm going to test the problem with --enable-debug but I'm not sure how to combine make build and gdb. Any ideas? Best wishes, -- Vadim V. Zhytnikov <address@hidden> <address@hidden>
[Prev in Thread] | Current Thread | [Next in Thread] |