From: Harry Putnam <reader@newsguy.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to point an emacs build to gif libs
Date: Fri, 23 Jan 2015 10:26:36 -0500 [thread overview]
Message-ID: <874mrhzff7.fsf@reader.local.lan> (raw)
In-Reply-To: 87bnlpzql5.fsf@reader.local.lan
Harry Putnam <reader@newsguy.com> writes:
> Everywhere you see that word will be info telling what lib is not
> being found. Once you know what lib... its short work to:
>
> find /suspected/path/base/ -name '*lib_named_at_perhaps*'
>
> And thereby find the correct paths to add. to PKG_CONFIG_PATH
I may have jumped the gun before testing ... I still haven't managed
to get ./configure to accept --with-gif=yes. In fact some of my
concoctions have broke the configure run entirely. for example:
It really is not thoroughly explained (nor should it be) in the
install file, just how to do this.. there are examples which I tried
to follow:
./configure --prefix=/usr/local/src/vcs/git/test --with-x=yes\
--with-gif=yes --with-imagemagick=yes --with-x-toolkit=athena\
--without-sound --disable-largefile
CPPFLAGS='-I/opt/csw/include'\
LDFLAGS="-L/opt/csw/lib -L/opt/csw/lib/amd64/" CFLAGS='-03'
(It's all one line on the cmd line)
Leads to a very short run of configure.. some 12-13 lines... Now it
cannot find the compiler... something it knew a few moments
ago... somehow my illinformed flags have rendered ./configure dumber
than with no flags
checking for xcrun... no
checking for GNU Make... make
checking for a BSD-compatible install... /usr/gnu/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/gnu/bin/mkdir -p
checking for gawk... gawk
checking whether make supports nested variables... (cached) yes
checking build system type... i386-pc-solaris2.11
checking host system type... i386-pc-solaris2.11
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/usr/local/src/vcs/git/emacs':
configure: error: C compiler cannot create executables
See `config.log' for more details
I've tried a few other concoctions too, which ended better than the
above run, but have yet to get configure to find the gif libs.
Again, I'm not particularly wedded to gif support... just would
finally like to know how set things up when a default ./configure run
doesn't cut it.
I've dug up some help on google and tried a run after reading a few
bits about it... it didn't wash out totally but still did not find or
use gif libs.
I believe the needed items are here:
find /opt/csw/ -name 'include'
/opt/csw/include
[...] trimmed out doco under ../share/..
/opt/csw/include/gif_lib.h
/opt/csw/lib/libgif.so.4.1.7
/opt/csw/lib/libgif.so
/opt/csw/lib/libungif.so.4
/opt/csw/lib/amd64/libgif.so.4
Can you suggest where I might find some more detailed info about how
those flags are actually set?
next prev parent reply other threads:[~2015-01-23 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 17:58 How to point an emacs build to gif libs Harry Putnam
2015-01-23 2:01 ` Glenn Morris
2015-01-23 11:25 ` Harry Putnam
2015-01-23 15:26 ` Harry Putnam [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-20 21:40 Harry Putnam
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mrhzff7.fsf@reader.local.lan \
--to=reader@newsguy.com \
--cc=help-gnu-emacs@gnu.org \
/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).