From: "Stefan Monnier" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu>
Subject: Re: Has anyone actually built emacs 21.3 for SOLARIS (sparc)?
Date: 21 May 2003 18:37:09 -0400 [thread overview]
Message-ID: <5lhe7olyei.fsf@rum.cs.yale.edu> (raw)
In-Reply-To: bags5k$ibs$2@reader1.panix.com
>> [emacs-21.3]$ ./configure --prefix=/usr/sfw --with-x-toolkit=motif
>> --with-xpm --with-jpeg --with-tiff --with-gif --with-png --with-x
> Question: does any 2nd person agree that I should use
> the above config-args -- either as-is, or with modifications.
The --with-xpm, --with-jpeg, --with-tiff, --with-gif, and --with-png,
and --with-x should be unnecessary (they are autodetected).
The --with-x-toolkit=motif is your choice, depending on whether you prefer
the Motif toolkit for scrollbars and menus or the Xaw3d toolkit for
scrollbars and the Lucid toolkit for menus.
You have Xaw3d installed on your system in /usr/sfw/lib as your
listing has shown, so it should work just fine as long as you make sure
to tell the executable where the Xaw3d library can be found.
For that you need to either provide a -R/usr/sfw/lib argument or an
LD_RUN_PATH to the C compiler (the C compiler did find the library while
compiling, but the compiler does not assume that the library will be at the
same spot when you run the program as when you compile) or set
LD_LIBRARY_PATH if you forgot to give the relevant info to the compiler.
The -R option is the best choice.
The same issue you're seeing with Xaw3d might occur with Motif, of course,
depending on where the library is installed and what is the default search
path for dynamically linked libraries.
Stefan
next prev parent reply other threads:[~2003-05-21 22:37 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 [this message]
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
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=5lhe7olyei.fsf@rum.cs.yale.edu \
--to=monnier+gnu.emacs.help/news/@flint.cs.yale.edu \
/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).