All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Natalia Portillo" <claunia@claunia.com>
To: kyle@silverbeach.net, qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] build problems on SuSE 9.1 w/CVS from 2004/05/31
Date: Thu, 15 Jul 2004 14:30:49 +0100	[thread overview]
Message-ID: <E1Bl6LT-0003I5-J5@lists.gnu.org> (raw)
In-Reply-To: <200405311216.20159.kyle@silverbeach.net>

Mmm,

I just got the SAME error with the CVS, but it says no SDL found (it is).
Also don't work downloading SDL source and doing make/make install.

Isn't there any solution?
I did not found it searching the mailing list. 

> -----Mensaje original-----
> De: qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org 
> [mailto:qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org] 
> En nombre de Kyle Hayes
> Enviado el: lunes, 31 de mayo de 2004 20:16
> Para: qemu-devel@nongnu.org
> Asunto: [Qemu-devel] build problems on SuSE 9.1 w/CVS from 2004/05/31
> 
> 
> I'm building with CVS from today.  My system is a P4 w/SuSE 
> 9.1 installed,
> 2.6.4 kernel.
> 
> I see two problems:
> 
> 1) when I run configure, I apparently cannot build anything 
> that needs static SDL:
> 
> linux:~/qemu/qemu # ./configure --prefix=/usr/local --enable-slirp
> Install prefix    /usr/local
> BIOS directory    /usr/local/share/qemu
> binary directory  /usr/local/bin
> Manual directory  /usr/local/share/man
> ELF interp prefix /usr/gnemul/qemu-%M
> Source path       /root/qemu/qemu
> C compiler        gcc
> make              make
> host CPU          i386
> host big endian   no
> target list       i386-user i386 i386-softmmu arm-user 
> sparc-user ppc-user 
> ppc-softmmu
> gprof enabled     no
> static build      no
> SDL support       yes
> SDL static link   no
> mingw32 support   no
> WARNING: cannot compile statically with SDL - qemu-fast won't 
> have a graphical output
> 
> I've installed all the SDL packages that SuSE 9.1 has.  Both 
> sdl-config and aalib-config report that there are static libs:
> 
> linux:~/qemu/qemu # aalib-config --static-libs -L/usr/lib 
> -Wl,-rpath,/usr/lib -laa -lm -L/usr/X11R6/lib -lX11 -lgpm -lslang
> 
> linux:~/qemu/qemu # sdl-config --static-libs -L/usr/lib 
> -Wl,-rpath,/usr/lib -lSDL -lpthread -lm -ldl -lasound 
> -L/usr/X11R6/lib -lX11 -lXext -laa
> 
> Under Gentoo, I had a problem with libasound.a missing.  
> However, under SuSE 9.1, it is there:
> 
> linux:~/qemu/qemu # locate libasound
> /usr/lib/libasound.a
> /usr/lib/libasound.la
> /usr/lib/libasound.so
> /usr/lib/libasound.so.2
> /usr/lib/libasound.so.2.0.0
> 
> I thought I would try to build anyway.  I don't usually use 
> qemu-fast, so this wasn't really a problem.  However, I find this:
> 
> linux:~/qemu/qemu # make
> gcc -Wall -O2 -g -D_GNU_SOURCE -o dyngen dyngen.c gcc -Wall 
> -O2 -g -g -D_GNU_SOURCE -o qemu-mkcow qemu-mkcow.c gcc -Wall 
> -O2 -g -g -D_GNU_SOURCE -o vmdk2raw vmdk2raw.c for d in 
> i386-user i386 i386-softmmu arm-user sparc-user ppc-user 
> ppc-softmmu; do \ make -C $d all || exit 1 ; \
>         done
> make[1]: Entering directory `/root/qemu/qemu/i386-user'
> gcc -Wall -O2 -g -fomit-frame-pointer -I. 
> -I/root/qemu/qemu/target-i386 -I/root/qemu/qemu 
> -I/root/qemu/qemu/linux-user
> -I/root/qemu/qemu/linux-user/i386 -D_GNU_SOURCE 
> -I/root/qemu/qemu/slirp -c -o elfload.o 
> /root/qemu/qemu/linux-user/elfload.c
> gcc -Wall -O2 -g -fomit-frame-pointer -I. 
> -I/root/qemu/qemu/target-i386 -I/root/qemu/qemu 
> -I/root/qemu/qemu/linux-user
> -I/root/qemu/qemu/linux-user/i386 -D_GNU_SOURCE 
> -I/root/qemu/qemu/slirp -c -o main.o 
> /root/qemu/qemu/linux-user/main.c gcc -Wall -O2 -g 
> -fomit-frame-pointer -I. -I/root/qemu/qemu/target-i386 
> -I/root/qemu/qemu -I/root/qemu/qemu/linux-user
> -I/root/qemu/qemu/linux-user/i386 -D_GNU_SOURCE 
> -I/root/qemu/qemu/slirp -c -o syscall.o 
> /root/qemu/qemu/linux-user/syscall.c
> /root/qemu/qemu/linux-user/syscall.c: In function `do_setsockopt':
> /root/qemu/qemu/linux-user/syscall.c:579: error: 
> `SO_BSDCOMPAT' undeclared (first use in this function)
> /root/qemu/qemu/linux-user/syscall.c:579: error: (Each 
> undeclared identifier is reported only once
> /root/qemu/qemu/linux-user/syscall.c:579: error: for each 
> function it appears in.)
> /root/qemu/qemu/linux-user/syscall.c: In function `do_syscall':
> /root/qemu/qemu/linux-user/syscall.c:1633: warning: 
> dereferencing type-punned pointer will break strict-aliasing rules
> make[1]: *** [syscall.o] Error 1
> make[1]: Leaving directory `/root/qemu/qemu/i386-user'
> make: *** [all] Error 1
> 
> I've done a grep -r in /usr/include and nothing in there has 
> "SO_BSDCOMPAT" 
> set.  I've searched the mailing list archive for this and do 
> not see anything about it.  
> 
> If I comment that one line (line 579 in syscall.c) out, then 
> the build succeeds.  I have not had a chance to use it yet.  
> I rather suspect that this will break something somewhere.  I 
> don't use the user-mode of QEMU either, but still....
> 
> Best,
> Kyle
>  
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

      parent reply	other threads:[~2004-07-15 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-31 19:16 [Qemu-devel] build problems on SuSE 9.1 w/CVS from 2004/05/31 Kyle Hayes
2004-05-31 19:44 ` Karel Gardas
2004-07-15 13:30 ` Natalia Portillo [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=E1Bl6LT-0003I5-J5@lists.gnu.org \
    --to=claunia@claunia.com \
    --cc=kyle@silverbeach.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.