From: dkcombs@panix.com (David Combs)
Subject: Re: Has anyone actually built emacs 21.3 for SOLARIS (sparc)?
Date: Wed, 21 May 2003 08:50:21 +0000 (UTC) [thread overview]
Message-ID: <bafekd$2re$1@reader1.panix.com> (raw)
In-Reply-To: pan.2003.05.20.21.03.12.709422@yahoo.com
In article <pan.2003.05.20.21.03.12.709422@yahoo.com>,
Dave Uhring <daveuhring@yahoo.com> wrote:
>On Tue, 20 May 2003 15:53:59 -0400, Bijan Soleymani wrote:
>
>> Looks like you've got problems with libXaw3d.
>>
>> You should look for xaw3d in /etc/PROBLEMS. Here is what I found:
>>
>> "
>> * On systems with shared libraries you might encounter run-time errors
>> from the dynamic linker telling you that it is unable to find some
>> shared libraries, for instance those for Xaw3d or image support.
>> These errors mean Emacs has been linked with a library whose shared
>> library is not in the default search path of the dynamic linker.
>
>Solaris is an ELF system. The library search path is supposed to be in
>the headers of the binary. It gets put there by using the proper LDFLAGS
>during the compile time link.
>
>[emacs-21.3]$ echo $LD_LIBRARY_PATH $LD_RUN_PATH
>
>[emacs-21.3]$ ldd src/emacs-21.3.1
> libXm.so.4 => /usr/dt/lib/libXm.so.4
> libgen.so.1 => /usr/lib/libgen.so.1
> libXp.so.1 => /usr/openwin/lib/libXp.so.1
> libXmu.so.4 => /usr/openwin/lib/libXmu.so.4
> libXt.so.4 => /usr/openwin/lib/libXt.so.4
> libSM.so.6 => /usr/openwin/lib/libSM.so.6
> libICE.so.6 => /usr/openwin/lib/libICE.so.6
> libXext.so.0 => /usr/openwin/lib/libXext.so.0
> libtiff.so.3 => /usr/sfw/lib/libtiff.so.3
> libjpeg.so.62 => /usr/sfw/lib/libjpeg.so.62
> libpng.so.2 => /usr/sfw/lib/libpng.so.2
> libz.so.1 => /usr/lib/libz.so.1
> libm.so.1 => /usr/lib/libm.so.1
> libXpm.so.4 => /usr/openwin/lib/libXpm.so.4
> libX11.so.4 => /usr/openwin/lib/libX11.so.4
> libsocket.so.1 => /usr/lib/libsocket.so.1
> libnsl.so.1 => /usr/lib/libnsl.so.1
> libkstat.so.1 => /usr/lib/libkstat.so.1
> libcurses.so.1 => /usr/lib/libcurses.so.1
> libc.so.1 => /usr/lib/libc.so.1
> libdl.so.1 => /usr/lib/libdl.so.1
> libmp.so.2 => /usr/lib/libmp.so.2
> /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1
>
>
Thanks!
My "make" got as far as creating "temacs", for
which ldd on gives:
libXaw3d.so.5 => (file not found)
libXmu.so.4 => /usr/openwin/lib/libXmu.so.4
libXt.so.4 => /usr/openwin/lib/libXt.so.4
libSM.so.6 => /usr/openwin/lib/libSM.so.6
libICE.so.6 => /usr/openwin/lib/libICE.so.6
libXext.so.0 => /usr/openwin/lib/libXext.so.0
libXpm.so.4 => /usr/openwin/lib/libXpm.so.4
libX11.so.4 => /usr/openwin/lib/libX11.so.4
libsocket.so.1 => /usr/lib/libsocket.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libkstat.so.1 => /usr/lib/libkstat.so.1
libcurses.so.1 => /usr/lib/libcurses.so.1
libm.so.1 => /usr/lib/libm.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libmp.so.2 => /usr/lib/libmp.so.2
/usr/platform/SUNW,Sun-Blade-100/lib/libc_psr.so.1
Why does mine want the 3d thing, and yours doesn't?
Also, you did that echo of the two LD_..._PATHs, and
showed nothing for what typed out.
Here's what I get:
84 ==/dkcjunk==> echo $LD_RUN_PATH
LD_RUN_PATH: Undefined variable
85 ==/dkcjunk==> echo $LD_LIBRARY_PATH
LD_LIBRARY_PATH: Undefined variable
86 ==/dkcjunk==>
A prior answer said to define the first one as
/usr/openwin/lib.
Is that your opinion too?
And what about the RUN path -- set it to what?
(The last time I dealt with these concepts was
way back on dec-20 twenex; since then I've been
using a language no one's ever heard of (Mainsail)
that works entirely differently, doesn't even
use ld, does such things its own (also nice) way.)
Thanks!
David
PS: your opinion on those configure-args suggested in that
same post? Any changes, or use as-is.
next prev parent reply other threads:[~2003-05-21 8:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 16:41 Has anyone actually built emacs 21.3 for SOLARIS (sparc)? David Combs
2003-05-20 18:10 ` Stefan Monnier
2003-05-20 19:38 ` Dave Uhring
2003-05-20 18:39 ` Dave Uhring
2003-05-21 21:47 ` David Combs
2003-05-21 22:37 ` Stefan Monnier
2003-05-21 23:15 ` Darren Dunham
2003-05-22 0:54 ` Stefan Monnier
2003-05-22 15:06 ` bbense+gnu.emacs.help.comp.unix.solaris.May.22.03
2003-05-22 15:45 ` Dave Uhring
2003-05-23 5:28 ` David Combs
2003-05-23 9:18 ` David Combs
2003-05-23 10:45 ` Dave Uhring
2003-05-26 0:44 ` David Combs
2003-05-23 10:41 ` Dave Uhring
2003-05-23 4:36 ` David Combs
2003-05-23 5:53 ` Miles Bader
2003-05-22 8:02 ` David Combs
2003-05-22 13:56 ` Stefan Monnier
2003-05-22 14:53 ` David Combs
2003-05-20 19:53 ` Bijan Soleymani
2003-05-20 21:03 ` Dave Uhring
2003-05-21 8:50 ` David Combs [this message]
2003-05-21 15:55 ` Dave Uhring
2003-05-21 22:24 ` David Combs
2003-05-21 22:49 ` Stefan Monnier
2003-05-21 23:34 ` Dave Uhring
2003-05-22 8:07 ` David Combs
2003-05-22 13:48 ` Casper H.S. Dik
2003-05-22 14:45 ` Dave Uhring
2003-05-24 7:29 ` David Combs
2003-05-24 14:55 ` Dave Uhring
2003-05-25 16:40 ` Philip Brown
2003-05-26 2:46 ` David Combs
2003-05-26 19:14 ` Philip Brown
2003-05-26 13:13 ` David Combs
2003-05-26 15:46 ` Dave Uhring
2003-05-26 22:49 ` David Combs
2003-05-26 23:44 ` Dave Uhring
2003-05-27 0:10 ` Dave Uhring
2003-06-03 7:13 ` David Combs
2003-06-03 7:09 ` David Combs
2003-06-03 13:47 ` Dave Uhring
2003-05-27 15:42 ` Kevin Rodgers
2003-06-03 7:19 ` David Combs
2003-05-21 21:44 ` David Combs
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='bafekd$2re$1@reader1.panix.com' \
--to=dkcombs@panix.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).