From: "Dave Uhring" <daveuhring@yahoo.com>
Subject: Re: Has anyone actually built emacs 21.3 for SOLARIS (sparc)?
Date: Tue, 03 Jun 2003 08:47:17 -0500 [thread overview]
Message-ID: <pan.2003.06.03.13.47.17.523420@yahoo.com> (raw)
In-Reply-To: bbhhis$9sd$1@reader1.panix.com
On Tue, 03 Jun 2003 07:09:16 +0000, David Combs wrote:
> What came compiled with gcc-3.2.2?
>
> Anything supplied by Sun -- including in that companion-cd?
AFAIK, every binary supplied by Sun was built using their own compilers.
And those libraries do seem to be compatible with binaries built using
gcc-3.2.2. I have KDE-3.1.1a compiled and installed on this system. KDE
requires libjpeg and I use jpeg supplied with the OE.
[lib]$ pkgchk -l -p /usr/sfw/lib/libjpeg.so.62.0.0
Pathname: /usr/sfw/lib/libjpeg.so.62.0.0
Type: regular file
Expected mode: 0755
Expected owner: root
Expected group: bin
Expected file size (bytes): 140144
Expected sum(1) of contents: 57880
Expected last modification: Mar 02 02:04:51 2002
Referenced by the following packages:
SUNWjpg
Current status: installed
> I finally managed, yesterday, to get emacs built, and
> I had to add opt/sfw/bin to path, and likewise for
> the ldflags for the -L and -R pair.
Had I known that you had installed packages from the Software Companion CD
I would have included those arguments to $LDFLAGS.
>>/opt/sfw does not exist.
>
> Oh yes it does. During 9's installation,
> I must have answered some question differently from you.
/opt/sfw gets created when you install packages from the Software
Companion CD. It is not there otherwise.
> Looks like I really screwed up where I got things placed
> during initial install. Even though I had sun-service on
> the phone while I did it!
Not a screw up as to where things got placed. You simply have to know
where they are and adjust your environment accordingly.
next prev parent reply other threads:[~2003-06-03 13:47 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
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 [this message]
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=pan.2003.06.03.13.47.17.523420@yahoo.com \
--to=daveuhring@yahoo.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).