public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/18804] [4.0 Regression] lib2funcs.vis:1: Error: unknown pseudo-op: `.hidden'
Date: Sat, 04 Dec 2004 02:13:00 -0000	[thread overview]
Message-ID: <20041204021334.12490.qmail@sourceware.org> (raw)
In-Reply-To: <20041203033039.18804.danglin@gcc.gnu.org>


------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca  2004-12-04 02:13 -------
Subject: Re:  [4.0 Regression] lib2funcs.vis:1: Error: un

> > Sounds like libgcc/./lib2funcs.vis is wrong and should not have .hidden in
> > it.
> 
> Yup:
> 
> -bash-2.05b$ less libgcc/./lib2funcs.vis
>         .hidden __gcc_plt_call

>From the build log:

nm -pg libgcc/./lib2funcs_s.o | gawk 'NF == 3 && $2 !~ /^[UN]$/ { print "
.hidden", $3 }' > libgcc/./lib2funcs.visT
mv -f libgcc/./lib2funcs.visT libgcc/./lib2funcs.vis

Dave


-- 


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


  parent reply	other threads:[~2004-12-04  2:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03  3:30 [Bug bootstrap/18804] New: " danglin at gcc dot gnu dot org
2004-12-03  3:31 ` [Bug bootstrap/18804] " danglin at gcc dot gnu dot org
2004-12-03  3:35 ` pinskia at gcc dot gnu dot org
2004-12-04  2:01 ` dave at hiauly1 dot hia dot nrc dot ca
2004-12-04  2:13 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2004-12-04  2:17 ` pinskia at gcc dot gnu dot org
2004-12-04  3:06 ` pinskia at gcc dot gnu dot org
2004-12-04  3:15 ` dave at hiauly1 dot hia dot nrc dot ca
2004-12-04  3:38 ` zack at gcc dot gnu dot org
2004-12-04 20:33 ` cvs-commit at gcc dot gnu dot org
2004-12-04 20:35 ` danglin at gcc dot gnu dot org
2004-12-04 20:36 ` pinskia at gcc dot gnu dot 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=20041204021334.12490.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).