This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: frv-elf-ld doesn't support the '-shared' option


Attempting a reply via the list.

----- Forwarded message from Mail Delivery System <MAILER-DAEMON@modra.org> -----
Content-Description: Delivery error report
Reporting-MTA: dns; bubble.modra.org
Arrival-Date: Tue, 25 Jan 2005 21:49:17 +1030 (CST)

Final-Recipient: rfc822; zhanrk@163.com
Action: failed
Status: 4.0.0
Diagnostic-Code: X-Postfix; connect to mx.mail.163.com[202.108.44.203]: server
    refused mail service

Content-Description: Undelivered Message
Date: Tue, 25 Jan 2005 21:49:17 +1030
From: Alan Modra <amodra@bigpond.net.au>
To: zhanrk <zhanrk@163.com>
Subject: Re: Re: frv-elf-ld doesn't support the '-shared' option

On Tue, Jan 25, 2005 at 06:53:46PM +0800, zhanrk wrote:
> Thanks very much. Is the target 'frv-elf' used to compile the stand alone programs?

Yes, I believe it is for embedded systems.

> It seems that the binutils have three targets: 'frv-elf', 'frv-uclinux' and 'frv-linux'. But gcc *only* has one target: 'frv-elf'! 

Well, frv-uclinux and frv-linux are the same target.

> Why? And how can i know what targets are supported by binutils/gcc packages ?

You can find supported targets by looking in various configure scripts,

eg. ld/configure.tgt
frv-*-*linux*)          targ_emul=elf32frvfd ;;
frv-*-*)                targ_emul=elf32frv ; targ_extra_emuls="elf32frvfd" ;;

It might be that you need a newer version of gcc to find frv-linux
support.  CVS head gcc has
$ grep frv config.gcc
*-*-linux* | frv-*-*linux* | *-*-kfreebsd*-gnu | *-*-knetbsd*-gnu)
frv-*-elf)
        tm_file="dbxelf.h elfos.h svr4.h ${tm_file} frv/frv-abi.h"
        tmake_file=frv/t-frv
frv-*-*linux*)
                 linux.h frv/linux.h frv/frv-abi.h"
        tmake_file="${tmake_file} frv/t-frv frv/t-linux"
    frv-*-*linux*)


> The target 'frv-uclinux' is used to compile/link the applications for uClinux (no MMU)? While the target 'frv-linux' is used to compile/link the applications for MMU linux? 

I don't know enough about frv to answer questions about mmu or lack of
mmu.

> Can i use the toolchain whose configure target is frv-linux to compile/link an application program which will run on an uClinux machine? and vice versa?

They will almost certainly produce the same code.  However, it pays to
keep the names exactly the same when configuring the various toolchain
pieces.  eg. If configuring gcc for frv-linux, the gcc configure scripts
will look for frv-linux-as, frv-linux-ld etc.  It won't find these if
you have frv-uclinux-as etc. installed, so could fall back to using the
system as and ld (which would fail).  For similar reasons, it pays to
use the same --prefix when configuring.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre


----- End forwarded message -----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]