public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mike@pelley.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/4020: Shell script syntax errors in gcc make files
Date: Tue, 14 Aug 2001 08:26:00 -0000	[thread overview]
Message-ID: <20010814152146.28446.qmail@sourceware.cygnus.com> (raw)

>Number:         4020
>Category:       bootstrap
>Synopsis:       Shell script syntax errors in gcc make files
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 14 08:26:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     mike@pelley.com
>Release:        gcc-current (head of tree)
>Organization:
>Environment:
Solaris 2.7
>Description:
My gcc-3.0 fails to build on Solaris 2.7 apparently due to
some script syntax errors.  I checked out head of tree for
the two files in question and the error still seems to be
there.  See patch file for more detail.
>How-To-Repeat:
Building natively for solaris 2.7 worked for me.
>Fix:
Patch attached.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="patch"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="patch"

SW5kZXg6IE1ha2VmaWxlLmluCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9jdnMvZ2NjL2djYy9nY2Mv
TWFrZWZpbGUuaW4sdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuNzIxCmRpZmYgLXUgLXIxLjcyMSBN
YWtlZmlsZS5pbgotLS0gTWFrZWZpbGUuaW4JMjAwMS8wOC8xMyAxNTo1MjoxNgkxLjcyMQorKysg
TWFrZWZpbGUuaW4JMjAwMS8wOC8xNCAxNDo1NDo0NgpAQCAtMjYzNCw3ICsyNjM0LDcgQEAKIAkg
ICAgZm9yIGYgaW4gY3BwLmluZm8gZ2NjLmluZm8gY3BwaW50ZXJuYWxzLmluZm87IGRvIFwKIAkJ
aWYgWyAtZiAkKGluZm9kaXIpLyQkZiBdOyB0aGVuIFwKIAkJICBpbnN0YWxsLWluZm8gLS1kaXIt
ZmlsZT0kKGluZm9kaXIpL2RpciAkKGluZm9kaXIpLyQkZjsgXAotCQllbHNlIHRydWU7IGZpIFwK
KwkJZWxzZSB0cnVlOyBmaTsgXAogCSAgICBkb25lOyBcCiAJICBlbHNlIHRydWU7IGZpOyBcCiAJ
ZWxzZSB0cnVlOyBmaTsKQEAgLTMwMjksNyArMzAyOSw3IEBACiAJICAgICAgbXYgJCRzdGFnZS8k
JGkvKiAkJGkvLiAyPi9kZXYvbnVsbDsgXAogCSAgICBlbHNlIFwKIAkgICAgICBtdiAkJHN0YWdl
LyQkaSAuOyBcCi0JICAgIGZpIFwKKwkgICAgZmk7IFwKIAkgIGRvbmUgXAogCWZpIDsgXAogCXJt
IC1mICQke3N0YWdlfV9idWlsZCAkJHtzdGFnZX1fY29weSA7XApJbmRleDogbWtsaWJnY2MuaW4K
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PQpSQ1MgZmlsZTogL2N2cy9nY2MvZ2NjL2djYy9ta2xpYmdjYy5pbix2CnJldHJp
ZXZpbmcgcmV2aXNpb24gMS4zMgpkaWZmIC11IC1yMS4zMiBta2xpYmdjYy5pbgotLS0gbWtsaWJn
Y2MuaW4JMjAwMS8wOC8wMyAwOToxOToxNwkxLjMyCisrKyBta2xpYmdjYy5pbgkyMDAxLzA4LzE0
IDE0OjU0OjQ2CkBAIC0zMzIsNyArMzMyLDcgQEAKIAogZWNobyAnc3RtcC1kaXJzOiBmb3JjZScK
IGVjaG8gJwlmb3IgZCBpbiAnIiRkaXJzIic7IGRvIFwnCi1lY2hvICcJICBpZiBbIC1kICQkZCBd
OyB0aGVuIHRydWU7IGVsc2UgJyRta2luc3RhbGxkaXJzJyAkJGQ7IGZpIFwnCitlY2hvICcJICBp
ZiBbIC1kICQkZCBdOyB0aGVuIHRydWU7IGVsc2UgJyRta2luc3RhbGxkaXJzJyAkJGQ7IGZpOyBc
JwogZWNobyAnCWRvbmUnCiBlY2hvICcJaWYgWyAtZiBzdG1wLWRpcnMgXTsgdGhlbiB0cnVlOyBl
bHNlIHRvdWNoIHN0bXAtZGlyczsgZmknCiAK


             reply	other threads:[~2001-08-14  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14  8:26 mike [this message]
2001-11-12  2:50 rodrigc
2001-11-12  8:06 rodrigc
2001-11-12  8:23 rodrigc
2001-11-12  8:28 rodrigc
2001-11-12 19:46 rodrigc
2001-11-12 20:09 rodrigc

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=20010814152146.28446.qmail@sourceware.cygnus.com \
    --to=mike@pelley.com \
    --cc=gcc-gnats@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).