From: dkcombs@panix.com (David Combs)
Subject: Re: Has anyone actually built emacs 21.3 for SOLARIS (sparc)?
Date: Tue, 3 Jun 2003 07:19:56 +0000 (UTC) [thread overview]
Message-ID: <bbhi6s$9sd$3@reader1.panix.com> (raw)
In-Reply-To: 3ED3874B.3010704@yahoo.com
In article <3ED3874B.3010704@yahoo.com>,
Kevin Rodgers <ihs_4664@yahoo.com> wrote:
>Dave Uhring wrote:
>
>> On Mon, 26 May 2003 13:13:59 +0000, David Combs wrote:
>>
>>
>>>Any ideas?
>>>
>>
>> None, really. I use gcc-3.2.2 built from source using gcc from the
>> Solaris 9 Software Companion CD; then I pkgrm'd SFWgcc and all of its
>> dependencies and I no longer have /opt/sfw.
>>
>> Since Sun chose to add its supported free software in /usr/sfw that is
>> where I placed the rest of the free software built from source on this
>> system.
>>
>> Solaris 9 -does not- "but solaris-NINE wants it in /opt/sfw (I believe
>> that's who wanted it there, not me)". If you did a complete install of
>> Solaris 9 you will indeed find much free software in /usr/sfw.
>
>The /opt/sfw (and now /usr/sfw) directory is a bad idea by Sun. Save
>yourself some grief and make /usr/local a symbolic link to whichever
>directory your version of Solaris came with.
>--
><a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
Thanks.
You mean make /usr/local a symlink to either /opt/sfw or /usr/sfw,
whichever one I have?
Well, probably due to answering some question wrong (or maybe right?),
I have *both*.
Perhaps best to make /usr/local a symlink to something on
a different partition, and keep them all separate,
so that the companion-disk stuff stays in an sfw-dir,
and the stuff I build can go in the /usr/local,
where so much stuff still seems to want to live.
David
next prev parent reply other threads:[~2003-06-03 7:19 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
2003-05-27 15:42 ` Kevin Rodgers
2003-06-03 7:19 ` David Combs [this message]
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='bbhi6s$9sd$3@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).