public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "Trenton D. Adams" <tadams@theone.dnsalias.com>
Cc: 'eCos Disuss' <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] CONFLICTS that SHOULD be!
Date: Thu, 16 Aug 2001 16:01:00 -0000	[thread overview]
Message-ID: <3B7C50B9.83E43B72@redhat.com> (raw)
In-Reply-To: <000701c12699$2dc520b0$090110ac@TRENT>

"Trenton D. Adams" wrote:
> 
> The following two items were required by the File I/O package.  When I
> removed that package they were not disabled.  As a result I got an error
> saying that the file or directory didn't exist.  In particular,
> <cyg/posix/signal.h>.
> CYGBLD_ISO_SIGNAL_NUMBERS_HEADER
> CYGBLD_ISO_SIGNAL_IMPL_HEADER
> 
> The following two items were required by another package which I think
> was File I/O as well.  When I removed the package they were not
> disabled.  As a result I got an error saying that the file or directory
> didn't exist.  In particular, <cyg/posix/limits.h> and/or
> <cyg/fileio/limits.h>
> CYGBLD_ISO_POSIX_LIMITS_HEADER
> CYGBLD_ISO_OPEN_MAX_HEADER
> 
> To be or not to be, that is the question!

Hmmm... yes, it would do that. This is an old chestnut that has caught us
out even internally before: should values be reinferred every time
something changes. Or perhaps even just when the user explicitly wants.
Right now we do neither :-|.

I think we should at least allow the user to force a reinference. However
customers tend not to pay for host tools, so very little development gets
done except in "spare time", so I don't know when that would appear. Sorry.
Of course, you have the source :).

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

      reply	other threads:[~2001-08-16 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16 14:20 Trenton D. Adams
2001-08-16 16:01 ` Jonathan Larmour [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=3B7C50B9.83E43B72@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=tadams@theone.dnsalias.com \
    /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).