From: Srujan Kotikela <ksrujandas@gmail.com>
To: xen-devel@lists.xensource.com
Cc: Lakshitha Harshan <harshan.dll@gmail.com>
Subject: Re: Hi all,
Date: Sun, 3 Apr 2011 09:23:11 -0500 [thread overview]
Message-ID: <BANLkTikMNpJvGxH0CDBBD91cNedh3M7Aeg@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimytzKnn8xvezzGaAhzwWzmnXCQ+7=HUC=xW07Z@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
Hi,
though I am not of great authority at *this* low-level stuff, I think the
file you mentioned is using "glibc" to generate 32-bit elf images. I do not
think you can use it for other purposes. Try if you can use other
alternatives for fopen for your particular problem.
If you can give more details on exactly what you are trying to do, some
others might help you.
--
Srujan D. Kotikela
On Sat, Apr 2, 2011 at 11:33 PM, Lakshitha Harshan <harshan.dll@gmail.com>wrote:
> Hi,
>
> I forgot to mention in previous mail. The thing is that
> xen/arch/x86/boot/mkelf32.c uses stdio.h and if I include fopen function in
> mkelf32.c, it will compile fine and generates xen.gz. I'm really confused on
> that.
> If you have any idea on that please let me know that.
>
> Regards,
> Harshan
>
>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 1262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-04-03 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 5:35 Hi all, Lakshitha Harshan
[not found] ` <AANLkTi=VS+_5YkcuvLqa_W1EGTyOk4D0YKrDwEdBeeUq@mail.gmail.com>
[not found] ` <AANLkTi=9D4LuQcqombfQKejoAwDeLPiS7GKFu7TTrgM6@mail.gmail.com>
2011-04-03 4:11 ` Srujan Kotikela
[not found] ` <AANLkTikcO2pJAxVDOG7tnHdH-qk4bBPYuic3dEk0TE8D@mail.gmail.com>
[not found] ` <AANLkTimytzKnn8xvezzGaAhzwWzmnXCQ+7=HUC=xW07Z@mail.gmail.com>
2011-04-03 14:23 ` Srujan Kotikela [this message]
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=BANLkTikMNpJvGxH0CDBBD91cNedh3M7Aeg@mail.gmail.com \
--to=ksrujandas@gmail.com \
--cc=harshan.dll@gmail.com \
--cc=xen-devel@lists.xensource.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 NNTP newsgroup(s).