This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
UDK Doc patch. was: new support for SCO Universal Development Kit target
> > [ patch ] allows you to use EGCS to generate SCO "universal"
> > binaries that run unchanged on OpenServer, Unixware 2, and
> > Unixware 7. (Hint: they also almost always run on Linux with ibcs
>
> Looks fine to me.
Thanx for the review, Jeff. I've now committed those. I'll be
submitting testsuite results for that target from time to time.
If you like, I'll adopt it as "mine" in MAINTAINERS.
> You need some ChangeLog entries of course :-)
Done.
Here is the current doc file I hinted at earlier. It'll likely change
as this target gets some air time, but I thought a peer review was in
order for initial checkin due to the funkiness of this target.
Thanx for the help.
RJL
Index: specific.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/install/specific.html,v
retrieving revision 1.14
diff -u -p -r1.14 specific.html
--- specific.html 1998/09/04 23:59:05 1.14
+++ specific.html 1998/10/01 03:53:58
@@ -33,6 +33,37 @@ OpenServer-specific flags.
tell you what you're running) require TLS597 from ftp.sco.com/TLS for
C++ constructors and destructors to work right.
+<p><b>i?86-*-udk</b><br>
+
+This target emulates the SCO Universal Development Kit and requires that
+package be installed. It's very much like the i?86-*-unixware7 target
+but is meant to be used when hosting on a system where UDK isn't the
+default compiler such as OpenServer 5 or Unixware 2. This target will
+generate binaries that will run on OpenServer, Unixware 2, or Unixware 7,
+with the same warnings and caveats as the SCO UDK.
+
+<p>You can stage1 with either your native compiler or with UDK. If you
+don't do a full bootstrap when initially building with your native compiler
+you will have an utterly unusable pile of bits as your reward.
+
+<p>This target is a little tricky to build because we have to distinguish
+it from the native tools (so it gets headers, startups, and libraries
+from the right place) while making the tools not think we're actually
+building a cross compiler. The easiest way to do this is with a configure
+command like this:
+
+<p>
+<code>
+ CC=/udk/usr/ccs/bin/cc CFLAGS=-O /play/egcs/configure --host=i686-pc-udk --target=i686-pc-udk --exec-prefix=udk-
+</code>
+
+<p> You should follow this with a 'make bootstrap'. After you do a
+'make install' you can then access the UDK-targeted EGCS tools by adding
+'udk-' before the commonly known name. For example, to invoke the C
+compiler, you would use 'udk-gcc'. They will coexist peacefully with
+any native-target EGCS tools you may have installed.
+
<p><b>i?86-pc-solaris*</b><br>
For versions of egcs before 1.0.1 you'll need a special
<a href="http://egcs.cygnus.com/faq.html#x86solaris">x86 solaris patch</a>