public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] eCos arm-eabi GNU tools - test release 4.6.3-20120315
Date: Mon, 19 Mar 2012 08:19:00 -0000	[thread overview]
Message-ID: <4F66EBDB.3010008@televic.com> (raw)
In-Reply-To: <4F660861.8050705@dallaway.org.uk>

On 03/18/2012 05:08 PM, John Dallaway wrote:
>
> I have generated a new test release of the GNU tools for ARM targets
> based on GCC 4.6.3. The new test release avoids issues with GCC 4.6.2. 
> Ref:
>
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001468#c30
>
I am testing 4.6.2 (AT91SAM9260 platform), and will try 4.6.3 to go on 
(ecos 3.0 builds OK, but our application fails).
But when I want to see those "issues with GCC 4.6.2", I get this:

     You are not authorized to access bug #1001468.

(I can see other bugs.)
Why is this? Maybe something wrong with my account, because when I go to 
my 'permissions tab', I get this:

     There are no permission bits set on your account.

Regards,
Jürgen
>
>
> These tools are intended for testing within the eCos community. The test
> builds can be downloaded from the eCos ftp site and are located under
> the "gnutools" directory:
>
> Cygwin-hosted:
> gnutools/cygwin/test/ecos-gnutools-arm-eabi-20120315.cygwin.tar.bz2
>
> Linux-hosted:
> gnutools/i386linux/test/ecos-gnutools-arm-eabi-20120315.i386linux.tar.bz2
>
> Please use a mirror site in your own geographical region to access these
> files. Sites which mirror the eCos ftp area are listed at:
>
> http://ecos.sourceware.org/mirror.html
>
> The tools may be extracted into the current working directory from the
> downloaded archive files by using one of the following commands at a
> bash prompt:
>
>   tar jxvf ecos-gnutools-arm-eabi-20120315.cygwin.tar.bz2
>   tar jxvf ecos-gnutools-arm-eabi-20120315.i386linux.tar.bz2
>
> The Linux-hosted tools should work on most Linux distributions. The
> Cygwin-hosted tools require a recent Cygwin installation including the
> "libexpat1" and "libmpc1" packages.
>
> The patches used in generating the 4.6.3-20120315 test toolchain are
> identical to those applied for the previous test release (4.6.2-20120125).
>
> When connecting to Cortex-M targets using the build of arm-eabi-gdb
> within this toolchain, you may observe an error message:
>
>   Remote 'g' packet reply is too long
>
> In such cases, it will be necessary to use a GDB target description file
> as a workaround. A suitable target description file is available at:
>
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001524#c1
>
> Jifl has developed a patch for this issue and we will be patching GDB in
> a subsequent build of the toolchain.
>
> Thank you for your feedback on the previous test release tooclhain. Your
> feedback on this new test release is also welcome. Please report any
> issues at:
>
> http://bugs.ecos.sourceware.org
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>


-- 
Jürgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2012-03-19  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18 16:08 John Dallaway
2012-03-19  8:19 ` Lambrecht Jürgen [this message]
2012-03-19  8:53   ` Ilija Kocho
2012-03-19  8:53   ` Ilija Kocho

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=4F66EBDB.3010008@televic.com \
    --to=j.lambrecht@televic.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).