public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Sullivan <michael@espersunited.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Weird problem while emerging virtualbox
Date: Tue, 29 Jan 2008 15:35:07 -0600	[thread overview]
Message-ID: <1201642507.13756.28.camel@camille.espersunited.com> (raw)

I tried to emerge virtualbox, and I got this:

>>> Emerging (1 of 1) app-emulation/virtualbox-1.5.2-r1 to /
 * VirtualBox-1.5.2_OSE.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...
[ ok ]
 * checking ebuild checksums ;-) ...
[ ok ]
 * checking auxfile checksums ;-) ...
[ ok ]
 * checking miscfile checksums ;-) ...
[ ok ]
 * checking VirtualBox-1.5.2_OSE.tar.bz2 ;-) ...
[ ok ]
>>> Unpacking source...
>>> Unpacking VirtualBox-1.5.2_OSE.tar.bz2
to /var/tmp/portage/app-emulation/virtualbox-1.5.2-r1/work
 * Applying virtualbox-1.5.2-remove-splitted-stuff.patch ...
[ ok ]
>>> Source unpacked.
>>> Compiling source
in /var/tmp/portage/app-emulation/virtualbox-1.5.2-r1/work/VirtualBox-1.5.2_OSE ...
Checking for environment: Determined build machine: linux.x86, target
machine: linux.x86, OK.
Checking for kBuild: found, OK.
Checking for gcc: found version 4.1.2, OK.
Checking for as86: found version 0.16.17, OK.
Checking for bcc: found version 0.16.17, OK.
Checking for iasl: found version 20060912, OK.
Checking for xslt: found, OK.
Checking for pthread: found, OK.
Checking for xalan: found version 1.10.0, OK.
Checking for xerces: found version 2.7.0, OK.
Checking for libIDL: found version 0.8.9, OK.
Checking for zlib: found version 1.2.3, OK.
Checking for SDL: found version 1.2.11, OK.
Checking for X libraries: found, OK.
Checking for Xcursor: found, OK.
Checking for Qt: 
  Qt not found at
"/usr/qt/3 /usr/lib/qt3 /usr/lib/qt-3.3 /usr/share/qt3 /usr/lib64/qt-3.3 /usr/X11R6" or Qt headers not found
  Check the
file /var/tmp/portage/app-emulation/virtualbox-1.5.2-r1/work/VirtualBox-1.5.2_OSE/configure.log for detailed error information.

I have a directory structure in /usr/qt/3, and it IS installed:

camille ~ # emerge -pv =qt-3*

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] x11-libs/qt-3.3.8-r4  USE="cups doc examples gif ipv6
mysql nas opengl -debug -firebird -immqt -immqt-bc -nis -odbc -postgres
-sqlite -xinerama" 0 kB 

Total: 1 package (1 reinstall), Size of downloads: 0 kB


Here's the directory structure in /usr/qt/3:

camille ~ # ls -l /usr/qt/3
total 48
drwxr-xr-x  2 root root 4096 Jun 16  2006 bin
drwxr-xr-x  4 root root 4096 Jun 17  2006 doc
drwxr-xr-x  3 root root 4096 Jun 16  2006 etc
drwxr-xr-x 80 root root 4096 Jan 24 14:38 examples
drwxr-xr-x  3 root root 8192 Jun 16  2006 include
drwxr-xr-x  3 root root 4096 Jan 24 14:38 lib
drwxr-xr-x  3 root root 4096 Jun 16  2006 mkspecs
drwxr-xr-x  5 root root 4096 Jun 23  2006 plugins
drwxr-xr-x  3 root root 4096 Jun 16  2006 tools
drwxr-xr-x  2 root root 4096 Nov  8 08:24 translations
drwxr-xr-x 18 root root 4096 Jan 24 14:38 tutorial

So why is it not registering?  Is there some shell variable I need to
set?



-- 
gentoo-user@lists.gentoo.org mailing list



                 reply	other threads:[~2008-01-29 21:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1201642507.13756.28.camel@camille.espersunited.com \
    --to=michael@espersunited.com \
    --cc=gentoo-user@lists.gentoo.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