public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Robin Farine <acnrf@dial.eunet.ch>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: Patch for x86 bootstrap
Date: Fri, 27 Apr 2001 01:29:00 -0000	[thread overview]
Message-ID: <86vgnq7o4j.fsf@halftrack.hq.acn-group.ch> (raw)
In-Reply-To: <20010426112108.A24912@buici.com>

elf@florence.buici.com writes:

> On Thu, Apr 26, 2001 at 06:55:09PM +0100, Jonathan Larmour wrote:
> > elf@florence.buici.com wrote:
> > > 
> > > On Thu, Apr 26, 2001 at 04:11:20AM +0100, Jonathan Larmour wrote:
> > > > Ah yes, of course. I forgot that one. You have to do a "ecosconfig
> > > > remove libc_signals".
> > > 
> > > And how am I supposed to guess this?
> > 
> > Not every consequence of changing your configuration can be documented!
> > Although the more tractable course of action would be to choose either the
> > "posix" or "elix" template instead of the default one, using
> > Build->Templates. That way the conflict doesn't arise.
> 
> I think you are missing my point.  The ecosconfig error message doesn't
> indicate the type of problem.  This is two-fold.
> 
>   C CYGPKG_POSIX, "requires" constraint not satisfied:
>   CYGBLD_ISO_SIGNAL_NUMBERS_HEADER == "<cyg/posix/signal.h>" C CYGPKG_POSIX,
>   "requires" constraint not satisfied: CYGBLD_ISO_SIGNAL_IMPL_HEADER ==
>   "<cyg/posix/signal.h>" C CYGINT_ISO_SIGNAL_NUMBERS, "requires" constraint
>   not satisfied: 1 >= CYGINT_ISO_SIGNAL_NUMBERS C CYGINT_ISO_SIGNAL_IMPL,
>   "requires" constraint not satisfied: 1 >= CYGINT_ISO_SIGNAL_IMPL
> 
> These errors don't give any hint that this might be a problem with multiple
> implementations.  I'd expect something like the Debian DEB format such as
> 
>   'signals' implementations conflict in
>     posix libc_signals

Right, this would help.

> 
> Second, it is unclear where these constants are defined so that I can discover
> the source of the unsatisfied constraints.  These are not present in the .ecc
> file, nor is there an indication of where to look.

From the package directory, you could try something like:

 find . \( -name '*.cdl' -exec grep CYGINT_ISO_SIGNAL_NUMBERS {} \; \) -exec ls \
 -ld {} \;

which produces:

      implements     CYGINT_ISO_SIGNAL_NUMBERS
  -rw-rw-r--    1 user  group      10116 Apr  9 15:48 \
  packages/compat/posix/current/cdl/posix.cdl
      requires        CYGINT_ISO_SIGNAL_NUMBERS
      default_value   { CYGINT_ISO_SIGNAL_NUMBERS != 0 && \
  -rw-rw-r--    1 user  group       4436 Mar  8 09:57 \
  packages/io/serial/current/cdl/termios.cdl
          cdl_interface CYGINT_ISO_SIGNAL_NUMBERS {
              requires      { 1 >= CYGINT_ISO_SIGNAL_NUMBERS }
  -rw-rw-r--    1 user  group      37273 Apr  9 15:50 \
  packages/isoinfra/current/cdl/isoinfra.cdl
      implements    CYGINT_ISO_SIGNAL_NUMBERS
  -rw-rw-r--    1 user  group      11273 Mar  8 09:57 \
  packages/language/c/libc/signals/current/cdl/signals.cdl

and then look in ecos.ecc to see which *active* package/component implements
CYGINT_ISO_SIGNAL_NUMBERS.


Robin

      reply	other threads:[~2001-04-27  1:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 19:18 [ECOS] " elf
2001-04-25  5:57 ` [ECOS] " Fabrice Gautier
2001-04-25 10:05   ` elf
2001-04-25 11:55     ` Fabrice Gautier
2001-04-25 12:25       ` elf
2001-04-25 15:42         ` Fabrice Gautier
2001-04-25 19:36           ` elf
     [not found]     ` <3AE710BB.568594BA@redhat.com>
     [not found]       ` <20010425110343.A14879@buici.com>
     [not found]         ` <3AE71269.3AA0AE00@redhat.com>
     [not found]           ` <20010425113613.A15225@buici.com>
     [not found]             ` <3AE71CD4.B4A4641D@redhat.com>
2001-04-25 12:23               ` elf
2001-04-25 13:34                 ` Jonathan Larmour
     [not found]                   ` <20010425192444.A17131@buici.com>
2001-04-25 20:11                     ` Jonathan Larmour
2001-04-25 23:36                       ` elf
2001-04-26 10:55                         ` Jonathan Larmour
2001-04-26 11:21                           ` elf
2001-04-27  1:29                             ` Robin Farine [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=86vgnq7o4j.fsf@halftrack.hq.acn-group.ch \
    --to=acnrf@dial.eunet.ch \
    --cc=ecos-discuss@sources.redhat.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).