I was attempting to compile my own kernel as a debian package, following
these directions:
https://www.debian.org/releases/jessie/i386/ch08s06.html.en
When I got to the point where it has you run make-kpkg itself, where it
suggests the following command:
# fakeroot make-kpkg --initrd
On Tue, 10 Dec 2013 22:36:02 -0500 (EST), Michael Gulick wrote:
I think my only option if I want automatic upgrades is to keep the
abiname constant. I'm assuming (and I'm not sure whether this
assumption is correct) that all the third party modules (primarily
nvidia drivers and vmware)
On Mon, 09 Dec 2013 23:13:32 -0500 (EST), Stephen Powell wrote:
If you want to do this, you won't be able to use make-kpkg. You will
need to do something like make a modified version of the Debian source
package, linux, and build it with dpkg-buildpackage. But you want to
use upstream sources
Hi,
I'm looking for a way to override the default kernel package versions
generated by make-kpkg. With 3.0+ kernels, the kernel sublevel (as in
VERSION.PATCHLEVEL.SUBLEVEL), which is incremented when there are stable
updates for a kernel release, is used to generate the package name
On Mon, Dec 9, 2013 at 8:39 PM, Michael Gulick mgul...@gmail.com wrote:
I'm looking for a way to override the default kernel package versions
generated by make-kpkg. With 3.0+ kernels, the kernel sublevel (as in
VERSION.PATCHLEVEL.SUBLEVEL), which is incremented when there are stable
updates
On Mon, 09 Dec 2013 15:39:29 -0500 (EST), Michael Gulick wrote:
Hi,
I'm looking for a way to override the default kernel package versions
generated by make-kpkg. With 3.0+ kernels, the kernel sublevel (as in
VERSION.PATCHLEVEL.SUBLEVEL), which is incremented when there are stable
updates
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Psé...
2 horitas y 20 minutos...de nada...
Uno lo está haciendo gracias a los paquetes de Debian Sid...
No. Nononono. Lo hago con el paquete de kernel.org...pero con make-kpkg. :þþþ
Ahora va bien. :þ
- --
Saludos de Santiago José López
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 07/05/13 16:25, Santiago José López Borrazás escribió:
:-þþþ
'Yastoy' con él... :þþþ
- --
Saludos de Santiago José López Borrazás.
-BEGIN PGP SIGNATURE-
iQIVAwUBUYlYSLuF9/q6J55WAQoIsxAArPV2NbBtw0olX1zOTsUVNGuTrnIXiRAo
Makefile mentions an environment variable named HOSTCC.
I tried to set the variable, but it still failed because of linker issue.
Can make-kpkg do this job correctly? What extra parameter I should add?
build
the kernel itself correctly, but the problem is script tools such as
genksyms are build as amd64 format.
I notice that Linux Makefile mentions an environment variable named HOSTCC.
I tried to set the variable, but it still failed because of linker issue.
Can make-kpkg do this job correctly
correctly, but the problem is script tools such as
genksyms are build as amd64 format.
I notice that Linux Makefile mentions an environment variable named HOSTCC.
I tried to set the variable, but it still failed because of linker issue.
Can make-kpkg do this job correctly? What extra parameter I should add
On 3/28/12, Stephen Powell zlinux...@wowway.com wrote:
(I.e. is this a bug or a feature?)
Haha, indeed! It seems M$ is haunting us, haha...
Regards,
Panayiotis
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
I am trying to understand how make-kpkg chooses the versions for the
packages it creates. Each package has a name(a), which contains a
version part(a1), as well as a version(b), which is further split in
upstream version(b1) and Debian revision(b2), right? Assuming this, I'll
ask my question
On Tue, 27 Mar 2012 06:49:58 -0400 (EDT), Panayiotis Karabassis wrote:
I am trying to understand how make-kpkg chooses the versions for the
packages it creates. Each package has a name(a), which contains a
version part(a1), as well as a version(b), which is further split in
upstream version
), the version in the
name of the package and the debian package version are often different!
Regards,
Panayiotis
On 03/27/2012 02:05 PM, Stephen Powell wrote:
On Tue, 27 Mar 2012 06:49:58 -0400 (EDT), Panayiotis Karabassis wrote:
I am trying to understand how make-kpkg chooses the versions
always did too. There were different suffices, but the
basic version (x.y.z, for example, 2.6.32), was always consistent. This
is no longer the case. As further clarification, make-kpkg uses
the internal version in it's package name, and the value specified for
--append-to-version will be appended
Hello,
I try to compile a custom kernel in my home-directory with make-kpkg to
create a .deb-package.
Unfortunately, when installing this debian-package, apt-get complains
about a wrong symlink:
Hmm. There is a symbolic link /lib/modules/3.0.9.mptcp+/build
However, I can not read
Buenas.
Tan solo para comentaros que estoy corriendo, bajo debian 6, el kernel
2.6.38-rc8. Para crearlo primero usé la utilidad make-kpkg (que
había usado años atrás en multitud de ocasiones). No había forma que
cargase el sistema. No digo que se me olvidase algo (a final de
cuentas, dejé el
El día 10 de marzo de 2011 11:45, Manuel Trujillo (TooManySecrets)
toom...@toomany.net escribió:
Buenas.
Tan solo para comentaros que estoy corriendo, bajo debian 6, el kernel
2.6.38-rc8. Para crearlo primero usé la utilidad make-kpkg (que
había usado años atrás en multitud de ocasiones
Going to try a make-file patch when I get some time.
The patch was offered from a user on the Xen-user mailing list.
[1] http://lists.xensource.com/archives/html/xen-users/2010-09/msg00396.html
-M
Subject: make-kpkg (from kernel-package) does not build xen
Hello list,
I cannot get make-kpkg to build a Xenlinux type kernel into a Debian kernel
binary on my Debian Squeeze x86_64 system.
I am using GNU/Linux kernel sources tree (2.6.34.4) with Xen patches for this
custom kernel. I am trying to use the make-kpkg command to build a working
linux
Hi Rob,
WARNING: Couldn't open directory
/usr/src/linux-source-2.6.26/debian/linux-image-/lib/modules/2.6.32-live1.0:
No such file or directory
FATAL: Could not open
/usr/src/linux-source-2.6.26/debian/linux-image-/lib/modules/2.6.32-live1.0/modules.dep.temp
for writing: No such file or
Hi I have using make-kpkg successfully on my amd64 dual core system
until about a month ago.
I did the following:
installed debian testing amd64
apt-get install kernel-package make g++ gcc build-essentail
libncurses5-dev linux-source-2.6.32
and any other files I needed to build a kernel
I
Hi Here it fails again. this is version 12.033 instead of 12.032
I downloaded kernel--package-12.033.tar.gz
invoke like this
CONCURRENCY_LEVEL=3 make-kpkg --initrd --append-to-version dickhead1.0
kernel_image kernel_headers
All done in /usr/src/linux-source-2.6.32. I am running kernel
On Wed, Apr 07 2010, Cameron Hutchison wrote:
Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
I run a make-kpkg clean it spits out lots of lines about unlinking
files in debian/... On a slow link, this is very annoying (if I forget
to run screen)
I have RTFM but I
On 08.04.2010 01:59, Cameron Hutchison wrote:
Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
I run a make-kpkg clean it spits out lots of lines about unlinking
files in debian/... On a slow link, this is very annoying (if I forget
to run screen)
I have RTFM but I
Mart Frauenlob mart.frauen...@chello.at writes:
On 08.04.2010 01:59, Cameron Hutchison wrote:
Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
I run a make-kpkg clean it spits out lots of lines about unlinking
files in debian/... On a slow link, this is very annoying
On 08.04.2010 12:12, Cameron Hutchison wrote:
Mart Frauenlob mart.frauen...@chello.at writes:
On 08.04.2010 01:59, Cameron Hutchison wrote:
Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
I run a make-kpkg clean it spits out lots of lines about unlinking
files
On Thu, Apr 08 2010, Mart Frauenlob wrote:
Does v.12.033 always run a 'clean' first?
Yes.
Mine with lenny v.11.015 does not.
That is one major version ago. Things changed a lot witht he new
major version.
manoj
--
mophobia, n.: Fear of being verbally abused by a
Manoj Srivastava sriva...@ieee.org writes:
On Wed, Apr 07 2010, Cameron Hutchison wrote:
Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
I run a make-kpkg clean it spits out lots of lines about unlinking
files in debian/...
Please file a wishlist bug. I have
Mart Frauenlob mart.frauen...@chello.at writes:
You want to see the output of the build, but the clean process is too
much? The build output will be multiple times greater anyways. This is
not a problem over the slow link?
Ok. It looks like you haven't run the latest make-kpkg.
I just did
Is there any way to make make-kpkg (kernel-package 12.033) quieter? When
I run a make-kpkg clean it spits out lots of lines about unlinking
files in debian/... On a slow link, this is very annoying (if I forget
to run screen)
I have RTFM but I cannot see anything about making make-kpkg less
/contol and debian/Control
Both of these files are rewritten when I do a `fakeroot debian/rules
binary` to build the kernel.
,[ Manual page make-kpkg(1) line 145 ]
| --overlay-dir /path/to/directory
|The specified directory should contain files that will be placed
|in the ./debian
On Mon, Feb 15, 2010 at 2:11 AM, Tzafrir Cohen tzaf...@cohens.org.il wrote:
On Fri, Feb 12, 2010 at 02:36:37PM -0500, Cliff Flood wrote:
Hi,
I'm having some problems with building kernel image packages using
`make-kpkg`
I'm trying to build a package with a custom dependency and have tried
On Tue, Feb 16, 2010 at 03:17:20PM -0500, Cliff Flood wrote:
On Mon, Feb 15, 2010 at 2:11 AM, Tzafrir Cohen tzaf...@cohens.org.il wrote:
On Fri, Feb 12, 2010 at 02:36:37PM -0500, Cliff Flood wrote:
Hi,
I'm having some problems with building kernel image packages using
`make-kpkg
On Fri, Feb 12, 2010 at 02:36:37PM -0500, Cliff Flood wrote:
Hi,
I'm having some problems with building kernel image packages using `make-kpkg`
I'm trying to build a package with a custom dependency and have tried
editing the control files generated by make-kpkg but find
Hi,
I'm having some problems with building kernel image packages using `make-kpkg`
I'm trying to build a package with a custom dependency and have tried
editing the control files generated by make-kpkg but find that these
changes don't make it into the produced package.
So let me back up
Bonjour,
j'ai un laptop avec 4 coeurs. La compilation de noyau prends 2 heures.
j'ai l'impression qu'elle ne tourne que sur 1 processeur. Est il
possible avec make-kpkg de compiler le noyau en parallèle ?
merci d'avance
Guillaume
--
Lisez la FAQ de la liste avant de poser une question :
http
Le samedi 09 janvier 2010 14:31:35, giggz a écrit :
Bonjour,
j'ai un laptop avec 4 coeurs. La compilation de noyau prends 2 heures.
j'ai l'impression qu'elle ne tourne que sur 1 processeur. Est il
possible avec make-kpkg de compiler le noyau en parallèle ?
merci d'avance
Guillaume
Jean-Damien Durand a écrit :
Le samedi 09 janvier 2010 14:31:35, giggz a écrit :
Bonjour,
j'ai un laptop avec 4 coeurs. La compilation de noyau prends 2 heures.
j'ai l'impression qu'elle ne tourne que sur 1 processeur. Est il
possible avec make-kpkg de compiler le noyau en parallèle
Hola chicos
Desde anoche que estoy intentando compilar un kernel con la
herramienta kernel-package y ejecute la siguiente orden:
make-kpkg kernel_image kernel_headers --initrd
Luego instalo el paquete recien creado con dpkg -i bla bla bla, pero
no me crea la imagen initrd.
A alguien mas le pasa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 09/05/2009 21:23, Maximiliano Marin Bustos escribió:
A alguien mas le pasa lo mismo?
Puede ser un bug?
A mí, hace unos días tuve ese mismo problema, y la solución, es copiar los
ficheros de kernel-package, los que están en /usr/share/. Los de
2009/5/9 Santiago José López Borrazás sjlop...@yahoo.es:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 09/05/2009 21:23, Maximiliano Marin Bustos escribió:
A alguien mas le pasa lo mismo?
Puede ser un bug?
A mí, hace unos días tuve ese mismo problema, y la solución, es copiar los
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 09/05/2009 21:41, Maximiliano Marin Bustos escribió:
(...)
Asi estaba leyendo. Felipe Portales me dijo que esto ya habia sido
solucionado en la lista y le estaba echando una mirada al directorio.
Porque dices que hay que modificar el fichero
2009/5/9 Santiago José López Borrazás sjlop...@yahoo.es:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 09/05/2009 21:41, Maximiliano Marin Bustos escribió:
(...)
Asi estaba leyendo. Felipe Portales me dijo que esto ya habia sido
solucionado en la lista y le estaba echando una mirada al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 02/05/2009 00:58, Santiago José López Borrazás escribió:
Haciéndolo ya...
Hecho. Y solucionado. Ahora me faltan 2 cosas, como tengo grub, hay que
editar el fichero script de enlaces de símbolos de las imágenes, y hay que
comentar el 'lilo',
The command is make-kpkg buildpackage. So far, it has never
worked under etch. The build starts out but fails after about a
minute:
CHK include/linux/compile.h
/home/martin/linux-2.6.29/scripts/gen_initramfs_list.sh: Cannot open 'y'
make[3]: *** [usr/initramfs_data.cpio.gz] Error 1
make[2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hola:
Al compilar el kernel 2.6.29.2, detecto que ya da un problema bastante grande.
Cuando ejecuto:
make-kpkg --revision=1-686 --initrd binary-arch
Todo correctamente, que hace la compilación. Peeero, cuando llega la hora de
la verdad, ya
El vie, 01-05-2009 a las 23:38 +0200, Santiago José López Borrazás
escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hola:
Al compilar el kernel 2.6.29.2, detecto que ya da un problema bastante grande.
Cuando ejecuto:
make-kpkg --revision=1-686 --initrd binary-arch
Todo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 02/05/2009 00:03, mariodebian escribió:
A partir de las versiones nuevas los kernel de kernel-package no generan
initramfs si no lo indicas...
Ah, coñees lo que no contaban. Y mira que hay que leerselo todo del
fichero... :-P Es que, hace
On Fri, May 01, 2009 at 11:38:59PM +0200, Santiago José López Borrazás wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hola:
Al compilar el kernel 2.6.29.2, detecto que ya da un problema bastante grande.
Cuando ejecuto:
make-kpkg --revision=1-686 --initrd binary-arch
Todo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
El 02/05/09 00:10, Blu escribió:
Lee /usr/share/doc/kernel-package/NEWS.Debian.gz
Haciéndolo ya...
- --
Slds. de Santiago José López Borrazás.
-BEGIN PGP SIGNATURE-
iQIVAwUBSft+pYFZAuZYtJmMAQoPsRAAgGDWujI1LOv8KLnMqbhgKUDUOxX06ZOx
Manoj Srivastava wrote:
On Tue, Dec 09 2008, Stefan Goebel wrote:
Manoj, should I file a bug report for this or is there something else I
can try first?
Thankd for the bug-report and patch; it is always appropriate to
file a bug on kernel-package when you are experiencing
On Tue, Dec 09 2008, Stefan Goebel wrote:
Manoj, should I file a bug report for this or is there something else I
can try first?
Thankd for the bug-report and patch; it is always appropriate to
file a bug on kernel-package when you are experiencing difficulties. At
worst, you'll be
-patches/all/2.6.26/apply/debian
-a i386 -f xen works, running make-kpkg --revision='1.0'
--append-to-version='-foo' kernel_image does not work, apparently
make-kpkg tries to run make bzImage on the kernel sources and there is
Nothing to be done for 'bzImage'. A make deb-pkg on the sources
works
Le Mar 9 décembre 2008 13:53, Stefan Goebel a écrit :
Applying the Xen patches with ../kernel-patches/all/2.6.26/apply/debian
-a i386 -f xen works, running make-kpkg --revision='1.0'
--append-to-version='-foo' kernel_image does not work, apparently
make-kpkg tries to run make bzImage
François Cerbelle wrote:
Le Mar 9 décembre 2008 13:53, Stefan Goebel a écrit :
Applying the Xen patches with ../kernel-patches/all/2.6.26/apply/debian
-a i386 -f xen works, running make-kpkg --revision='1.0'
--append-to-version='-foo' kernel_image does not work [...]
You should try to use
Lenny.
Applying the Xen patches with ../kernel-patches/all/2.6.26/apply/debian
-a i386 -f xen works, running make-kpkg --revision='1.0'
--append-to-version='-foo' kernel_image does not work, apparently
make-kpkg tries to run make bzImage on the kernel sources and there is
Nothing to be done
),
on an i386 system running Lenny.
Applying the Xen patches with ../kernel-patches/all/2.6.26/apply/debian
-a i386 -f xen works, running make-kpkg --revision='1.0'
--append-to-version='-foo' kernel_image does not work, apparently
make-kpkg tries to run make bzImage on the kernel sources
On Tue, Dec 09, 2008 at 01:53:58PM +0100, Stefan Goebel wrote:
Hi,
I'm trying to build a custom Xen (DomU for now) kernel using the Debian
sources (i.e. linux-source-2.6.26 (2.6.26-11) with Debian's Xen patches
from linux-patch-debian-2.6.26 (2.6.26-11)) and kernel-package (11.015),
on an
# fakeroot make-kpkg --revision=custom.1.0 kernel_image
kernel source# dpkg -i /home/user/src/linux-image-2.6.27_custom.1.0_amd64.deb
kernel source# mkinitramfs -o /boot/initrd.img-2.6.27 2.6.27
That last should not be required if you had added --initrd to
the make-kpkg line.
Here
-kpkg.
The compile process gets all the way to the end and fails with
debian/stamp/Install: Is a directory
The exact command line I'm using at the top level linux-2.6.27 direcory is:
fakeroot make-kpkg --initrd --arch amd64 kernel_image
have tried to compile this in etch and lenny with no luck
2008/10/12 thveillon.debian [EMAIL PROTECTED]:
I've used Lenny default for the kernel I'm currently running
(11.001-something I think), and then tried 11.007 from Sid with good
results.
The .config is from my previously home-rolled 2.6.26-6, gcc is Lenny 4.3.2,
config is nothing fancy,
2008/10/12 thveillon.debian [EMAIL PROTECTED]:
Adrian Levi a écrit :
I have since tried compiling the kernel in a clean lenny debootstrap
chroot sucessfully.
Strangely is was called,
linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
Maybe you enabled xen support in the config : CONFIG_XEN
I'm having troubles compiling a vanilla 2.6.27 kernel using
kernel-package. Looks like there is a new iwl4965 driver and I'd like
to try it out.
The kernel compiles correctly using the usual toolchain provided with
the sources but fails on the packaging part using make-kpkg.
The compile process
Adrian Levi a écrit :
I have since tried compiling the kernel in a clean lenny debootstrap
chroot sucessfully.
Strangely is was called,
linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
Maybe you enabled xen support in the config : CONFIG_XEN
But it boots and works, must be a version
for testing (aka
fun !) purpose, the compilation went smoothly, including creation of
kernel-headers, but I didn't actually try the resulting kernel yet.
I'm on Lenny amd64.
Basically command is :
make-kpkg --initrd --append-to-version -vanilla64 --revision 2 kernel-image
kernel-headers
-kpkg.
The compile process gets all the way to the end and fails with
debian/stamp/Install: Is a directory
The exact command line I'm using at the top level linux-2.6.27 direcory is:
fakeroot make-kpkg --initrd --arch amd64 kernel_image
have tried to compile this in etch and lenny with no luck, can
on the packaging part using make-kpkg.
Have you tried kernel-package 11.007 from sid?
The compile process gets all the way to the end and fails with
debian/stamp/Install: Is a directory
The exact command line I'm using at the top level linux-2.6.27 direcory is:
fakeroot make-kpkg --initrd --arch amd64
Adrian Levi a écrit :
But you ended up with a .deb package at the end, Mine is failing
before creating the package.
My installed kernel-package version is 11.007 what was yours?
What did you use for a .config file? Mine is from linux-image-2.6.26
in lenny, answered the few new questions and
on the packaging part using make-kpkg.
The compile process gets all the way to the end and fails with
debian/stamp/Install: Is a directory
The exact command line I'm using at the top level linux-2.6.27 direcory is:
fakeroot make-kpkg --initrd --arch amd64 kernel_image
Have you tried without
On Sun, Oct 12 2008, Adrian Levi wrote:
I have since tried compiling the kernel in a clean lenny debootstrap
chroot sucessfully.
Strangely is was called,
linux-xenu-2.6.27_2.6.27-10.00.Custom_amd64.deb
But it boots and works, must be a version incompatibility somewhere, I
still have etch
provided with
the sources but fails on the packaging part using make-kpkg.
The compile process gets all the way to the end and fails with
debian/stamp/Install: Is a directory
The exact command line I'm using at the top level linux-2.6.27 direcory is:
fakeroot make-kpkg --initrd --arch amd64
setarch i386 make-kpkg --initrd --arch=i386 --revision $revision
binary
Thanks for that info, Steve. However I still cannot get it to work.
Try this:
DEB_HOST_ARCH=i386 make-kpkg --arch i386 --cross_compile - \
--rootcmd fakeroot --initrd --append-to-version mytest kernel_image
What you
use this:
setarch i386 make-kpkg --initrd --arch=i386 --revision $revision binary
Thanks for that info, Steve. However I still cannot get it to work.
When I run make-kpkg with the --arch parameter, it seems to always try
to use a cross-compiler - i486-linux-gnu-gcc (or something like
On Sat Jul 12, 2008 at 04:12:56 -, Cameron Hutchison wrote:
I just needed to add that --cross-compile - argument and it worked.
I spoke too soon. It does not quite work. It builds an amd64 arch
package, so I cannot install it on an i386 arch.
I use this:
setarch i386 make-kpkg
I am trying to build a kernel for my i386 box on my amd64 host. I want
to do this because the amd64 box build at least 10 times faster than the
target box.
I am using make-kpkg to build the kernel package. I am having the
following problem:
$ make-kpkg --rootcmd fakeroot --arch i386 kernel_image
Cameron Hutchison [EMAIL PROTECTED] writes:
I am trying to build a kernel for my i386 box on my amd64 host. I want
to do this because the amd64 box build at least 10 times faster than the
target box.
I am using make-kpkg to build the kernel package. I am having the
following problem:
$ make-kpkg
Cameron Hutchison [EMAIL PROTECTED] writes:
Cameron Hutchison [EMAIL PROTECTED] writes:
I am trying to build a kernel for my i386 box on my amd64 host. I want
to do this because the amd64 box build at least 10 times faster than the
target box.
I am using make-kpkg to build the kernel package. I
Bonjour,
Je veux fabriquer un paquet noyau i386 depuis amd64 debian
je lance:
make-kpkg --rootcmd fakeroot --arch i386 --append_to_version $version
--revision=$revision --initrd kernel_image kernel_headers kernel_doc
modules_image
depuis un poste 64 bits ca plante avec un:
/usr/bin/make
/home/georges/src/crusoe/linux-2.6.24.5/scripts/gcc-version.sh: line 22:
i486-linux-gnu-gcc: command not found
apparement un probleme avec gcc?
gcc --version donne
gcc (GCC) 4.2.4 (Debian 4.2.4-1)
est ce un bug, ou il me manque un paquet?
Si je lance make-kpkg sans arch i386 ca
[précision] installe gcc-3.4 avant bien sûr..
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/DebFrFrenchLists
Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et
Reply-To:
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Le samedi 24 mai 2008 à 10:00 +0200, François Boisson a écrit :
[précision] installe gcc-3.4 avant bien sûr..
Ben non, ca marche pas non plus, ca me fait un probleme avec asm
maintenant
arch/x86/kernel/asm-offsets.c:1: error: CPU you selected does not
support x86-64 instruction set
Le Sat, 24 May 2008 10:22:53 +0200
georges [EMAIL PROTECTED] a écrit:
Le samedi 24 mai 2008 à 10:00 +0200, François Boisson a écrit :
[précision] installe gcc-3.4 avant bien sûr..
Ben non, ca marche pas non plus, ca me fait un probleme avec asm
maintenant
On Thu, 2008-08-05 at 06:44 +0200, NN_il_Confusionario wrote:
On Wed, May 07, 2008 at 03:05:37PM -0700, Bill wrote:
The UTS Release version in include/linux/version.h
does not match current version:
2.6.25
Please correct this.
Any pointers here would be helpful.
It
On Thu, May 08, 2008 at 03:55:22AM -0700, Bill wrote:
Should there be a include/linux/version.h file in the
2.6.25 directory?
if you follow the documentation of kernel-package then make-kpkg will
create it.
If no commands were executed in the 2.6.25 directory tree after creating
Hi folks,
I'm trying to compile 2.6.25 using
fakeroot make-kpkg clean
fakeroot make-kpkg modules-clean
The second command terminates with an error as follows:
echo The UTS Release version in include/linux/version.h; echo
\\ ; echo does not match current version:; echo \2.6.25\ ;
echo
On Wed, May 07, 2008 at 03:05:37PM -0700, Bill wrote:
The UTS Release version in include/linux/version.h
does not match current version:
2.6.25
Please correct this.
Any pointers here would be helpful.
It might be a faq about kernel-package, and its documentation in
I made a custom kernel:
make kpkg --revision=.custom.10 --append-to-version=.cybo.1 --initrd
kernel_image
this issued in: linux-image-2.6.25.cybo.1_custom.1.0_amd64.deb
I installed this and wanted to make nvidia modules for it:
make-kpkg modules_image
This issued an error: (para phrased
Olá,
Ao correr o comando
make-kpkg --revision hostname.versão kernel-image
São aplicados automaticamente os patchs da debian ao kernel ?
Em Ter, 2008-02-12 às 19:54 +, debiminho debiminho escreveu:
Olá,
Ao correr o comando
make-kpkg --revision hostname.versão kernel-image
São aplicados automaticamente os patchs da debian ao kernel ?
Olá.
Se você pegou o kernel do site kernel.org não, simplemente o
Olá,
Ao correr o comando
make-kpkg --revision hostname.versão kernel-image
São aplicados automaticamente os patchs da debian ao kernel ?
Estou a perguntar isto por causa da falha detectada a pouco tempo,
pelos vistos o source já foi actualizado assim como um pacote com
as patchs
I have recently switched to debian, and I am trying to learn to compile kernels
the debian way. I need a patch and an external module, so I am trying the
following script:
M=make-kpkg \
--us --uc --initrd \
--append-to-version q4 \
--stem linux \
--added-modules madwifi
Am 2007-03-17 20:11:57, schrieb dranger003:
Indeed it was the debug causing the issue. After disabling all DEBUG lines
in the .config the kernel is now of the correct size.
:-)
Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian
Indeed it was the debug causing the issue. After disabling all DEBUG lines in
the .config the kernel is now of the correct size.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I have exactly the same problem. Also running Feisty.
I used the following to compile the kernel:
sudo make-kpkg --initrd --append-to-version=-1-Custom kernel_image
kernel_headers
My /lib/modules/$(uname -r) folder is huge as well. All the modules have bigger
than normal sizes - every
Am 2007-03-06 22:04:59, schrieb Matt Price:
snip
this? the vmlinuz produced by the package is of normal size, but the
initrd is huge -- 43 megs! -- and /lib/modules/kernel-version-number/ is
on the order of 530 megs!!!
Sorry, but with the infos you have provided I can not help you.
Please,
hi
obviously a half-gig-sized kernel package is not optimal, i'd very much
like to figure out what's going on here... also i should say that the
after the build process, the source directory becomes enormous -- 2.7
gigs with ubuntu's 2.6.20 as opposed to a more restrained 700megs back
in the
i,
i'm having a problem using make-kpkg to build kernel packages on my
laptop, which runs ubuntu feisty and currently has make-kpkg version
10.065ubuntu4. this happens with upstream, debian, and ubuntu sources,
as far as I can tell, but most of my experimentation has been with
ubuntu's linux
Jacques L'helgoualc'h a écrit :
Bayrouni a écrit, vendredi 2 mars 2007, à 10:37 :
[...] la région du MBR, d'ailleurs beaucoup plus petite qu'1M, et
elle doit faire, si je ne me trompe pas 512 Ko.
Perdu, c'est 512 ... octets :)
Une petite question de vocabulaire au passage :
Au
1 - 100 of 1376 matches
Mail list logo