linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: Nautilus builds and works from source on ppc
Date: Thu, 17 Aug 2000 18:40:01 -0400	[thread overview]
Message-ID: <399C69C1.AEF6646E@sympatico.ca> (raw)


Hi,

In case anyone is interested.  I upgraded a straight YDL CS 1.2 system with the
latest binutils, glibc, and gcc from Franz and installed the helix code and
updated it to the latest releases.

I then grabbed all of the required parts and followed the build instructions
from Eazel and shortly had a working Nautilus file manager (I did have to edit
one makefile in Nautilus to add the -lrpm library to one of the component view
tools but that is it.

It seems to build rather easily.  If it turns out to be stable I will build tar
archives for installation into /usr/local/ so other people can play with it.

Just let me know if you are interested.

Kevin

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2000-08-17 22:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=399C69C1.AEF6646E@sympatico.ca \
    --to=kevin.hendricks@sympatico.ca \
    --cc=khendricks@ivey.uwo.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 NNTP newsgroup(s).