public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/34957] duplicate libgcc_s.1.dylib warning on Mac OS X Leopard
Date: Sat, 26 Jan 2008 01:11:00 -0000	[thread overview]
Message-ID: <20080126000509.23242.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34957-15598@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from dominiq at lps dot ens dot fr  2008-01-26 00:05 -------
> This should have been fixed by 30572.

I was thinking to this one. This is why I asked to check there was some files
/libgcc_s*, just in case the package installed it.

I don't understand the problem: I am using Leopard and gcc works rather well
with it: probably less bugs than with 10.4 (cannot remember the cat!-).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34957


  parent reply	other threads:[~2008-01-26  0:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 19:05 [Bug fortran/34957] New: " dojo at masterleep dot com
2008-01-25 17:06 ` [Bug fortran/34957] " dominiq at lps dot ens dot fr
2008-01-25 18:37 ` dojo at masterleep dot com
2008-01-25 18:54 ` dominiq at lps dot ens dot fr
2008-01-25 22:38 ` dojo at masterleep dot com
2008-01-25 22:48 ` dominiq at lps dot ens dot fr
2008-01-26  0:43 ` [Bug target/34957] " pinskia at gcc dot gnu dot org
2008-01-26  1:11 ` dominiq at lps dot ens dot fr [this message]
2009-04-24  3:29 ` fago at earthlink dot net
     [not found] <bug-34957-4@http.gcc.gnu.org/bugzilla/>
2014-11-04  0:08 ` fxcoudert at gcc dot gnu.org

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=20080126000509.23242.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).