public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Stone <ahs3@fc.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: milstone reached: ia64 linux builds out of Linus' tree
Date: Tue, 30 Mar 2004 01:28:45 +0000	[thread overview]
Message-ID: <1080610125.1838.169.camel@fcboson> (raw)
In-Reply-To: <20040330003052.GD2986@cse.unsw.EDU.AU>

Um, I hate to throw a damper on this party, but the
Intel compiler license specifically prohibits this 
sort of redistribution.  Intel's legal folks would
have to provide gelato some mechanism for this to
work.

On Mon, 2004-03-29 at 18:16, Jesse Barnes wrote:
> On Monday 29 March 2004 5:03 pm, Peter Chubb wrote:
> > >>>>> "Duraid" = Duraid Madina <duraid@octopus.com.au> writes:
> >
> > Duraid> And for your next trick... any chance of adding an Intel C
> > Duraid> compiler version to the tinderbox?
> >
> > I'd love this to happen, but I haven't yet been able to build the
> > kernel with icc.
> >
> > If anyone out there has managed it, please document the result ---
> > maybe on our Wiki? http://www.gelato.unsw.edu.au/IA64wiki/
> 
> Yeah, this would be nice.  I received some secret instructions (Intel 
> apparently doesn't want some of the required compiler flags to be made 
> public) on how to do this since I promised David I'd cleanup the sn2 asm code 
> and use the compiler intrinsics, but I accidentally deleted that mail before 
> I had a chance to do the cleanup...
> 
> Thanks,
> Jesse
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Ciao,
al
----------------------------------------------------------------------
Al Stone                                      Alter Ego:
Linux & Open Source Lab                       Debian Developer
Hewlett-Packard Company                       http://www.debian.org
E-mail: ahs3@fc.hp.com                        ahs3@debian.org
----------------------------------------------------------------------


  parent reply	other threads:[~2004-03-30  1:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30  0:30 milstone reached: ia64 linux builds out of Linus' tree Ian Wienand
2004-03-30  0:37 ` Duraid Madina
2004-03-30  1:03 ` Peter Chubb
2004-03-30  1:16 ` Jesse Barnes
2004-03-30  1:28 ` Al Stone [this message]
2004-03-30  1:57 ` Duraid Madina
2004-03-30  3:59 ` Al Stone
2004-03-30  7:51 ` Siddha, Suresh B
2004-03-30 17:39 ` Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2003-08-04 17:37 David Mosberger
2003-08-04 17:53 ` H. J. Lu
2003-08-04 18:00 ` Jesse Barnes
2003-08-04 18:10 ` H. J. Lu
2003-08-04 18:21 ` David Mosberger
2003-08-04 18:27 ` David Mosberger
2003-08-04 18:31 ` David S. Miller
2003-08-04 18:40 ` David Mosberger
2003-08-04 18:41 ` Jes Sorensen
2003-08-04 18:45 ` David S. Miller
2003-08-04 18:49 ` Jesse Barnes
2003-08-04 18:52 ` Jesse Barnes
2003-08-04 19:07 ` David Mosberger
2003-08-04 19:07 ` Alan Cox
2003-08-04 19:17 ` David S. Miller
2003-08-04 19:18 ` Andreas Schwab
2003-08-04 19:53 ` H. J. Lu
2003-08-04 23:06 ` Peter Chubb
2003-08-04 23:20 ` Jesse Barnes
2003-08-04 23:35 ` David Mosberger
2003-08-04 23:39 ` David Mosberger
2003-08-13  0:07 ` Ian Wienand
2003-09-10  0:53 ` Ian Wienand
2003-09-10  1:57 ` David Mosberger

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=1080610125.1838.169.camel@fcboson \
    --to=ahs3@fc.hp.com \
    --cc=linux-ia64@vger.kernel.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