all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: emacs 21.2 make crashes
Date: Tue, 03 Sep 2002 15:06:12 +0200	[thread overview]
Message-ID: <vafd6rv9q9n.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: mailman.1031051295.13026.help-gnu-emacs@gnu.org

Pieter Donche <Pieter.Donche@ua.ac.be> writes:

> I have SUN Blade 2000, Solaris 2.9, gcc-3.2, trying to install emacs-21.2
> # ./configure
> # make
> ...
>      ../lwlib/liblw.a -L/usr/openwin/lib  -lXaw3d -lXmu -lXt -lSM -lICE -lXext
> -ltiff  -lpng -lz -lm  -lXpm -lX11    -lsocket -lnsl -lkstat  -lcurses   -lm
> xfns.o: In function `tiff_load':
> /home/wins/builds/src/gnu/emacs-21.2/src/xfns.c:9537: undefined reference to `T
> IFFClientOpen'
> collect2: ld returned 1 exit status
> make[1]: *** [temacs] Error 1
> make[1]: Leaving directory `/home/wins/builds/src/gnu/emacs-21.2/src'
> make: *** [src] Error 2
>
> I do have /usr/local/lib/libtiff.a and /usr/local/lib/libtiff.so,
> from installation of version 3.5.7 of libtiff.
> And also - part of Solaris - /usr/openwin/lib/libtiff.so
> and /usr/sfw/lib/libtiff.so

I think the problem is with tiff.h or whatever the file is called.  I
think you should make sure that the tiff.h and libtiff.{a,so} come
from the same directory, either both from /usr/openwin or both from
/usr/local.

You can look in config.log, I think, to see what the configure script
has found.

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

       reply	other threads:[~2002-09-03 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1031051295.13026.help-gnu-emacs@gnu.org>
2002-09-03 13:06 ` Kai Großjohann [this message]
2002-09-03 11:07 emacs 21.2 make crashes Pieter Donche

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=vafd6rv9q9n.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.