public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Torsten Becker <ghostlinktb@yahoo.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: error
Date: Mon, 28 May 2001 14:36:00 -0000	[thread overview]
Message-ID: <org0dpma09.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20010528103616.99393.qmail@web13605.mail.yahoo.com>

On May 28, 2001, Torsten Becker <ghostlinktb@yahoo.de> wrote:

> Hello, who could help? What means these error messege?
> I use uClinux!

> ucLinux:/home/torsten/c_stuff # m68k-pic-coff-gcc
> key.c -o key
> /tmp/cca006321.o(.text+0x56):key.c: undefined
> reference to `$0700'

Looks like the assembler misunderstood this constant as a symbol.  Are
you sure you're using an appropriate assembler for this platform?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

  reply	other threads:[~2001-05-28 14:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-28  3:36 error Torsten Becker
2001-05-28 14:36 ` Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22  0:45 error Bill Cunningham
2019-11-01  1:44 Error pen1979871192
2007-10-13  1:09 error jay caverte
2007-10-13  1:25 ` error Brian Dessent
2005-04-13 22:39 Error Dean Margell
2002-05-12  8:50 Error Rahul  it
2002-05-12  9:27 ` Error bjorn rohde jensen
2002-05-12 20:44   ` Error David Dudley
2001-05-28  3:22 error Torsten Becker
2001-02-07  7:57 error Edmond Kereku
2000-01-14 14:03 Error DarkSprrow
2000-04-01  0:00 ` Error DarkSprrow

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=org0dpma09.fsf@guarana.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ghostlinktb@yahoo.de \
    /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).