public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Building RedBoot for SH3 targets with new toolchain
Date: Thu, 22 Jan 2009 12:30:00 -0000	[thread overview]
Message-ID: <497866C6.80009@dallaway.org.uk> (raw)
In-Reply-To: <20090122103119.GG7080@donkey.ma.tech.ascom.ch>

Hi Andrew

Andrew Lunn wrote:

>> Taking all these things into account, plus the desire to avoid further
>> delays to the eCos 3.0 release, I think it preferable to stick with the
>> stock mpfr and gmp DLLs for the Cygwin-hosted toolchains. We must
>> document the need to install the relevant Cygwin packages though, and
>> add an entry to the FAQ.
> 
> Would it be possible to detect at build time if these DLLs are
> installed? But a custom build rule with the highest priority in infra,
> or HAL which will test if this files exist and stop and print an
> useful error message if they are not installed?
> 
> The way cygwin is silently failing is not nice...

The failure mode is certainly not nice. I expect that the mpfr and gmp
DLLs are loaded explicitly by the compiler using LoadLibrary() and
failure is not being reported at the application level.

We could emit a _warning_ message using a custom rule. An _error_
message would be too strong since older toolchains do not use mpfr and
gmp. However, it seems cleaner to keep such testing out of the build
process and perform the tests in the eCos install script instead when
the relevant toolchains are being installed. Having said that, I
appreciate that experienced eCos developers may not use the install script.

John Dallaway

  reply	other threads:[~2009-01-22 12:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 19:48 John Dallaway
2009-01-21 20:30 ` Jonathan Larmour
2009-01-21 22:08   ` John Dallaway
2009-01-21 22:33     ` Jonathan Larmour
2009-01-21 23:34       ` John Dallaway
2009-01-22  0:29         ` Jonathan Larmour
2009-01-22 10:15           ` John Dallaway
2009-01-22 10:31             ` Andrew Lunn
2009-01-22 12:30               ` John Dallaway [this message]
2009-01-22 14:40                 ` Bart Veer
2009-01-22 16:59                   ` John Dallaway

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=497866C6.80009@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.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 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).