From: Nigel Horne <676190@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 676190] Re: Latest git fails to link - missing main() routine
Date: Wed, 17 Nov 2010 01:09:59 -0000 [thread overview]
Message-ID: <4CE32B67.1090507@bandsman.co.uk> (raw)
In-Reply-To: AANLkTin1Vb6gEp0=K+M+rDa62GP16b-MK3eywiPcykjF@mail.gmail.com
On 11/16/2010 04:14 PM, Stefan Hajnoczi wrote:
> On Tue, Nov 16, 2010 at 6:37 PM, Nigel Horne<676190@bugs.launchpad.net> wrote:
>
>> Public bug reported:
>>
>> I can't get git 2834c3e0140c3b0ed4422909dfa0607b7213d95d to link on my
>> Debian Linux/x86_64 machine with gcc4.4:
>>
> Peter Maydell has submitted a patch to fix this:
> http://patchwork.ozlabs.org/patch/71449/
>
> I just tried it and it works for me.
>
> Stefan
>
>
Thanks for the quick turn around. I've closed the bug - it works for me
now as well.
Regards,
-Nigel
** Changed in: qemu
Status: New => Fix Released
--
Latest git fails to link - missing main() routine
https://bugs.launchpad.net/bugs/676190
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Fix Released
Bug description:
I can't get git 2834c3e0140c3b0ed4422909dfa0607b7213d95d to link on my Debian Linux/x86_64 machine with gcc4.4:
All goes well until the link stage:
/usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/crt1.o: In function `_start':
(.text+0x20): undefined reference to `main'
collect2: ld returned 1 exit status
make[1]: *** [trace] Error 1
make: *** [subdir-i386-softmmu] Error 2
I did
make distclean
./configure --enable-linux-aio --enable-io-thread --enable-kvm
prev parent reply other threads:[~2010-11-17 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 18:37 [Qemu-devel] [Bug 676190] [NEW] Latest git fails to link - missing main() routine Nigel Horne
2010-11-16 21:14 ` Stefan Hajnoczi
2010-11-17 1:09 ` Nigel Horne [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=4CE32B67.1090507@bandsman.co.uk \
--to=676190@bugs.launchpad.net \
--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).