From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17596 invoked by alias); 19 Mar 2004 04:18:32 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 17585 invoked from network); 19 Mar 2004 04:18:30 -0000 Received: from unknown (HELO mgr2.xmission.com) (198.60.22.202) by sources.redhat.com with SMTP; 19 Mar 2004 04:18:30 -0000 Received: from [198.60.22.201] (helo=mgr1.xmission.com) by mgr2.xmission.com with esmtp (Exim 3.35 #1) id 1B4BSn-0003S9-02; Thu, 18 Mar 2004 21:18:29 -0700 Received: from [198.60.22.20] (helo=xmission.xmission.com) by mgr1.xmission.com with esmtp (Exim 4.30) id 1B4BSn-0003gj-Rz; Thu, 18 Mar 2004 21:18:29 -0700 Received: from llewelly by xmission.xmission.com with local (Exim 3.35 #1 (Debian)) id 1B4BSn-0003PQ-00; Thu, 18 Mar 2004 21:18:29 -0700 To: Jeremy Kolb Cc: gcc-help@gcc.gnu.org References: <1079546410.23228.2.camel@glorfindel> From: llewelly@xmission.com Date: Fri, 19 Mar 2004 10:33:00 -0000 In-Reply-To: <1079546410.23228.2.camel@glorfindel> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Subject: Re: visibility attribute not supported?! Content-Type: text/plain; charset=us-ascii X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mgr1.xmission.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=8.0 tests=NO_REAL_NAME,PLING_QUERY autolearn=no version=2.63 X-SA-Exim-Mail-From: llewelly@xmission.com X-SA-Exim-Version: 3.1 (built Wed Aug 20 09:38:54 PDT 2003) X-SA-Exim-Scanned: Yes X-SW-Source: 2004-03/txt/msg00173.txt.bz2 Jeremy Kolb writes: > I'm running linux 2.6.3, gcc 3.3.3 on an amd t-bird. When I try to > compile glibc I get a warning about the visibility attribute not being > supported. I've tested this out with a test program that uses the > visibility attribute and that fails as well. So glibc won't build for > me. How do I enable the visibility attribute? I've recompiled binutils > and gcc but I still get the same error. First, make sure you are using fsf gcc 3.3.3 and not the derivative shipped by your distro maker (it seems all distros hand-roll their own gcc derivative ... don't ask me why.) If you can still reproduce with fsf gcc, I think you should report this as a bug. There's a similar bug reported against 3.4-branch: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13134 but it doesn't mention 3.3.3 .