public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: Andre Heidenreich <andre@swol.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: undefined reference
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <orvh41btk0.fsf@garnize.lsd.ic.unicamp.br> (raw)
Message-ID: <20000401000000.F00WQFbHzstW-a2Wn4Wwc3wWMh1rPIQJUS063vFQ78U@z> (raw)
In-Reply-To: <Pine.LNX.4.10.10002031202480.869-100000@deathvalley.darknet.de>

On Feb  4, 2000, Andre Heidenreich <andre@swol.de> wrote:

> i've a problem when i compiling and linking glibc-2.1.2.

This is not really the place to ask for help on installing glibc.  How
about writing to a glibc mailing list?

> 0000000000032280 t __libc_global_ctors

> why are there errors during linking?

`t' indicates a local symbol, i.e., one that is not available to other
libraries/objects.

-- 
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them

  reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-04  8:18 Andre Heidenreich
2000-02-06 19:06 ` Alexandre Oliva [this message]
2000-04-01  0:00   ` Alexandre Oliva
2000-04-01  0:00 ` Andre Heidenreich
2002-10-29 17:22 Undefined Reference Vincent Lee
2002-10-30  1:06 ` bjorn rohde jensen
2004-09-11 15:35 undefined reference zippo
2004-09-11 15:58 ` Eljay Love-Jensen
2004-09-11 20:00   ` zippo
2004-09-11 23:35     ` Eljay Love-Jensen
     [not found] <CA+JCqFYCePkAWFyUv5gp4rZbMUL8j71hBxY6=-4ju2DduhpCGA@mail.gmail.com>
2022-06-05 13:03 ` renwang101
2022-06-05 22:07   ` fedor_qd
2022-06-05 22:54     ` renwang101

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=orvh41btk0.fsf@garnize.lsd.ic.unicamp.br \
    --to=oliva@lsd.ic.unicamp.br \
    --cc=andre@swol.de \
    --cc=gcc-help@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).