public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: Andreas Schuldei <andreas@schuldei.org>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] ecos cvs problems
Date: Fri, 01 Dec 2000 15:56:00 -0000	[thread overview]
Message-ID: <3A283A8A.3DBF3DDF@cygnus.co.uk> (raw)
In-Reply-To: <20001202003824.A27821@sigrid.schuldei.com>

Andreas Schuldei wrote:
> 
> * Jonathan Larmour (jlarmour@cygnus.co.uk) [001202 00:33]:
> > > I got the up to date cvs snapshot of ecos and configured it (with problems
> > > with configure: it did not look for libs and includes well, but I fixed that).
> 
> Will you accept patches that are not needed under redhat? I had the feeling
> that the configure script is VERY specific where it expects things. Since I
> run Debian I had to make minior ajustments.

Absolutely. As long as they don't break under Red Hat ;).

Although if it's something to do with the location of your TCL
installation, it may be a non-issue - there are --with-tcl-header and
--with-tcl-lib arguments to configure you can use for that. But let's see
the patches anyway and we can decide. Do not send the patches to configure
or any similar generated files, i.e. send configure.in, not configure, etc.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  reply	other threads:[~2000-12-01 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-01 15:13 Andreas Schuldei
2000-12-01 15:30 ` Jonathan Larmour
2000-12-01 15:35   ` Andreas Schuldei
2000-12-01 15:56     ` Jonathan Larmour [this message]
2001-01-27 14:19   ` [ECOS] ecos-1.3.1/host/infra/hosttest.exp Andreas Schuldei
2001-01-29 10:30     ` 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=3A283A8A.3DBF3DDF@cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=andreas@schuldei.org \
    --cc=ecos-discuss@sourceware.cygnus.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).