initial feedback on *-rtems was [Fwd: binutils 2.12 is approaching]

initial feedback on *-rtems was [Fwd: binutils 2.12 is approaching]

[Joel Sherrill]

[-- Attachment #1: Type: text/plain, Size: 427 bytes --]


I am forwarding email from an RTEMS user who responded to my request
to test binutils in anticipation of the branch.

It looks like make doc hits a problem in a 
build/bfd/doc/targets.texi.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985

[-- Attachment #2: Type: message/rfc822, Size: 3491 bytes --]

From: Eric Norum <eric.norum@usask.ca>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: Re: binutils 2.12 is approaching
Date: Thu, 31 Jan 2002 09:40:48 -0600
Message-ID: <3C596580.3C9AB160@usask.ca>

Joel Sherrill wrote:
> 
> Hi,
> 
> An announcement recently was made to the binutils list that
> an attempt will be made to make a 2.12 branch in the next
> couple of weeks.  Feb 5 was mentioned as the target date.
> 
> If anyone wants to step up to the plate and help verify
> that the *-rtems targets are OK, it would be appreciated.
> 

I checked out the binutils source to my RedHat 7.2 Linux system last
night:
CVSROOT=:pserver:anoncvs@sources.redhat.com:/cvs/src cvs co  binutils

Things build properly, but the make install failed on the
documentation.  The build process creates build/bfd/doc/targets.texi
improperly (it creates a @code{xxxxx} directive with a / in place of the
terminating }).  The following script works around this problem.  I
can't imagine this problem being present this late in the development
cycle, so perhaps it's just something wrong with my Linux setup.  I
don't have time to dig any deeper.

Here's the offending line (line 203):
  /* Check the format of a file being read.  Return a @code{bfd_target
*/ or zero.  */
and here's what it looks like after my script fixes it
  /* Check the format of a file being read.  Return a @code{bfd_target
*} or zero.  */

==========================================================
#!/bin/sh

set -ex

for arch in m68k i386 ppc
do
        rm -rf build
        mkdir -p build
        cd build
        ../../src/configure --target=${arch}-rtems --prefix=/opt/rtems
        gmake -w
        gmake -w install || true
        sed '/Check the format of a file being read.  Return a/s/\/ or/}
or/' bfd/doc/targets.texi >jnk
        mv jnk bfd/doc/targets.texi
        gmake -w install
        cd ..
        rm -rf build
done
============================================================

Running the script gives me a working set of tools:

norume@norum1 230> m68k-rtems-ld --version
GNU ld version 2.11.93 20020131
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms
of
the GNU General Public License.  This program has absolutely no
warranty.

I've used the resulting binutils to build my RTEMS and EPICS
applications.  Everything seems to work.

-- 
Eric Norum                                 eric.norum@usask.ca
Department of Electrical Engineering       Phone: (306) 966-5394
University of Saskatchewan                 FAX:   (306) 966-5407
Saskatoon, Canada.

Re: initial feedback on *-rtems was [Fwd: binutils 2.12 is approaching]

[Nick Clifton]

Hi Joel,

> I am forwarding email from an RTEMS user who responded to my request 
> to test binutils in anticipation of the branch.
> 
> It looks like make doc hits a problem in a 
> build/bfd/doc/targets.texi.

I think Alan's recent patch fixed this.  It does not appear to happen
with today's sources.

Cheers
        Nick