public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Bhushan Verma" <bhushan.verma@iap-online.com>
To: "Nick Clifton" <nickc@redhat.com>
Cc: <binutils@sourceware.org>
Subject: RE: Regarding linker code generation
Date: Tue, 04 Sep 2007 08:23:00 -0000	[thread overview]
Message-ID: <OIEOKFKBHBJGOGBPDDFIAEJCCBAA.bhushan.verma@iap-online.com> (raw)
In-Reply-To: <46D83277.5030909@redhat.com>

Dear  Nick,

We got the solution  that generate separate code and data segment by
updating tool chain.
Since someone build this tool chain now this is rebuild .I think there was
some problem in building tool chain.

Now problem is that we are unable to give the execute permission (RWX) to
data segment.
This is requirement for  run time linker.
Could you please help me how can I do this ,is there any provision to change
the default linker script.
I mean how can I change default linker script which gives execute permission
to linker.


Regards
Bhushan



-----Original Message-----
From: Nick Clifton [mailto:nickc@redhat.com]
Sent: Saturday, September 01, 2007 12:24 AM
To: Bhushan Verma
Cc: binutils@sourceware.org
Subject: Re: Regarding linker code generation


Hi Bhushan,

> I am using 2.17 linker version.
> I do know know how this is happening?
> There can be some environment problem.

Possibly.  Please could you generate a simple test case that demonstrates
this
problem, so that we can investigate it ?

Cheers
   Nick


  reply	other threads:[~2007-09-04  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1185763943.19324.ezmlm@sourceware.org>
2007-07-30 14:24 ` Bhushan Verma
2007-08-01 17:38   ` Nick Clifton
2007-08-02  1:21     ` Bhushan Verma
2007-08-06 15:28       ` Nick Clifton
2007-08-13  7:45         ` Bhushan Verma
2007-08-31 20:53           ` Nick Clifton
2007-09-04  8:23             ` Bhushan Verma [this message]
2007-09-07 15:38               ` Nick Clifton

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=OIEOKFKBHBJGOGBPDDFIAEJCCBAA.bhushan.verma@iap-online.com \
    --to=bhushan.verma@iap-online.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.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).