From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Building from scratch.
Date: Mon, 27 Aug 2001 23:54:31 -0400 [thread overview]
Message-ID: <20010827235431.K28978@megatonmonkey.net> (raw)
In-Reply-To: <20010827203849.H525@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Mon, Aug 27, 2001 at 08:38:49PM +0100
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
> > I started by building the tools, as per the instructions on the website.
> >
> > - Built binutils
> > - Partially build gcc
> > - Unpack and configure kernel
> > - Build glibc...
>
> Where did you get glibc from? The only place with current patches is the
> Debian package. Our CVS is terribly out of date.
>
> --
> Revolutions do not require corporate support.
M,
That explains things...
ftp://puffin.external.hp.com/pub/parisc/cvs <== Bad!
ftp://ftp.debian.org/debian/pool/main/g/glibc/ <== Good!?
Cheers,
Carlos.
p.s. Small diff to the toolchain index.html ?
[-- Attachment #2: index.html.diff --]
[-- Type: text/plain, Size: 1607 bytes --]
--- ./toolchain/index.html Mon Aug 27 22:45:01 2001
+++ index.html Mon Aug 27 23:47:33 2001
@@ -94,9 +94,23 @@
<br> <br>
The source trees of all of these are available through <A HREF="../tools/index.html">CVS</A> but we also make available nightly snapshots from <A HREF="ftp://puffin.external.hp.com/pub/parisc/cvs/">here</A>. It is best to get a snapshot the first time you want to build a tree and update from CVS from then on. <BR>
-
<OL>
<strong><LI>Fetch GCC, Binutils, Glibc, Linux:</strong>
+<br> <BR>
+Note that the /pub/parisc/cvs snapshots may not be completely up
+to date for glibc. The most complete snapshots may be found at the debian
+pool <a href="ftp://ftp.debian.org/debian/pool/main">ftp://ftp.debian.org/debian/pool/main</a>. Although the example lists glibc 2.2.4, you will want to replace this with the latest available glibc version.
+<PRE>
+cd
+mkdir source
+mkdir build
+cd source
+wget ftp://ftp.debian.org/debian/pool/main/g/glibc/glibc_2.2.4.orig.tar.gz
+wget ftp://puffin.external.hp.com/pub/parisc/cvs/binutils-latest.tar.gz
+wget ftp://puffin.external.hp.com/pub/parisc/cvs/gcc-latest.tar.gz
+wget ftp://puffin.external.hp.com/pub/parisc/cvs/linux-latest.tar.gz
+</PRE>
+Or alternatively:
<PRE>
cd
mkdir source
@@ -109,9 +123,15 @@
get binutils-latest.tar.gz
get gcc-latest.tar.gz
get linux-latest.tar.gz
-get glibc-latest.tar.gz
+quit
+ftp ftp.debian.org
+user: anonymous
+password: you@your.email.address
+cd debian/pool/main/g/glibc
+get glibc_2.2.4.orig.tar.gz
quit
</PRE>
+
<strong>Determine the host system setup:</strong>
<br> <br>
next prev parent reply other threads:[~2001-08-28 3:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-26 20:27 [parisc-linux] Building from scratch Carlos O'Donell Jr.
2001-08-27 19:38 ` Matthew Wilcox
2001-08-28 3:54 ` Carlos O'Donell Jr. [this message]
2001-08-28 4:39 ` Carlos O'Donell Jr.
2001-08-28 5:10 ` Matthew Wilcox
2001-08-28 11:17 ` Carlos O'Donell Jr.
2001-08-28 14:56 ` Matthew Wilcox
2001-08-28 15:29 ` Carlos O'Donell Jr.
2001-08-28 18:47 ` Matthew Wilcox
2001-08-28 19:22 ` Carlos O'Donell Jr.
2001-08-28 19:44 ` Matthew Wilcox
2001-08-28 20:36 ` Carlos O'Donell Jr.
2001-08-28 20:47 ` Matthew Wilcox
2001-08-28 15:06 ` Carlos O'Donell Jr.
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=20010827235431.K28978@megatonmonkey.net \
--to=carlos@megatonmonkey.net \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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