From: "Koundinya.K" <kk@ddeorg.soft.net>
To: mark@codesourcery.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: MIPS linker status
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <199906151107.QAA04923@madras.ddeorg.soft.net> (raw)
In-Reply-To: <19990615013258W.mitchell@codesourcery.com>
Hi !,
mark@codesourcery.com said:
-> I've made good progress with the IRIX6 port of GNU ld. I expect to
-> have preliminary patches good enough for basic N32 functionality ready
-> for submission within the next two weeks at the outside.
That sounds great !.
-> I've found a lot of problems that look like they would affect IRIX5,
-> and probably other MIPS ABI platforms. (For example, utter garbage in
-> the GOT.) Is anybody actually using GNU ld on other MIPS platforms?
-> If so, are they creating dynamic executables?
Yes I have been using the GNU linker for my MIPS ( R4400) based System
running the SVR4.2 UNIX from Dansk Data Electronik A/S , which is MIPS ABI (
version 1.2) Compliant. The reference platform suggested by MIPS ABI is IRIX
6.2.
But to get the GNU linker working I had to build those startup files ( crt*)
stuff by myself. But still I am not able to use the linker to generate
statically linked executables. I am however able to create the dynamic
executables.
-> I'm curious because I'm wondering when I look at code whether it's
-> just not right for IRIX6, or not right in general.
Though for systems confirming to MIPS ABI version 1.2 , the recommended
platform is IRIX6.2 or something, but I found that IRIX6* has a different
way of doing things compared to IRIX5*. I do not have access to any IRIX
machine here. But reading some documentation made me think so.
Cheers !!
Koundinya
-> Thanks !
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 mark
1999-07-01 0:00 ` Koundinya.K [this message]
1999-07-01 0:00 ` Ralf Baechle
1999-07-01 0:00 ` Ian Lance Taylor
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=199906151107.QAA04923@madras.ddeorg.soft.net \
--to=kk@ddeorg.soft.net \
--cc=binutils@sourceware.cygnus.com \
--cc=mark@codesourcery.com \
/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).