From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: olson@anchor.engr.sgi.com (Dave Olson)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: anyone know if this is true?
Date: Tue, 18 Jun 1996 10:21:17 -0700 (PDT) [thread overview]
Message-ID: <199606181721.KAA14883@yon.engr.sgi.com> (raw)
In-Reply-To: <199606181711.KAA13973@anchor.engr.sgi.com> from "Dave Olson" at Jun 18, 96 10:11:49 am
>
>It's not true. All he has to do is install eoe.hdrs and compiler_eoe.hdrs.
>
Dave, I'm afraid you're misinformed. The problem is real.
Customers cannot build anything on 6.2 even if the install the above
subsystems, unless they buy our IDO.
I said it many times, to be able to build anything on 6.2
they still miss a linker (the GNU linker is not supported in
any official GNU or Cygnus releases on any SGI and we don't include
/usr/lib/crt[1n].o with our headers and libraries)
David Miller has a heavily patched working GNU linker that creates
Linux elf-32 binaries. He told me that it should be easy to
make it produce native IRIX binaries. As for the crt[1n].o files
I really hope they are not a problem to give away.
>That's just the *BASE* header files.
>
This is correct. From the point of view of the original complaint
Is not enough.
--
Peace, Ariel
WARNING: multiple messages have this Message-ID (diff)
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: Dave Olson <olson@anchor.engr.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: anyone know if this is true?
Date: Tue, 18 Jun 1996 10:21:17 -0700 (PDT) [thread overview]
Message-ID: <199606181721.KAA14883@yon.engr.sgi.com> (raw)
Message-ID: <19960618172117.Hv5qqbJeWWuy8EoiZBlyDV0_PXUKBdZS0wv1XSViNKA@z> (raw)
In-Reply-To: <199606181711.KAA13973@anchor.engr.sgi.com> from "Dave Olson" at Jun 18, 96 10:11:49 am
>
>It's not true. All he has to do is install eoe.hdrs and compiler_eoe.hdrs.
>
Dave, I'm afraid you're misinformed. The problem is real.
Customers cannot build anything on 6.2 even if the install the above
subsystems, unless they buy our IDO.
I said it many times, to be able to build anything on 6.2
they still miss a linker (the GNU linker is not supported in
any official GNU or Cygnus releases on any SGI and we don't include
/usr/lib/crt[1n].o with our headers and libraries)
David Miller has a heavily patched working GNU linker that creates
Linux elf-32 binaries. He told me that it should be easy to
make it produce native IRIX binaries. As for the crt[1n].o files
I really hope they are not a problem to give away.
>That's just the *BASE* header files.
>
This is correct. From the point of view of the original complaint
Is not enough.
--
Peace, Ariel
next prev parent reply other threads:[~1996-06-18 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-18 17:11 anyone know if this is true? Dave Olson
1996-06-18 17:21 ` Ariel Faigon [this message]
1996-06-18 17:21 ` Ariel Faigon
1996-06-18 18:39 ` William J. Earl
1996-06-18 18:39 ` William J. Earl
-- strict thread matches above, loose matches on Subject: below --
1996-06-18 16:41 Larry McVoy
1996-06-18 17:10 ` Ariel Faigon
1996-06-18 17:10 ` Ariel Faigon
1996-06-18 17:35 ` Michael Tiemann
1996-06-18 17:35 ` Michael Tiemann
[not found] ` <lm@neteng>
1996-06-18 17:14 ` Donna Yobs
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=199606181721.KAA14883@yon.engr.sgi.com \
--to=ariel@yon.engr.sgi.com \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=olson@anchor.engr.sgi.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