All of lore.kernel.org
 help / color / mirror / Atom feed
From: "T. P. Saravanan" <sara@procsys.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: mips linux glibc-2.3.3 build - Assembler errors in rtld.c
Date: Thu, 07 Oct 2004 09:56:44 +0530	[thread overview]
Message-ID: <4164C584.60801@procsys.com> (raw)
In-Reply-To: <20041005.191608.59649656.nemoto@toshiba-tops.co.jp>

Atsushi Nemoto wrote:

>>>>>>On Tue, 05 Oct 2004 15:20:53 +0530, "T. P. Saravanan" <sara@procsys.com> said:
>>>>>>            
>>>>>>
>sara> glibc-2.2.3 build on mips linux breaks with following assembler errors:
>...
>sara> /tmp/ccNhjRu0.s: Assembler messages:
>sara> /tmp/ccNhjRu0.s:48: Warning: missing .end
>sara> /tmp/ccNhjRu0.s:80: Warning: No .frame pseudo-op used in PIC code
>sara> /tmp/ccNhjRu0.s:88: Warning: .end directive without a preceding .ent 
>
>This is now fixed in libc CVS.
>
>http://sources.redhat.com/ml/libc-alpha/2004-04/msg00078.html
>
>Also, you might have to pass -fno-unit-at-a-time to gcc 3.4.  (at
>least glibc 2.3.2 requires it).
>
>  
>
I merged the patch int the URL you gave.  It worked.  Thanks.

(But now I am getting a linker error.  I will post it seperately.)

-Sa.

      parent reply	other threads:[~2004-10-07  4:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05  9:50 mips linux glibc-2.3.3 build - Assembler errors in rtld.c T. P. Saravanan
2004-10-05 10:16 ` Atsushi Nemoto
2004-10-05 10:53   ` Maciej W. Rozycki
2004-10-05 12:17     ` Jan-Benedict Glaw
2004-10-05 20:15       ` Maciej W. Rozycki
2004-10-05 20:40         ` Jan-Benedict Glaw
2004-10-07  4:26   ` T. P. Saravanan [this message]

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=4164C584.60801@procsys.com \
    --to=sara@procsys.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.