public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: visibility attribute not supported?!
@ 2004-03-23 18:44 Jeremy Kolb
  0 siblings, 0 replies; 5+ messages in thread
From: Jeremy Kolb @ 2004-03-23 18:44 UTC (permalink / raw)
  To: gcc-help

[-- Attachment #1: Type: text/plain, Size: 129 bytes --]

I've posted this to bugzilla but no one's really responded. There was
one response but it did not help. Please help.

Jermey

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: visibility attribute not supported?!
  2004-03-19 17:37   ` Jeremy Kolb
@ 2004-03-19 20:24     ` llewelly
  0 siblings, 0 replies; 5+ messages in thread
From: llewelly @ 2004-03-19 20:24 UTC (permalink / raw)
  To: Jeremy Kolb; +Cc: gcc-help

Jeremy Kolb <jkolb@brandeis.edu> writes:

> Yeah It's stock fsf gcc. The distro I use is Sourcemage and it downloads
> from gcc directly from the gnu site (and it's md5 verified).  The thing
> is this has only happened to a few people and not the rest, we don't
> know why.

As near as I can tell, gcc should build with visibility support iff
    you are using gnu ld.

Since you are running linux, I can't imagine you might be using
    anything else. So I suspect a bug somewheres. When you file a bug
    report, you should include the output of ld --version, gcc
    --version, and uname -a, in addition to the info requested at
    gcc.gnu.org/bugs.html .

I suppose you could reconfigure and rebuild gcc, adding --with-gnu-ld
    to your configure arguments, but it seems a bug that that should
    be necessary on a platform where SFAIK only gnu ld is available.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: visibility attribute not supported?!
  2004-03-19 10:33 ` llewelly
@ 2004-03-19 17:37   ` Jeremy Kolb
  2004-03-19 20:24     ` llewelly
  0 siblings, 1 reply; 5+ messages in thread
From: Jeremy Kolb @ 2004-03-19 17:37 UTC (permalink / raw)
  To: llewelly; +Cc: gcc-help

Yeah It's stock fsf gcc. The distro I use is Sourcemage and it downloads
from gcc directly from the gnu site (and it's md5 verified).  The thing
is this has only happened to a few people and not the rest, we don't
know why.

Jeremy

On Thu, 2004-03-18 at 23:18, llewelly@xmission.com wrote:
> Jeremy Kolb <jkolb@brandeis.edu> 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 .
> 

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: visibility attribute not supported?!
  2004-03-17 22:17 Jeremy Kolb
@ 2004-03-19 10:33 ` llewelly
  2004-03-19 17:37   ` Jeremy Kolb
  0 siblings, 1 reply; 5+ messages in thread
From: llewelly @ 2004-03-19 10:33 UTC (permalink / raw)
  To: Jeremy Kolb; +Cc: gcc-help

Jeremy Kolb <jkolb@brandeis.edu> 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 .

^ permalink raw reply	[flat|nested] 5+ messages in thread

* visibility attribute not supported?!
@ 2004-03-17 22:17 Jeremy Kolb
  2004-03-19 10:33 ` llewelly
  0 siblings, 1 reply; 5+ messages in thread
From: Jeremy Kolb @ 2004-03-17 22:17 UTC (permalink / raw)
  To: gcc-help

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.

Jeremy

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-03-23 17:16 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-23 18:44 visibility attribute not supported?! Jeremy Kolb
  -- strict thread matches above, loose matches on Subject: below --
2004-03-17 22:17 Jeremy Kolb
2004-03-19 10:33 ` llewelly
2004-03-19 17:37   ` Jeremy Kolb
2004-03-19 20:24     ` llewelly

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).