From: Janis Johnson <janis187@us.ibm.com>
To: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>
Cc: janis187@us.ibm-com, gcc@gcc.gnu.org
Subject: Re: Testing 3.1 g++ applications on cygwin
Date: Fri, 26 Apr 2002 14:16:00 -0000 [thread overview]
Message-ID: <20020426140506.A21317@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0204262029430.28063-100000@snake.iap.physik.tu-darmstadt.de>; from schmid@snake.iap.physik.tu-darmstadt.de on Fri, Apr 26, 2002 at 08:37:04PM +0200
On Fri, Apr 26, 2002 at 08:37:04PM +0200, Peter Schmid wrote:
> I test pooma gcc on a regular basis. I did not encounter a problem since
> May 2001. But I am using the original pooma-gcc distribution
> with two patches of mine applied, otherwise configuring does not work.
>
> Maybe applying the following patchset makes a difference:
> http://gcc.gnu.org/ml/gcc/2001-04/msg01020.html
>
> Hope this helps, if not could you please post your log file.
>
> Peter Schmid
Thanks, I applied that patch to pooma-gcc and it's chugging along now.
Gerald, how about this for gcc-3.1/testing-pooma.html? The formatting
surrounding the patch code is highly questionable, so feel free to fix
it or tell me how to do it properly.
On the other hand, perhaps someone can rebuild the pooma-gcc tarball,
fixing this and also the copyright in testing.pl.
Janis
Index: testing-pooma.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.1/testing-pooma.html,v
retrieving revision 1.2
diff -u -p -r1.2 testing-pooma.html
--- testing-pooma.html 18 Apr 2002 20:27:38 -0000 1.2
+++ testing-pooma.html 26 Apr 2002 20:59:39 -0000
@@ -28,6 +28,36 @@ programs, and run the examples, use:</p>
<li><code>cd pooma-gcc</code></li>
</ul>
</li>
+<li>Apply this patch:
+ <ul>
+ <li><code>patch -b -p0 << END_OF_PATCH
+ <pre>
+--- tester.pl.orig Fri Apr 26 11:06:30 2002
++++ tester.pl Fri Apr 26 11:06:57 2002
+@@ -111,7 +111,7 @@ while (<VARIABLETEMPLATE>)
+ }
+ close (VARIABLES);
+ die ("Failed to finish writing the shared variables file.") if $?;
+-close (VARIABLE-TEMPLATE);
++close (VARIABLETEMPLATE);
+ die ("Failed to finish reading the shared variables template file.") if $?;
+
+ ######################################################################
+--- config/Shared/tail.mk.orig Fri Apr 26 13:26:20 2002
++++ config/Shared/tail.mk Fri Apr 26 13:25:57 2002
+@@ -110,7 +110,7 @@ endif
+ include $(SHARED_ROOT)/rules.mk
+
+ # Include (if it exists) the dependency file.
+--include $(LIBRARY_ROOT)/depend.mk
++#-include $(LIBRARY_ROOT)/depend.mk
+
+
+ # ACL:rcsinfo
+END_OF_PATCH
+ </pre></code></li>
+ </ul>
+</li>
</ul>
next prev parent reply other threads:[~2002-04-26 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 10:37 Peter Schmid
2002-04-26 14:16 ` Janis Johnson [this message]
2002-04-26 14:33 ` Gerald Pfeifer
2002-04-26 15:48 ` Janis Johnson
2002-04-26 16:09 ` Paolo Carlini
2002-04-27 11:45 ` Gerald Pfeifer
-- strict thread matches above, loose matches on Subject: below --
2002-04-25 23:26 Billinghurst, David (CRTS)
2002-04-26 8:20 ` Janis Johnson
2002-04-26 8:36 ` Gerald Pfeifer
2002-04-26 9:30 ` Janis Johnson
2002-04-26 9:47 ` Janis Johnson
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=20020426140506.A21317@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm-com \
--cc=schmid@snake.iap.physik.tu-darmstadt.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).