GNOME.org
 

Re: [gnome-love] Setting up a development environment

Ok, there indeed a problem while installing guest tools here is the
content of my vboxadd-install.log file:

Uninstalling modules from DKMS
Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxguest/4.1.18/source ->
                 /usr/src/vboxguest-4.1.18

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make KERNELRELEASE=3.11.6-201.fc19.x86_64
-C /lib/modules/3.11.6-201.fc19.x86_64/build
M=/var/lib/dkms/vboxguest/4.1.18/build...(bad exit status: 2)
Error! Bad return status for module build on kernel:
3.11.6-201.fc19.x86_64 (x86_64)
Consult /var/lib/dkms/vboxguest/4.1.18/build/make.log for more
information.
Failed to install using DKMS, attempting to install without
grep: /lib/modules/3.11.6-201.fc19.x86_64/build/include/linux/version.h:
Aucun fichier ou dossier de ce type
make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG=
-C /lib/modules/3.11.6-201.fc19.x86_64/build SUBDIRS=/tmp/vbox.0
SRCROOT=/tmp/vbox.0 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;                                                       \
echo >&2 "  ERROR: Kernel configuration is invalid.";           \
echo >&2 "         include/generated/autoconf.h or
include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to
fix it.";       \
echo >&2 ;                                                      \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
  gcc -Wp,-MD,/tmp/vbox.0/.VBoxGuest-linux.o.d  -nostdinc
-isystem /usr/lib/gcc/x86_64-redhat-linux/4.8.2/include
-I/usr/src/kernels/3.11.6-201.fc19.x86_64/arch/x86/include
-Iarch/x86/include/generated  -Iinclude
-I/usr/src/kernels/3.11.6-201.fc19.x86_64/arch/x86/include/uapi
-Iarch/x86/include/generated/uapi
-I/usr/src/kernels/3.11.6-201.fc19.x86_64/include/uapi
-Iinclude/generated/uapi
-include /usr/src/kernels/3.11.6-201.fc19.x86_64/include/linux/kconfig.h
-D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
-fno-strict-aliasing -fno-common -Werror-implicit-function-declaration
-Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-sse
-mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone
-mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args
-fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
-DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1
-DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare
-fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
-mno-avx -Wframe-larger-than=2048 -Wno-unused-but-set-variable
-fno-omit-frame-pointer -fno-optimize-sibling-calls -g -pg -mfentry
-DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign
-fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO
-include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h
-I/lib/modules/3.11.6-201.fc19.x86_64/build/include -I/tmp/vbox.0/
-I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxguest/
-I/tmp/vbox.0/vboxguest/include -I/tmp/vbox.0/vboxguest/r0drv/linux
-D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0
-DIN_GUEST -DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST
-DVBOX_WITH_HGCM -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS  -DMODULE
-D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(VBoxGuest_linux)"
-D"KBUILD_MODNAME=KBUILD_STR(vboxguest)" -c
-o /tmp/vbox.0/VBoxGuest-linux.o /tmp/vbox.0/VBoxGuest-linux.c
/tmp/vbox.0/VBoxGuest-linux.c:206:49: erreur: expected ‘=’, ‘,’, ‘;’,
‘asm’ or ‘__attribute__’ before ‘g_VBoxGuestPciId’
 static const struct pci_device_id __devinitdata g_VBoxGuestPciId[] =
                                                 ^
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:78:0,
                 from /tmp/vbox.0/VBoxGuest-linux.c:28:
include/linux/module.h:87:32: erreur: ‘__mod_pci_device_table’ aliased
to undefined symbol ‘g_VBoxGuestPciId’
 extern const struct gtype##_id __mod_##gtype##_table  \
                                ^
include/linux/module.h:140:3: note: in expansion of macro
‘MODULE_GENERIC_TABLE’
   MODULE_GENERIC_TABLE(type##_device,name)
   ^
/tmp/vbox.0/VBoxGuest-linux.c:216:1: note: in expansion of macro
‘MODULE_DEVICE_TABLE’
 MODULE_DEVICE_TABLE(pci, g_VBoxGuestPciId);
 ^
make[2]: *** [/tmp/vbox.0/VBoxGuest-linux.o] Erreur 1
make[1]: *** [_module_/tmp/vbox.0] Erreur 2
make: *** [vboxguest] Erreur 2
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.

Le jeudi 07 novembre 2013 à 18:18 +0100, Mathieu Stumpf a écrit :

So, I just installed a bright new Fedora into a VirtualBox (v4.1.18) but
despite the fact that I installed guest additions as explained on [1], I
can configure my guest with a resolution upper than 1024*768… Does
someone have any idea why?

[1]
http://www.sysprobs.com/install-fedora-15-virtualbox-steps-install-virtualbox-guest-additions-fedora-15



Le mercredi 06 novembre 2013 à 09:38 -0800, Sriram Ramkrishna a écrit :

On Wed, Nov 6, 2013 at 8:50 AM, Sindhu S <sindhus live in> wrote:

Hi Mathieu and all,

I found that using GNOME on arch was a better experience than other
distributions. I've done my share of distro hopping from RPM to DEB systems
and I think Arch with its quick packagers and simple installation is
recommended if you are comfortable with commandline. Arch repositories carry
GNOME 3.10.1.



+1  You get the latest development environment using "tarballs" for
free.  So you can easily develop against the latest release.
Definitely worth checking out. Arch is always the first distro out of
the gate with a pure GNOME experience after a release.  Usually within
2 weeks.  Within 1 week, you have it in testing repo.


sri


_______________________________________________
gnome-love mailing list
gnome-love gnome org
https://mail.gnome.org/mailman/listinfo/gnome-love
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]