> From: Peter Maydell
> Subject: Re: [Qemu-devel] [build-error] possible build error at the tip of >
> the trunk? (dtc-related?)
>
> On Mon, 11 Mar 2019 at 16:59, Aleksandar Markovic
> wrote:
> >
> > Hello, all
> >
> > All of the sudden, the la
On Mon, 11 Mar 2019 at 16:59, Aleksandar Markovic
wrote:
>
> Hello, all
>
> All of the sudden, the latest code doesn't build on my host: (the code from
> several days ago builds fine)
>
> Do you know what would be the culprit? Is it my environment, or a genuine
> build error?
Hi -- we've now co
On Wed, Mar 13, 2019 at 01:14:35PM +, Peter Maydell wrote:
> On Wed, 13 Mar 2019 at 12:09, Stefan Hajnoczi wrote:
> >
> > On Mon, Mar 11, 2019 at 04:49:15PM +, Aleksandar Markovic wrote:
> > > Hello, all
> > >
> > > All of the sudden, the latest code doesn't build on my host: (the code
>
On Wed, 13 Mar 2019 at 12:09, Stefan Hajnoczi wrote:
>
> On Mon, Mar 11, 2019 at 04:49:15PM +, Aleksandar Markovic wrote:
> > Hello, all
> >
> > All of the sudden, the latest code doesn't build on my host: (the code from
> > several days ago builds fine)
> >
> > Do you know what would be the
On Mon, Mar 11, 2019 at 04:49:15PM +, Aleksandar Markovic wrote:
> Hello, all
>
> All of the sudden, the latest code doesn't build on my host: (the code from
> several days ago builds fine)
>
> Do you know what would be the culprit? Is it my environment, or a genuine
> build error?
CCing J
Hello, all
All of the sudden, the latest code doesn't build on my host: (the code from
several days ago builds fine)
Do you know what would be the culprit? Is it my environment, or a genuine build
error?
Thanks in advance!
Aleksandar
rtrk@rtrkw774-lin:~/qemu-tot$ ./configure
Install prefix
On 26/02/2019 12.05, Peter Maydell wrote:
> On Tue, 26 Feb 2019 at 09:06, Thomas Huth wrote:
>> Ok, then that's the problem here: GCC often produces some additional
>> "may be unused" warnings with -O3, and we normally only guarantee that
>> QEMU compiles without warnings when using the standard -
On Tue, 26 Feb 2019 at 09:06, Thomas Huth wrote:
> Ok, then that's the problem here: GCC often produces some additional
> "may be unused" warnings with -O3, and we normally only guarantee that
> QEMU compiles without warnings when using the standard -O2 optimization
> level.
> So if you want to co
В сообщении от Tuesday 26 February 2019 12:58:11 вы написали:
> On 26/02/2019 10.46, Andrew Randrianasulu wrote:
> [...]
>
> > also, -g 1186x864x32 resulted in funnuy diagonal corruption even at
> > firmware screen level, and probably same happening with x86-64/kvm guest
> > if I select some less c
On 26/02/2019 10.46, Andrew Randrianasulu wrote:
[...]
> also, -g 1186x864x32 resulted in funnuy diagonal corruption even at firmware
> screen level, and probably same happening with x86-64/kvm guest if I select
> some less comon, but exposed via xrandr mode. (this bit for -vga std, default)
118
В сообщении от Tuesday 26 February 2019 12:05:02 Thomas Huth написал(а):
> On 26/02/2019 09.58, Andrew Randrianasulu wrote:
> > В сообщении от Tuesday 26 February 2019 11:54:12 вы написали:
> >> On 25/02/2019 18.29, Andrew Randrianasulu wrote:
> >>> В сообщении от Monday 25 February 2019 19:19:01 P
On 26/02/2019 09.58, Andrew Randrianasulu wrote:
> В сообщении от Tuesday 26 February 2019 11:54:12 вы написали:
>> On 25/02/2019 18.29, Andrew Randrianasulu wrote:
>>> В сообщении от Monday 25 February 2019 19:19:01 Philippe Mathieu-Daudc3a9
>>>
>>> написал(а):
Hi Andrew,
On 2/23/19
В сообщении от Tuesday 26 February 2019 11:54:12 вы написали:
> On 25/02/2019 18.29, Andrew Randrianasulu wrote:
> > В сообщении от Monday 25 February 2019 19:19:01 Philippe Mathieu-Daudc3a9
> >
> > написал(а):
> >> Hi Andrew,
> >>
> >> On 2/23/19 1:35 AM, Andrew Randrianasulu wrote:
> >>> Hello!
>
On 25/02/2019 18.29, Andrew Randrianasulu wrote:
> В сообщении от Monday 25 February 2019 19:19:01 Philippe Mathieu-Daudc3a9
> написал(а):
>> Hi Andrew,
>>
>> On 2/23/19 1:35 AM, Andrew Randrianasulu wrote:
>>> Hello!
>>>
>>> I just pulled latest git
>>
>> [...]
>>
>>> and default build with simpl
В сообщении от Monday 25 February 2019 19:19:01 Philippe Mathieu-Daudc3a9
написал(а):
> Hi Andrew,
>
> On 2/23/19 1:35 AM, Andrew Randrianasulu wrote:
> > Hello!
> >
> > I just pulled latest git
>
> [...]
>
> > and default build with simple ./configure on slackware 14.2 x86-64 box
> > failed like
Hi Andrew,
On 2/23/19 1:35 AM, Andrew Randrianasulu wrote:
> Hello!
>
> I just pulled latest git
>
[...]
>
> and default build with simple ./configure on slackware 14.2 x86-64 box failed
> like this:
>
> root@slax:~/src/qemu# LANG=C make -j 5
> CHK version_gen.h
> CC qobject/bl
Adding people in cc based on 'scripts/get-maintainer.pl -f
qobject/block-qdict.c'
On 2/22/19 6:35 PM, Andrew Randrianasulu wrote:
> Hello!
>
> I just pulled latest git
>
> up to
> commit 8eb29f1bf5a974dc4c11d2d1f5e7c7f7a62be116 (HEAD -> master,
> origin/master,
> origin/HEAD)
> Merge: a05838c
Hello!
I just pulled latest git
up to
commit 8eb29f1bf5a974dc4c11d2d1f5e7c7f7a62be116 (HEAD -> master, origin/master,
origin/HEAD)
Merge: a05838cb2a 2b6326c0bf
Author: Peter Maydell
Date: Fri Feb 22 15:48:04 2019 +
Merge remote-tracking branch
'remotes/awilliam/tags/vfio-updates-20
Thanks. Out-of-tree build worked (with make distclean before checking out
new commit).
On Tue, Jun 10, 2014 at 5:53 PM, Peter Maydell
wrote:
> On 10 June 2014 13:03, Sai Prajeeth wrote:
> > Hi,
> > I am getting this error if i try to build qemu.
> >
> > libqemuutil.a(oslib-posix.o): In functio
On 10 June 2014 13:03, Sai Prajeeth wrote:
> Hi,
> I am getting this error if i try to build qemu.
>
> libqemuutil.a(oslib-posix.o): In function `qemu_anon_ram_alloc':
> /util/oslib-posix.c:141: undefined reference to `trace_qemu_anon_ram_alloc'
> libqemuutil.a(oslib-posix.o): In function `qemu_an
Hi,
I am getting this error if i try to build qemu.
libqemuutil.a(oslib-posix.o): In function `qemu_anon_ram_alloc':
/util/oslib-posix.c:141: undefined reference to `trace_qemu_anon_ram_alloc'
libqemuutil.a(oslib-posix.o): In function `qemu_anon_ram_free':
/util/oslib-posix.c:153: undefined refere
Hi,
I tried to build qemu's user mode linux emulation on RHEL 4.8 x86_64 -
but I run into this issue -
ARi386-linux-user/libqemu.a
LINK i386-linux-user/qemu-i386
/usr/bin/ld:/home/ckk/lab/qemu-0.12.5/x86_64.ld:41: syntax error
collect2: ld returned 1 exit status
make[1]: *** [qemu-i386] Er
On 03/21/2010 02:37 PM, Blue Swirl wrote:
On 3/21/10, Anthony Liguori wrote:
On 03/20/2010 03:14 AM, Blue Swirl wrote:
On 3/20/10, Paul Bolle wrote:
0) Building current master
(3290c4aac5b97bb1e3b2b28d94669f2c611ce84a,
Introduce a default qmp session
On 3/21/10, Anthony Liguori wrote:
> On 03/20/2010 03:14 AM, Blue Swirl wrote:
>
> > On 3/20/10, Paul Bolle wrote:
> >
> >
> > > 0) Building current master
> (3290c4aac5b97bb1e3b2b28d94669f2c611ce84a,
> > > Introduce a default qmp session) fails here:
> > >
> > > $ make> /dev/null
> > > cc1:
On 03/20/2010 03:14 AM, Blue Swirl wrote:
On 3/20/10, Paul Bolle wrote:
0) Building current master (3290c4aac5b97bb1e3b2b28d94669f2c611ce84a,
Introduce a default qmp session) fails here:
$ make> /dev/null
cc1: warnings being treated as errors
curses.c: In function ‘curses_display_
On 03/20/2010 03:14 AM, Blue Swirl wrote:
On 3/20/10, Paul Bolle wrote:
0) Building current master (3290c4aac5b97bb1e3b2b28d94669f2c611ce84a,
Introduce a default qmp session) fails here:
$ make> /dev/null
cc1: warnings being treated as errors
curses.c: In function ‘curses_display_
On 3/20/10, Paul Bolle wrote:
> 0) Building current master (3290c4aac5b97bb1e3b2b28d94669f2c611ce84a,
> Introduce a default qmp session) fails here:
>
> $ make > /dev/null
> cc1: warnings being treated as errors
> curses.c: In function ‘curses_display_init’:
> curses.c:341: error: initializat
0) Building current master (3290c4aac5b97bb1e3b2b28d94669f2c611ce84a,
Introduce a default qmp session) fails here:
$ make > /dev/null
cc1: warnings being treated as errors
curses.c: In function ‘curses_display_init’:
curses.c:341: error: initialization from incompatible pointer type
make: *** [cur
On Tue, Jan 08, 2008 at 03:43:34PM +0100, Andreas Färber wrote:
> Hello,
>
> Am 08.01.2008 um 00:59 schrieb Rob Landley:
>
>> On Monday 07 January 2008 05:27:19 Edgar E. Iglesias wrote:
>>> I needed this or similar to build recent qemu's with gcc-4.
>>>
>> Is that all you needed, and did the result
Hello,
Am 08.01.2008 um 00:59 schrieb Rob Landley:
On Monday 07 January 2008 05:27:19 Edgar E. Iglesias wrote:
I needed this or similar to build recent qemu's with gcc-4.
Is that all you needed, and did the result work?
For system emulation on OSX/ppc I only needed a fix for always_inline
On Mon, Jan 07, 2008 at 05:59:24PM -0600, Rob Landley wrote:
> On Monday 07 January 2008 05:27:19 Edgar E. Iglesias wrote:
> > Hello,
> >
> > I needed this or similar to build recent qemu's with gcc-4.
> >
> > Best regards
>
> Is that all you needed, and did the result work?
>
> The 0.9.1 build I
On Monday 07 January 2008 05:27:19 Edgar E. Iglesias wrote:
> Hello,
>
> I needed this or similar to build recent qemu's with gcc-4.
>
> Best regards
Is that all you needed, and did the result work?
The 0.9.1 build I did yesterday grabbed gcc 3.4 during the ./configure stage,
which is only insta
Hello,
I needed this or similar to build recent qemu's with gcc-4.
Best regards
--
Edgar E. Iglesias
Axis Communications AB
diff --git a/linux-user/main.c b/linux-user/main.c
index e3a2374..164fdb9 100644
--- a/linux-user/main.c
+++ b/linux-user/main.c
@@ -53,7 +53,8 @@ asm(".globl __preinit_ar
33 matches
Mail list logo
