From: Jeffrey A Law <law@cygnus.com>
To: Alex deVries <adevries@thepuffingroup.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting problems
Date: Sat, 12 Jun 1999 15:09:21 -0600 [thread overview]
Message-ID: <23436.929221761@upchuck.cygnus.com> (raw)
In-Reply-To: Your message of Sat, 12 Jun 1999 07:15:18 EDT. <37624146.A7B5F0FE@thepuffingroup.com>
In message <37624146.A7B5F0FE@thepuffingroup.com>you write:
> Jeffrey A Law wrote:
> >
>
> <snip>
>
> Okay, I can make that change, unless someone beats me to it.
Let me know if it helps. That change is just an educated guess :-)
> However, there's this time gap between now and when we actually have the
> new toolchain from Cygnus. During this time, the only thing that we
> expect to work on is the kernel and bootloader. Having just those two
> components building with the current gcc and linker are important.
OK. But note Cygnus is _NOT_ currently scheduled or contracted to provide a
32bit ELF toolchain. Cygnus will be providing a 64bit ELF toolchain which
folks can use to derive much of the 32bit toolchain.
>
> If we don't do it this way, the only toolchain we'll have is hosted on
> HPUX, which I want to avoid if I possibly can. The
> fix-build-boot-restart cycle is muuuuch faster if you can cross compile
> and netboot, particularly for those people who only have one HPUX
> machine and slow connectivity to the HPUX box that HP has online for us.
I understand. I'm still skeptical that you're going to end up burning
more time fighting those lame elf tools than you would by building with
SOM tools.
Of course, if you had two HP machines, then this is a non-issue :-)
jeff
next prev parent reply other threads:[~1999-06-12 21:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3761F335.ADA76678@thepuffingroup.com>
1999-06-12 6:32 ` [parisc-linux] booting problems Jeffrey A Law
1999-06-12 11:15 ` Alex deVries
1999-06-12 16:57 ` John David Anglin
1999-06-12 18:36 ` Alan Cox
1999-06-12 18:53 ` Jeffrey A Law
1999-06-12 19:36 ` Matthew Wilcox
1999-06-12 21:15 ` Jeffrey A Law
1999-06-12 21:09 ` Jeffrey A Law [this message]
1999-06-13 19:10 ` John David Anglin
1999-06-14 0:17 ` Alex deVries
2001-08-31 16:06 James Waterhouse
-- strict thread matches above, loose matches on Subject: below --
1999-06-11 18:49 Jason Eckhardt
1999-06-11 19:37 ` Alex deVries
1999-06-12 0:56 ` John David Anglin
1999-06-12 1:25 ` John David Anglin
1999-06-12 3:23 ` John David Anglin
1999-06-12 3:43 ` Jeffrey A Law
1999-06-12 5:10 ` Alex deVries
1999-06-12 5:11 ` Jeffrey A Law
1999-06-10 21:06 Richard J. Rauenzahn
[not found] <no.id>
1999-06-10 18:32 ` Stan Sieler
1999-06-10 5:07 Alex deVries
1999-06-10 6:20 ` Kirk Bresniker
1999-06-10 7:21 ` Alex deVries
1999-06-10 15:26 ` Kirk Bresniker
1999-06-10 17:08 ` Stan Sieler
1999-06-10 17:03 ` Stan Sieler
1999-06-10 21:20 ` John David Anglin
1999-06-11 7:36 ` Alex deVries
1999-06-11 8:57 ` Alex deVries
1999-06-11 9:08 ` Jeffrey A Law
1999-06-11 14:06 ` John David Anglin
1999-06-11 17:19 ` Alex deVries
1999-06-11 18:10 ` Kirk Bresniker
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=23436.929221761@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=adevries@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
/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