From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: 'Jonathan Larmour' <jlarmour@redhat.com>, amassa@cts.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] Re: Networking Help
Date: Tue, 24 Oct 2000 21:22:00 -0000 [thread overview]
Message-ID: <5AF611D83988D4118ACF00E0B10400540557E2@mr-intranet.sdesigns.net> (raw)
> > After that I get a conflict which states:
> >
> > Requires constraint not satisfied: CYGBLD_ISO_BSDTYPES_HEADER ==
> > "<sys/bsdtypes.h>"
> >
> > What do I need to change to correct this?
>
> Click Continue? If that doesn't work, just update the value
> of the option
> by hand.
I got the same problem in several occasions. It seems that the configuration
tools is not abble to resolve conflicts which involve a string value.
--
Fabrice Gautier
fabrice_gautier@sdesigns.com
next reply other threads:[~2000-10-24 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 21:22 Fabrice Gautier [this message]
2000-10-25 4:31 ` Hugo Tyson
2000-10-25 5:25 ` Bart Veer
-- strict thread matches above, loose matches on Subject: below --
2000-10-24 11:28 [ECOS] " amassa
2000-10-24 11:57 ` [ECOS] " Jonathan Larmour
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=5AF611D83988D4118ACF00E0B10400540557E2@mr-intranet.sdesigns.net \
--to=fabrice_gautier@sdesigns.com \
--cc=amassa@cts.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@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).