zsh-workers
 help / color / mirror / code / Atom feed
From: "Vin Shelton" <acs@alumni.princeton.edu>
To: "Peter Stephenson" <pws@csr.com>
Cc: "River Tarnell" <river@wikimedia.org>,
	 "Zsh Hackers' List" <zsh-workers@sunsite.dk>
Subject: Re: [PATCH] 4.3.5 build fails on SunOS 4.1.4
Date: Mon, 3 Mar 2008 12:31:38 -0500	[thread overview]
Message-ID: <20a807210803030931h2a4520dcw8fed0e91dff23569@mail.gmail.com> (raw)
In-Reply-To: <20080303123622.169e55c8@news01>

On Mon, Mar 3, 2008 at 7:36 AM, Peter Stephenson <pws@csr.com> wrote:
> On Mon, 3 Mar 2008 04:58:15 +0000
>  River Tarnell <river@wikimedia.org> wrote:
>  >  + unless compiled with --disable-dynamic, any attempt to use
>  >    completion-related features crashes the shell with 'Undefined
>  >    symbol: _incompfunc'
>
>  I think the answer here is probably --disable-dynamic.  It's going back a
>  while, but I have a suspicion dynamic linking has always been problematic
>  on SunOS 4.  It might be fixable if anyone thought it worth while and had
>  the time and facilities.
>
>  For the specific problem, on some older systems an underscore needed to be
>  added by hand to entry points when fetching them with dlsym().  It looks
>  like this is some variant of that problem (although dlsym() isn't directly
>  involved).  Again, it's going back a bit and I'm not sure how this was
>  supposed to pan out.

Peter et al -

As you wrote, this is going back some ways (it's been *at least* 3
years since I built on a SunOS 4 platform) - I had to
--disable-dynamic in order to build a working zsh on SunOS4.  I recall
investigating further, but I never got the build to the point where
building with dynamic linking worked, IIRC.

  - Vin


      reply	other threads:[~2008-03-03 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03  4:58 River Tarnell
2008-03-03 12:36 ` Peter Stephenson
2008-03-03 17:31   ` Vin Shelton [this message]

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=20a807210803030931h2a4520dcw8fed0e91dff23569@mail.gmail.com \
    --to=acs@alumni.princeton.edu \
    --cc=pws@csr.com \
    --cc=river@wikimedia.org \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).