public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rene Rebe <rene.rebe@gmx.net>
To: gcc@gcc.gnu.org
Subject: Re: building a gcc-3.3-prerelease cross-compiler
Date: Wed, 05 Nov 2003 14:12:00 -0000	[thread overview]
Message-ID: <20031105.150809.55830890.rene.rebe@gmx.net> (raw)
In-Reply-To: <20030512.212240.893778964.rene.rebe@gmx.net>

Hi,

in this thread I previously posted a link into our revision control
system. But since our basic layout changed a bit I just want to post
the new links as google reference because of so many 404-errors in my
apache log ... :

our gcc build script:

http://svn.rocklinux-consulting.de/rock-linux/trunk/package/base/gcc3/gcc3.conf

the other related scripts:

http://svn.rocklinux-consulting.de/rock-linux/trunk/package/base/linux24-header/linux24-header.conf

http://svn.rocklinux-consulting.de/rock-linux/trunk/package/base/binutils/binutils.conf

http://svn.rocklinux-consulting.de/rock-linux/trunk/package/base/glibc23/glibc23.conf

Sincerely yours,
  René Rebe
    - ROCK Linux stable release maintainer

--  
René Rebe - Europe/Germany/Berlin
  rene@rocklinux.org rene@rocklinux-consulting.de
http://www.rocklinux.org http://www.rocklinux-consulting.de
http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene

  reply	other threads:[~2003-11-05 14:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 12:00 Rene Rebe
2003-05-12 14:22 ` Daniel Jacobowitz
2003-05-12 16:51   ` Rene Rebe
2003-05-12 16:59     ` Paul Koning
2003-05-12 19:24       ` Rene Rebe
2003-11-05 14:12         ` Rene Rebe [this message]
2003-05-13 15:46       ` Michael Eager
2003-05-13 16:07         ` Rene Rebe
2003-05-13 18:56           ` Michael Eager
2003-05-13 19:44             ` Rene Rebe
2003-05-13 20:34               ` Michael Eager
2003-05-13 22:14                 ` Rene Rebe
2003-05-12 17:04     ` Joseph S. Myers
2003-05-12 17:13     ` Daniel Jacobowitz

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=20031105.150809.55830890.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).