zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
To: zsh-workers@sunsite.dk
Subject: help?  configure, non-standard prefix, linkage
Date: Sun, 3 Jun 2007 18:29:04 -0700	[thread overview]
Message-ID: <20070604012904.GA94660@redoubt.spodhuis.org> (raw)

I build test instances of zsh to install into --prefix=$HOME/dbg, a
hierarchy which I can safely annihilate at any time.  I manually force
in /usr/local/lib/ as a library search path so that libiconv is
available.

I also apply any autotools updates which FreeBSD's Ports collection
offers, as this normally reduces pain of the "your framework of hacks
upon hacks is too old, nyer nyer nyer" variety.  I especially come
up-to-date on these before installing security updates.  Being silly and
trusting, and valuing my time, I didn't regression-test build everything
after each individual update.

At some point, "something" has changed the linkage flags passed to zsh,
so that it's specifying the system LDFLAGS -L/usr/local/lib to the build
twice, the second time as a linker -Wl,-R/usr/local/lib; this means that
a zsh installed into ~/dbg can't find libzsh.

I've searched back through zsh CVS and it's now "broken" for versions
which previously installed fine, so I don't think that this is zsh
breakage.  It's something in my build environment.  I'm hoping that
someone here with more experience of autotools can point me at what I've
broken.  I've tried using v259 instead of v261 but whatever's changed is
broken in both.

Thanks,
-Phil

----------------------------8< cut here >8------------------------------
sed -i.bak '/auto/s/$/261/' .preconfig
sh ./.preconfig
zbuildopts=(
        --build=amd64-phil-freebsd62
        --with-curses-terminfo --with-tcsetpgrp
        --enable-etcdir=/etc --enable-function-subdirs
        --enable-zsh-mem --enable-zsh-secure-free
        --enable-zsh-debug --enable-zsh-mem-debug
        --enable-dynamic
        --enable-multibyte
        --enable-pcre
        --enable-site-fndir=/usr/local/share/zsh/site-functions
        )
CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib \
./configure $zbuildopts --prefix=$HOME/dbg \
        --enable-fndir=$HOME/dbg/share/zsh/zsh-phil-4.3.4/functions
----------------------------8< cut here >8------------------------------


                 reply	other threads:[~2007-06-04  1:29 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=20070604012904.GA94660@redoubt.spodhuis.org \
    --to=zsh-workers+phil.pennock@spodhuis.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).