From: ceo@shore.net
To: sourcenav@sources.redhat.com
Subject: Building on FreeBSD 3.2: Success!!
Date: Sat, 25 Nov 2000 17:55:00 -0000 [thread overview]
Message-ID: <3A2065DA.A0DC3EA2@shore.net> (raw)
After a lot of excellent help from Ben Elliston and other folks here,
and some poking around in configure.in files, I finally figured it out.
The problem was that the uname command on the machine I was building on
produces highly nonstandard output, as it's my development machine at
work, and my employer's products are based on a somewhat modified
version of FreeBSD. Configure uses uname to figure out where various
system calls live, including the ones dealing with dynamic libraries
(dlopen() etc.). This meant it was unable to find those libraries, and
hence the build failed.
I hard-coded the $system variable in
SN452-source/tcl8.1/unix/configure.in (line 728) to "FreeBSD-3.2", reran
autoconf, deletd config.cache, and it configured and build perfectly.
Haven't had a chance to play around with it much, as I'm logged in from
home, and running large X apps over my 56K on a *very* good day wet
string is not one of life's more rewarding experiences.
Many thanks to all who helped.
--
-Chip Olson. | ceo@shore.net
reply other threads:[~2000-11-25 17:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A2065DA.A0DC3EA2@shore.net \
--to=ceo@shore.net \
--cc=sourcenav@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).