On Fri, 2016-04-08 at 11:42 -0500, Bruce Dubbs wrote:
> John Frankish wrote:
> > > > Ref:
> > > > Beyond LinuxR From Scratch - Version 2016-04-05
> > > > Chapter 8. Virtualization
> > > > qemu-2.5.1
> > > > 
> > > > vte-0.44.0 is mentioned as an optional dependency, but this
> > > > will not
> > work as
> > > > qemu looks for vte-2.90 and vte-0.44.0 supplies vte-2.91.
> > > > 
> > > > In addition, if qemu is compiled against gtk3, it starts,
> > > > displays the
> > bios
> > > > message and hangs.
> > > > 
> > > I have in my log:
> > > 
> > > GTK support       yes
> > > VTE support       yes
> > > 
> > > It doesn't mention whether that is gtk2 or gtk3.  I have both
> > > installed.
> > > However I was using qemu yesterday and it worked fine.
> > > 
> > OK, but:
> > 
> > $ cd qemu-2.5.1
> > 
> > $ CC="gcc -mtune=generic -Os -pipe" CXX="g++ -mtune=generic -Os
> > -pipe
> > -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local
> > --localstatedir=/var --libexecdir=/usr/local/lib/qemu --audio-drv-
> > list="oss
> > alsa sdl" --target-list="i386-softmmu i386-linux-user x86_64-
> > softmmu
> > x86_64-linux-user" --smbd=/usr/local/sbin/smbd --enable-vte
> > 
> > ERROR: User requested feature vte
> >         configure was not able to find it.
> >        Install libvte-2.90 devel
> 
> I cannot reproduce this.  I ran the command above and do get:
> 
> cc1: warning: command line option ‘-fno-rtti’ is valid for C++/ObjC++
> but 
> not for C
> 
> but otherwise the configure worked for me.
> 
>    -- Bruce
> 
> 

That's interesting. What do you get with the following command:
ls -la /usr/lib/pkgconfig/vte*
The other reason it might be working for you is that you are building
against gtk2? Try the following switch --with-gtkabi=3.0

A slight correction to my previous email. I was building with qemu-
2.5.0 and not 2.5.1. I'll test this out again with the correct version
 at the next opportunity.

Regards,
Wayne.


-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to