public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bob Young" <BYoung@nucoretech.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] gcc-4.1.1
Date: Fri, 16 Jun 2006 10:50:47 -0700	[thread overview]
Message-ID: <FAEEIJPAOFEMBBLKPMJEKEKFGEAA.BYoung@NuCORETech.com> (raw)
In-Reply-To: <4492E985.60400@veldy.net>



> -----Original Message-----
> From: Thomas T. Veldhouse [mailto:veldy@veldy.net]
> Sent: Friday, June 16, 2006 10:25 AM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] gcc-4.1.1

> You didn't pay attention to what he wrote.  I hope perhaps my post made
> it more clear.
>
> Tom Veldhouse

The only thing your post made clear is that you don't bother to read all of
a thread before replying to it. Maybe this will help:


The following reply was sent by me on Thur 6/8/2006 7:57 AM
*************************************************************


> -----Original Message-----
> From: Bo Ørsted Andresen [mailto:bo.andresen@zlin.dk]
> Sent: Thursday, June 08, 2006 7:29 AM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] gcc-4.1.1
>
>
> Thursday 08 June 2006 16:00 skrev Bob Young:
> > Show me some documentation for this "staging" you refer to.
>
> If you unpack the gcc sources you will find it in
> gcc-*/INSTALL/build.html as
> already mentioned by Richard. But you can also see it at [1].
>
> [1] http://gcc.gnu.org/install/build.html
>

Okay, I stand corrected.

Regards,
Bob Young

*************************************************************



-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-06-16 18:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ad4496950606070647s5a4bc702m8deeda7dbd590c4a@mail.gmail.com>
2006-06-07 13:53 ` [gentoo-user] gcc-4.1.1 Mohammed Hagag
2006-06-07 14:30   ` Peper
2006-06-07 14:35     ` Julien Cabillot
2006-06-07 14:45   ` Kristian Poul Herkild
2006-06-07 14:56   ` Neil Bothwick
2006-06-07 15:00   ` Bo Ørsted Andresen
2006-06-07 15:25   ` Conneries wearegeeks
2006-06-07 16:04   ` Roy Wright
2006-06-07 17:46     ` Mike Huber
2006-06-07 18:09       ` Daniel da Veiga
2006-06-07 19:27         ` Roy Wright
2006-06-07 19:55           ` Daniel da Veiga
2006-06-07 18:17       ` Evan Klitzke
2006-06-07 23:25     ` Richard Fish
2006-06-08  0:32       ` Evan Klitzke
2006-06-08  4:40         ` Richard Fish
2006-06-08 11:39           ` Mohammed Hagag
2006-06-08  1:50       ` Bob Young
2006-06-08  2:10         ` Jerry McBride
2006-06-12 21:35           ` Bob Young
2006-06-13  0:09             ` Richard Fish
2006-06-08  4:24         ` Richard Fish
2006-06-08 12:34           ` Bob Young
2006-06-08 13:31             ` Hans-Werner Hilse
2006-06-08 14:00               ` Bob Young
2006-06-08 14:28                 ` Bo Ørsted Andresen
2006-06-08 14:57                   ` Bob Young
2006-06-08 15:27                 ` Toby Cubitt
2006-06-08 18:05             ` Richard Fish
2006-06-09 11:50               ` Vladimir G. Ivanovic
2006-06-09 19:43                 ` Richard Fish
2006-06-16 17:25             ` Thomas T. Veldhouse
2006-06-16 17:50               ` Bob Young [this message]
2006-06-16 17:17         ` Thomas T. Veldhouse

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=FAEEIJPAOFEMBBLKPMJEKEKFGEAA.BYoung@NuCORETech.com \
    --to=byoung@nucoretech.com \
    --cc=gentoo-user@lists.gentoo.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