From: Greg Shubin <gshubin@sonic.net>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Deborah.Bennett@eng.sun.com, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] trying to build ecosconfig for Solaris 7
Date: Tue, 12 Sep 2000 09:49:00 -0000 [thread overview]
Message-ID: <39BE6143.E4690B57@sonic.net> (raw)
In-Reply-To: <39BE2AA3.B97C85CA@redhat.com>
When I tried to build the ECOS tools on FreeBSD, I found that the configure
script makes a few (Linux-centric?) assumptions about where tcl is installed.
For one, it assumes a single version in a single location (e.g. /usr), where
the include and lib directories can be found.
tcl on FreeBSD allows for having several versions installed, so there are
sudirectories for the include and lib files, e.g. /usr/local/include/tcl8.0
and /usr/local/include/tcl8.2, and the same for the libraries.
Looking at our local Solaris (SunOS 5.1) it seems like there is a hybrid, i.e.
there is one /usr/loca/include/tcl.h, but there are several lib
subdirectories, /usr/local/lib/tcl8.x.
I started to play around with modifying configure, but then I found that
ecosconfig ran just fine under FreBSD's Linux compatiibility. It looked like
you could add a new variable for the library, something like 'with-tcl-lib',
and use 'with-tcl' for the include directory.
Jonathan Larmour wrote:
> Robert Swindells wrote:
> >
> > [Problems with building ecosconfig deleted]
> >
> > You need to build and install both infra and libcdl before building
> > ecosconfig itself.
> >
> > The configure script for ecosconfig assumes that all the headers have
> > been copied to /usr/local/include.
>
> That's odd, here (admittedly on Linux) I have no trouble doing:
>
> ~/sourceware/ecos/ecos/host/configure --with-tcl=PATHTOINSTALLEDTCL
> --with-tcl-version=8.2
> make
>
> Note that part of the configure output includes:
>
> make[3]: Entering directory `/local/pot/ecc-obj/native/x/infra'
> /usr/bin/install -c -m 644
> /home/jlarmour/sourceware/ecos/ecos/host/infra/infra.h pkgconf/inf
> ra.h
> /usr/bin/install -c -m 644 hostinfra.h pkgconf/hostinfra.h
> /usr/bin/install -c -m 644
> /home/jlarmour/sourceware/ecos/ecos/host/infra/cyg_type.h cyg/infr
> a/cyg_type.h
> /usr/bin/install -c -m 644
> /home/jlarmour/sourceware/ecos/ecos/host/infra/basetype.h cyg/hal/
> basetype.h
> /usr/bin/install -c -m 644
> /home/jlarmour/sourceware/ecos/ecos/host/infra/cyg_ass.h cyg/infra
> /cyg_ass.h
> c++ -Wall -Wpointer-arith -Wbad-function-cast -Wcast-qual
> -Wstrict-prototypes -Wmissing-proto
>
> 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
next prev parent reply other threads:[~2000-09-12 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200009120909.CAA20410@cygnus.com>
2000-09-12 6:07 ` Jonathan Larmour
2000-09-12 9:49 ` Greg Shubin [this message]
2000-09-12 10:06 ` Bart Veer
2000-09-12 9:54 ` Greg Shubin
2000-09-12 11:17 Deborah Bennett
-- strict thread matches above, loose matches on Subject: below --
2000-09-12 10:47 Deborah Bennett
2000-09-12 11:13 ` Greg Shubin
2000-09-12 9:42 Deborah Bennett
2000-09-12 10:27 ` Bart Veer
2000-09-11 19:08 Deborah Bennett
2000-09-12 2:09 ` Robert Swindells
2000-09-12 6:21 ` Bart Veer
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=39BE6143.E4690B57@sonic.net \
--to=gshubin@sonic.net \
--cc=Deborah.Bennett@eng.sun.com \
--cc=ecos-discuss@sources.redhat.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).