public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "CARTER-HITCHIN, David, GBM" <David.CARTER-HITCHIN@rbos.com>
To: "'H. J. Lu'" <hjl@lucon.org>
Cc: "'binutils@sourceware.org'" <binutils@sourceware.org>
Subject: RE: Compiling and linking 32 bit code on a 64 machine (AMD Optero 	n)
Date: Fri, 23 Jun 2006 16:59:00 -0000	[thread overview]
Message-ID: <3B4C77997DD0254B86D3C9454476B6BC057A92@lonms00812.fm.rbsgrp.net> (raw)

Hi HJ

Thanks for replying.

I've built a testcase: I've got a 6 line Makefile, a 5 line helloworld
source file and 238 lines of linker output.  Shall I post those here, or is
there a better place?

Thanks,

David Carter-Hitchin.
--
Royal Bank of Scotland
Interest Rate Derivatives IT
135 Bishopsgate
LONDON EC2M 3TP

Tel: +44 (0) 207 085 1088


> -----Original Message-----
> From: H. J. Lu [mailto:hjl@lucon.org] 
> Sent: 23 June 2006 16:45
> To: CARTER-HITCHIN, David, GBM
> Cc: 'binutils@sourceware.org'
> Subject: Re: Compiling and linking 32 bit code on a 64 
> machine (AMD Optero n)
> 
> 
> On Fri, Jun 23, 2006 at 04:36:11PM +0100, CARTER-HITCHIN, 
> David, GBM wrote:
> > Hi,
> > 
> > Looking more closely at the output of --verbose, I've realised that
> > /usr/lib64/crti.o *is* being linked in, how can I stop ld from doing
> > that?  The info page says that -L paths should override the default
> > ones, but clearly this is not happening. Should I submit a 
> bug report
> > or am I missing something?
> > 
> 
> It shouldn't happen. Please provide a complete testcase to show what
> really happened.
> 
> 
> H.J.
> 

***********************************************************************************
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
Authorized and regulated by the Financial Services Authority 
 
This e-mail message is confidential and for use by the 
addressee only. If the message is received by anyone other 
than the addressee, please return the message to the sender 
by replying to it and then delete the message from your 
computer. Internet e-mails are not necessarily secure. The 
Royal Bank of Scotland plc does not accept responsibility for 
changes made to this message after it was sent. 

Whilst all reasonable care has been taken to avoid the 
transmission of viruses, it is the responsibility of the recipient to 
ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its 
systems or data. No responsibility is accepted by The Royal 
Bank of Scotland plc in this regard and the recipient should carry 
out such virus and other checks as it considers appropriate. 
Visit our websites at: 
http://www.rbos.com
http://www.rbsmarkets.com 
***********************************************************************************

             reply	other threads:[~2006-06-23 16:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 16:59 CARTER-HITCHIN, David, GBM [this message]
2006-06-23 17:21 ` H. J. Lu
  -- strict thread matches above, loose matches on Subject: below --
2006-06-23 23:11 CARTER-HITCHIN, David, GBM
2006-06-23 23:01 CARTER-HITCHIN, David, GBM
2006-06-23 17:28 CARTER-HITCHIN, David, GBM
2006-06-23 17:30 ` Daniel Jacobowitz
2006-06-23 18:12 ` H. J. Lu
2006-06-23 15:44 CARTER-HITCHIN, David, GBM
2006-06-23 15:55 ` H. J. Lu

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=3B4C77997DD0254B86D3C9454476B6BC057A92@lonms00812.fm.rbsgrp.net \
    --to=david.carter-hitchin@rbos.com \
    --cc=binutils@sourceware.org \
    --cc=hjl@lucon.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 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).