zsh-workers
 help / color / mirror / code / Atom feed
From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
To: zsh-workers@sunsite.dk
Cc: Jason Price <jprice@cyberbuzz.gatech.edu>
Subject: Re: gcc 3.0 produces broken zsh
Date: Sat, 23 Jun 2001 22:24:49 +0400	[thread overview]
Message-ID: <3B34DEF1.7010701@mow.siemens.ru> (raw)
In-Reply-To: <002301c0faff$339a0430$21c9ca95@mow.siemens.ru>

Andrej Borsenkow wrote:

> 
> Everything is nice, no errors, everything properly defined but does not
> work. I'll try to get a look at weekend with gcc3 on Mandrake cooker.
> 


Unfortunately, it works here using gcc3.0 from cooker contrib and 
(mostly) up-to-date cooker.

{pts/1}% rpm -qa | grep gcc3.0
gcc3.0-cpp-3.0-1mdk
gcc3.0-3.0-1mdk
libgcc3.0-3.0-1mdk

The one warning I got is

gcc -V 3.0   -shared -o zleparameter.so   zleparameter..o    -ldl -lnsl 
-ltermcap -lm  -lc
gcc: Spec failure: Unrecognised spec option 'M'
gcc: Spec failure: Unrecognised spec option 'M'

that I presume is related to this spec line:
*libgcc:
%{shared-libgcc:-lgcc_s%M 
-lgcc}%{static-libgcc:-lgcc}%{!shared-libgcc:%{!static-libgcc:%{shared:-lgcc_s%M 
-lgcc}}}%{!shared-libgcc:%{!static-libgcc:%{!shared:-lgcc}}}

(Chmou, would you look into it?) but in spite of it all tests passed.


Cannot speak about CVS version off GCC but released seems to work.

-andrej


  parent reply	other threads:[~2001-06-23 18:22 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
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 [this message]
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=3B34DEF1.7010701@mow.siemens.ru \
    --to=andrej.borsenkow@mow.siemens.ru \
    --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).