From: Neil Horman <nhorman@lvl7.com>
To: Magnus Damm <damm@opensource.se>
Cc: laurent.pinchart@capflow.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Development tools version
Date: Fri, 01 Mar 2002 07:32:59 -0500 [thread overview]
Message-ID: <3C7F74FB.1BC24793@lvl7.com> (raw)
In-Reply-To: 3C7F7319.1BCECF7E@opensource.se
Really! Is there a patch available or are the problems persistent? I ask
because we have had interesting behavior differences on occasion between
stripped and unstripped versions of some software we are working on. Thanks!
Neil :)
Magnus Damm wrote:
>
> FYI,
>
> strip in binutils-2.11.2 has problems...
> Not very important maybe, but annoying.
>
> http://sources.redhat.com/ml/bug-binutils/2001-q3/msg00108.html
>
> / magnus
>
> Neil Horman wrote:
> >
> > Yes, binutils 2.11.2. Sorry about my fat fingers... :)
> > Say....Speaking of those memory faults. I never got around to researching
> > them. Can you or anyone else provide general notes on exactly what those
> > patches fix? I'd certainly appreciate it, as I always wanted to track those
> > down, but never quite found the time. Thanks!
> >
> > Laurent Pinchart wrote:
> > >
> > > >
> > > >
> > > >I think that the Hard Hat tools will probably be the easiest for you to get up
> > > >and running with. They have probably been the most throughly debugged for the
> > > >8xx. Although if your looking to put together your own tools for the 860
> > > >series, we here have built the following, with a reasonably good deal of
> > > >success. See the notes for details:
> > > >
> > > >Binutils:
> > > > 2.1.2 - no problems at all. Download and build them for powerpc-linux and away
> > > >you go
> > > >
> > > >GCC:
> > > > 2.95.3 - again no real problems.
> > > >
> > > >GLIBC:
> > > > 2.2.4 - relatively easy. Some issues with memory faults on occasion, which I
> > > >have not yet traked down.
> > > >
> > > >GDB:
> > > > 5.1.1 - no problems
> > > >
> > > >General notes:
> > > > I've personally been following the embedded cross-gcc mini howto available on
> > > >penguinppc.com and I've been more or less happy with the results. hope that
> > > >helps!
> > > >
> > > Thanks Neil.
> > >
> > > I've been able to succesfully use the Hard Hat binaries (actually that's
> > > so simple that I wouldn't have dared asking questions in this mailing
> > > list if I hadn't :-), but I'd like to recompile from the sources, in
> > > order not to depend on a binary release, and also to be able to modify
> > > the tools if needed.
> > >
> > > I tried to compile the tools from the sources without patching them a
> > > few months ago, and experienced memory faults and a lot of other
> > > problems with dynamically linked executables (is that a known issue ?).
> > >
> > > Recompiling from the SRPMS shouldn't be a hard job, so that's what I'll
> > > try. All the patches are supposed to be included in there...
> > >
> > > Just to make sure, did you mean binutils 2.11.2 ?
> > >
> > > Laurent Pinchart
> >
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-03-01 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 13:45 Development tools version Laurent Pinchart
2002-02-28 14:24 ` Alex Zeffertt
[not found] ` <3C7E372A.7B4E5F0@lvl7.com>
[not found] ` <3C7F3507.1060702@capflow.com>
2002-03-01 11:30 ` Neil Horman
2002-03-01 12:24 ` Magnus Damm
2002-03-01 12:32 ` Neil Horman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C7F74FB.1BC24793@lvl7.com \
--to=nhorman@lvl7.com \
--cc=damm@opensource.se \
--cc=laurent.pinchart@capflow.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.