zsh-workers
 help / color / mirror / code / Atom feed
From: teg@redhat.com (Trond Eivind Glomsrød)
To: Jason Price <jprice@cyberbuzz.gatech.edu>
Cc: zsh-workers@sunsite.dk
Subject: Re: gcc 3.0 produces broken zsh
Date: 20 Jun 2001 00:01:29 -0400	[thread overview]
Message-ID: <xuybsnjiyue.fsf@halden.devel.redhat.com> (raw)
In-Reply-To: <20010619235049.A20425@oobleck.gatech.edu>

Jason Price <jprice@cyberbuzz.gatech.edu> writes:

> Out of morbid curiosity, I built gcc3 and installed it somewhere out of the
> way (like $HOME/gcc3) on my redhat 7.1 linux box.  Then I tried to build
> zsh with it.
> 
> It configured and compiled with hardly any errors.  The only build errors
> were:
> 
> math.c: In function `zzlex':
> math.c:382: warning: operation on `ptr' may be undefined
> utils.o: In function `gettempname':
> utils.o(.text+0x1de2): the use of `mktemp' is dangerous, better use `mkstemp'
> 
> However, when I install it, it doesn't seem to be able to find or load any
> modules.  Building with stock gcc's of the 2.95.* variety work

It seems to work nicely with the compiler we ship, 2.96RH, as well
(downgrading to 2.95? Yick)
 
> Now, I could VERY easily be wrong, but most of the painful changes in gcc3
> are in C++ land

Yes.

-- 
Trond Eivind Glomsrød
Red Hat, Inc.


  reply	other threads:[~2001-06-20  4:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20  3:50 Jason Price
2001-06-20  4:01 ` Trond Eivind Glomsrød [this message]
2001-06-21  3:19   ` Vin Shelton
2001-06-21  3:36     ` Andrej Borsenkow
2001-06-21 20:44       ` Jason Price
2001-06-22  9:39         ` Andrej Borsenkow
2001-06-22 12:53           ` Chmouel Boudjnah
2001-06-23 18:24           ` Andrej Borsenkow
2001-06-25 11:15             ` Chmouel Boudjnah
2001-06-25 11:22             ` Andrej Borsenkow
2001-06-21  4:44     ` Bart Schaefer
2001-06-20  4:13 ` Dan Nelson
2001-06-20 11:19   ` Chmouel Boudjnah

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=xuybsnjiyue.fsf@halden.devel.redhat.com \
    --to=teg@redhat.com \
    --cc=jprice@cyberbuzz.gatech.edu \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).