This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
[Fwd: mips-pe target]
- From: Kai Ruottu <kai dot ruottu at luukku dot com>
- To: binutils at sources dot redhat dot com
- Date: Tue, 03 Jun 2003 10:30:43 +0300
- Subject: [Fwd: mips-pe target]
- Reply-to: kai dot ruottu at luukku dot com
Daniel Jacobowitz wrote:
> On Mon, Jun 02, 2003 at 10:49:02AM -0700, Eric Christopher wrote:
>
>>On Mon, 2003-06-02 at 09:58, Daniel Jacobowitz wrote:
>>
>>>On Fri, Apr 11, 2003 at 12:29:21AM -0700, Eric Christopher wrote:
>>>
>>>>On Wed, 2003-04-09 at 01:01, Alan Modra wrote:
>>>>
>>>>>Both of these targets fail with
>>>>>tc-mips.o(.rodata+0x2a4): In function `md_begin':
>>>>>.../gas/config/tc-mips.c:1258: undefined reference to
`ecoff_directive_extern'
>>>>>
>>>>>They also failed with 2.13. The lack of bug reports (besides mine)
>>>>>says to me that there are zero users for these targets. Let's
remove
>>>>>the configury bits before 2.14 goes out the door.
If bug reports (unofficial and on wrong maillist) are wished, the
attachment contains one coming from China...
I tried the binutils-2.13.2.1 sources for 'mips-wince-pe' and met the
same bug and a short study told that wrapping this member in the MIPS
pseudo-op table could fix it:
------------- clip -----------------------------
static const pseudo_typeS mips_pseudo_table[] =
{
/* MIPS specific pseudo-ops. */
<snip>
{"word", s_cons, 2},
#ifndef NO_ECOFF_DEBUGGING
{ "extern", ecoff_directive_extern, 0},
#endif
{ NULL, NULL, 0 },
};
------------- clip -----------------------------
I couldn't easily produce a diff just now, so this was taken from
the fixed 'gas/config/tc-mips.c'. Surprisingly Wreckor didn't mention
the bug and the fix made for it...
Of couse the 'mips-wince-pe', 'mips-mingw32' etc. possible targets
with the MIPS/PE format have very minimal or zero support in the GCC
sources, but this is a separate issue.
>>Probably print an obsolete message and fail. If someone cares they'll
>>mail the list.
I really don't care but there can be others like Wreckor who do care
about the 'mips-pe' support and post to some list, not necessarily to
the right one...
Cheers, Kai
--- Begin Message ---
- From: "longchuan" <longchuan at koretide dot com dot cn>
- To: "'Crossgcc'" <crossgcc at sources dot redhat dot com>
- Date: Fri, 23 May 2003 11:16:55 +0800
- Subject: mips-pe target
hello all:
Does binutils support for mips-pe target support? or what exactly target
alias should i use when configure it? I am working on Win2k.
I build the whole toolchain of gcc( gcc 3.2, binutils 2.13, newlib
1.11.0), configured with target=mips-pe, and not yet test the result.
But when i use dlltool, I got some bad news:
dlltool -C -d test.def -e test.exp -D test.dll -l test.lib
dlltool: Machine 'mips' not supported
dlltool --help
Usage dlltool <option(s)> <object-file(s)>
-m --machine <machine> Create as DLL for <machine>. [default:
mips]
possible <machine>: arm[_interwork], i386, mcore[-elf]{-le|-be},
ppc, thumb
......
Although the toolchain contains dlltool, but seems to me that this
dlltool doesn't support mips cpu?
Could anybody tell me something about this target( or mips*-*-pe)? Had
gcc been ported for that?
I looked through google, but few information.
thanks,
wreckor
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
--- End Message ---