From: Bart Veer <bartv@redhat.com>
To: gshubin@sonic.net
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] trying to build ecosconfig for Solaris 7
Date: Tue, 12 Sep 2000 10:06:00 -0000 [thread overview]
Message-ID: <200009121706.SAA16781@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <39BE6143.E4690B57@sonic.net>
>>>>> "Greg" == Greg Shubin <gshubin@sonic.net> writes:
Greg> When I tried to build the ECOS tools on FreeBSD, I found
Greg> that the configure script makes a few (Linux-centric?)
Greg> assumptions about where tcl is installed. For one, it
Greg> assumes a single version in a single location (e.g. /usr),
Greg> where the include and lib directories can be found.
Greg> tcl on FreeBSD allows for having several versions installed,
Greg> so there are sudirectories for the include and lib files,
Greg> e.g. /usr/local/include/tcl8.0 and
Greg> /usr/local/include/tcl8.2, and the same for the libraries.
Greg> Looking at our local Solaris (SunOS 5.1) it seems like there
Greg> is a hybrid, i.e. there is one /usr/loca/include/tcl.h, but
Greg> there are several lib subdirectories, /usr/local/lib/tcl8.x.
Greg> I started to play around with modifying configure, but then
Greg> I found that ecosconfig ran just fine under FreBSD's Linux
Greg> compatiibility. It looked like you could add a new variable
Greg> for the library, something like 'with-tcl-lib', and use
Greg> 'with-tcl' for the include directory.
This has been raised before, see e.g. the thread
http://sources.redhat.com/ml/ecos-discuss/2000-06/msg00090.html
There are various complications caused by concurrent installs, the use
of symbolic links, subtly different conventions between Unix vs.
Windows vs. cygwin, and so on.
As long as the standard Tcl configure script has been used, if you
specify the same path for Tcl's --prefix and the eCos tools'
--with-tcl, everything should just work. On systems with an unusual
setup this might involve downloading and rebuilding Tcl.
The SunOS setup you describe actually looks right. There should be
/usr/local/include/tcl.h, a /usr/local/lib/libtcl.a (probably a
symbolic link to e.g. libtcl8.0.a), and a directory
/usr/local/lib/tcl8.0/ with auxiliary Tcl scripts. Specifying
--with-tcl=/usr/local should work just fine.
I also have some experimental patches to the relevant autoconf macro
and hence to the various configure scripts, to cope with more unusual
setups, but those are not ready for prime time yet.
Bart
next prev parent reply other threads:[~2000-09-12 10:06 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
2000-09-12 10:06 ` Bart Veer [this message]
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=200009121706.SAA16781@sheesh.cygnus.co.uk \
--to=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gshubin@sonic.net \
/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).