From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: CVS snapshot qemu-img.c
Date: Mon, 02 Aug 2004 20:41:46 +0200 [thread overview]
Message-ID: <pan.2004.08.02.18.41.45.685808@reply.to> (raw)
In-Reply-To: pan.2004.08.02.12.39.34.945375@reply.to
Le Mon, 02 Aug 2004 14:39:39 +0200, Ronald a écrit :
> defining ENOTSUP 48 (defined in pthread.h) in qemu-img.c and block.c does
> not help a lot:
>
> i386-mingw32-gcc -DQEMU_TOOL -Wall -O2 -g -fno-strict-aliasing
> -fpack-struct -g -D_GNU_SOURCE -o qemu-img qemu-img.c block.c block-cow.c
> block-qcow.c aes.c block-vmdk.c -lz qemu-img.c: In function `img_info':
> qemu-img.c:644: structure has no member named `st_blocks' block.c: In
> function `get_tmp_filename': block.c:83: warning: implicit declaration of
> function `mkstemp' block.c: In function `raw_create':
> block.c:571: warning: implicit declaration of function `ftruncate64'
> block-qcow.c: In function `get_cluster_offset': block-qcow.c:353: warning:
> implicit declaration of function `ftruncate' block-qcow.c: In function
> `qcow_create': block-qcow.c:554: warning: implicit declaration of function
> `realpath' make: *** [qemu-img] Erreur 1
Some more infos:
not building qemu-img leads to make aborting later with:
block-qcow.o(.text+0xd5f):block-qcow.c: undefined reference to `ftruncate'
block-qcow.o(.text+0x154a):block-qcow.c: undefined reference to `realpath'
when linking qemu.exe
I have tried to define ftruncate and ftruncate64 to chsize and mkstemp to
mktemp, but can not find a replacement function for realpath.
prev parent reply other threads:[~2004-08-02 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 11:31 [Qemu-devel] CVS snapshot qemu-img.c mister pants
2004-08-02 12:39 ` [Qemu-devel] " Ronald
2004-08-02 18:41 ` Ronald [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=pan.2004.08.02.18.41.45.685808@reply.to \
--to=look@reply.to \
--cc=daimon55@free.fr \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).