This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Results for binutils 20021028 cvs 2.13 branch testsuite on sparc64-unknown-linux-gnu
On Tue, Oct 29, 2002 at 08:17:28AM +0100, Christian Jönsson wrote:
> On Mon, Oct 28, 2002 at 04:28:22PM -0500, Daniel Jacobowitz wrote:
> > On Mon, Oct 28, 2002 at 10:13:50PM +0100, Christian Jönsson wrote:
> > > On Mon, Oct 28, 2002 at 04:09:33PM -0500, Daniel Jacobowitz wrote:
> > > > On Mon, Oct 28, 2002 at 10:06:57PM +0100, Christian Jönsson wrote:
> > > > > On Mon, Oct 28, 2002 at 03:27:11PM -0500, Daniel Jacobowitz wrote:
> > > > > > On Mon, Oct 28, 2002 at 09:22:45PM +0100, Christian Jönsson wrote:
> > > > > > > === ld Summary for unix/-fpic ===
> > > > > > >
> > > > > > > # of expected passes 63
> > > > > > > # of unexpected failures 62
> > > > > > > # of expected failures 11
> > > > > >
> > > > > > I explained all or most of these on the list this morning. It's bison
> > > > > > at work.
> > > > >
> > > > > but I have bison 1.35 insatlled on this system...
> > > >
> > > > Is /usr/bin/bison 1.35?
> > >
> > > uhm, yes...
> > >
> > > chj@fw:~$ /usr/bin/bison --version
> > > bison (GNU Bison) 1.35
> >
> > You'll have to give us some more details then.
> >
> > I'm still not entirely convinced that your problems are a bug in the
> > tools instead of your local configuration...
>
> Sure, I'd be happy to. I'll attach the log file of dejagnu for the
> unexpected ld failuers for sparc64-linux.
>
> hmm,
>
> (1) libc was not the lib64 one...
>
> (2) elf32-sparc insetad of elf64-sparc in some files...
>
> I'll rerun the build now with env LD_LIBRARY_PATH=/lib64 to make a few
> linker failures go away I guess... but what about the elf32-sparc issues?
>
hmm, I used this configury instead:
env LD_LIBRARY_PATH=/usr/lib64 \
/usr/local/src/gcc-binutils/branch/src/configure \
sparc64-linux --prefix=/usr/local/gcc-binutils \
--enable-shared --enable-threads=posix >& configure.log;
(i.e., the env LD_LIBRARY_PATH is added...)
but, to my surprise, this was not used when running the test suite
AFAICT...
So, same test results.
Cheers,
/ChJ