Alex Papadopoulos([EMAIL PROTECTED]) is reported to have said:
> I've managed to reinstall gcc-3.3 (with aptitude), after having cleared my
> apt cache (apt-get clean) so as to be sure that a "correct" version would
> be downloaded...
> Same problem, segmentation fault when I do 'gcc -v'
>
I hav
I've managed to reinstall gcc-3.3 (with aptitude), after having cleared my
apt cache (apt-get clean) so as to be sure that a "correct" version would be
downloaded...
Same problem, segmentation fault when I do 'gcc -v'
_
Express your
And it seems all my gcc-3.x packages don't work... gcc-2.95 is fine, but too
old...
_
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
I removed some of my gcc's, keeping the gcc-x.x-base files though, they
seemed necessary. I tried again, same error. The funny thing, even 'make
clean' fails :
...
/bin/sh: line 1: 15413 Segmentation fault gcc -D__KERNEL__ -Iinclude
-Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-alia
I do have all the necessary packages. The thing is that I configured my
kernel a couple of months ago (when 2.6.5 was the latest stable kernel
version). It worked fine. Yesterday I found shfs module, and while trying to
compile it I got this error message.
It isn't a "normal" compilation error,
Yes I have, with the latest provided by debian : 2.6.9
The problem seems to be unrelated to the version of the kernel because even
module compilation fails, as I stated before.
Thanks for helping
Hi
Have you tried to compile another 2.6.x kernel with your 2.6.5/.config
? Moreover you will have a
C muttered:
> make[1]: *** [vmlinux] Error 1
> make[1]: Leaving directory `/usr/src/linux'
> make: *** [stamp-build] Error 2
I saw this too when compiling 2.4.16, running an up-to-date Woody
system. I'll wait for 2.4.17.
While I'm waiting, I have 2 questions for kernel-hackers:
1. I'm currently
On Wed, Dec 12, 2001 at 14:21:53 +0100, G. Soyez wrote:
> It seems that the bug comes from the binutils package and can be solved by
> downgrading binutils.
No it doesn't. The bug is in the kernel sources, and older versions of
binutils just happened not to fail on it whereas the newer one does.
; - Original Message -
> From: "Dragos" <[EMAIL PROTECTED]>
> To: "C" <[EMAIL PROTECTED]>;
> Sent: Wednesday, December 12, 2001 1:18 PM
> Subject: Re: Kernel compilation error...
>
> > On Wednesday 12 December 2001 01:38 pm, C wrote:
Hi CraigT
On Merkidi 12 Decimbe 2001 12:38, C wrote:
> Hi there
>
> I recently upgraded my machinevia apt.this included a glibc6/-dev
> upgrade amongst other things.
> now when compiling a kernel...even one known to previously
> compileit fails at this point every time
>
> driv
To: "C" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, December 12, 2001 12:07 PM
Subject: Re: Kernel compilation error...
> well I had trouble like those some times, and I assume that is something
> related with a misconfigured kernel configuration file. I reinstalled the
On Wednesday 12 December 2001 01:38 pm, C wrote:
> Hi there
>
> I recently upgraded my machinevia apt.this included a glibc6/-dev
> upgrade amongst other things.
> now when compiling a kernel...even one known to previously
> compileit fails at this point every time
>
> drivers/n
well I had trouble like those some times, and I assume that is something
related with a misconfigured kernel configuration file. I reinstalled the
source ( lazy ) and reconfigured the kernel to compile, and everything
went just fine.
On Wed, 12 Dec 2001, C wrote:
> Hi there
>
> I recently upgra
On Mon, Jul 16, 2001 at 12:57:04PM -0400, Case, Benjamin wrote:
> I just apt-got the kernel-source-2.4.6. I make menuconfiged it and then I
> make-kpkg cleaned it, and ran make-kpkg --revision custom.1 kernel_image.
> About 10 minutes in to the compilation it stops with this message:
>
> install:
"J.A.Serralheiro" <[EMAIL PROTECTED]> wrote:
>hi. I already posted a question, but got any replies.
You did. I've cc'ed you directly this time; you might want to check the
web archives at http://lists.debian.org/ if you aren't subscribed to
debian-user, as the convention here is usually to send re
Ulrich wrote:
>
> I tried to compile a kernel from the 2.2.17-source.
> Up to 'make dep' and 'make clean', everything went fine.
> Make bzImage stops with following error-message:
>as86 -0 -a -o bbootsect.o bbootsect.s
>Make(1): as86: Command not found
>Make(1): *** [bbootsect.o] Error
On Wed 08/18/99 01:01AM, Heikki Vatiainen wrote:
>
> My guess is that your gcc is too new. In my potato system I have
> these too compilers installed:
>
> % gcc --version
> 2.95.1
> % gcc272 --version
> 2.7.2.3
for me:
# gcc --version
egcs-2.91 (something like that)
I installed the gcc and gcc
Mark Wagnon <[EMAIL PROTECTED]> wrote:
> I'm trying to compile a 2.0.36 kernel on my potato system, but I
> keep getting this error:
>
> init/main.c: In function `get_options':
> init/main.c:272: warning: subscript has type `char'
> make: *** [init/main.o] Error 1
My guess is that your gcc
Andrew Ivanov wrote:
>
> I have binutils 2.9.1-0.2 installed, which is what I think , at least
> this is a requirement for kernel source, as it's said on www.debian.org
> And compilation ran with binutils installed, and I got that error.
> Andrew
>
The as86 program is in the 'bin86' pac
Thank you for fast response. bin86 was the package needed.
Andrew
Never include a comment that will help | Andrew Ivanov
someone else understand your code. | [EMAIL PROTECTED]
If they understand it, they don't | ICQ: 124
I have binutils 2.9.1-0.2 installed, which is what I think , at least
this is a requirement for kernel source, as it's said on www.debian.org
And compilation ran with binutils installed, and I got that error.
Andrew
Never includ
On Sat, Nov 21, 1998 at 02:30:12AM -0600, Andrew Ivanov wrote:
> I just finished compiling my own kernel( 2.0.34), and it comes out of size
> 788K, which is too big for Lilo to handle.
> Are there any ways around it?
>
> I tried make bzImage, like HOWTO suggested, but at the end of compilation
> I
Andrew Ivanov wrote:
>
> I just finished compiling my own kernel( 2.0.34), and it comes out of size
> 788K, which is too big for Lilo to handle.
> Are there any ways around it?
>
> I tried make bzImage, like HOWTO suggested, but at the end of compilation
> I get:
> as86 -0 -a -o bbootsect.o bboot
On Sat, May 10, 1997 at 11:40:55AM -0400, Rick Jones wrote:
> On Sat, 10 May 1997, Johann Spies wrote:
>
> > defxx.o(.text+0x15a): undefined reference to `pcibios_present'
> > defxx.o(.text+0x188): undefined reference to `pcibios_find_device'
> I'm not a developer, but it may be that you have PCI
On Sat, 10 May 1997, Johann Spies wrote:
> The problem is that I have no PCI and did not select PCI in the
> configuration process (make xconfig).
I thought that at first but didn't think that compiling the kernel without
PCI enabled it would figure it out for it's self. If so how could you
comp
On Sat, 10 May 1997, Rick Jones wrote:
> On Sat, 10 May 1997, Johann Spies wrote:
>
> > defxx.o(.text+0x15a): undefined reference to `pcibios_present'
> > defxx.o(.text+0x188): undefined reference to `pcibios_find_device'
> > defxx.o(.text+0x1c2): undefined reference to `pcibios_read_config_word
On Sat, 10 May 1997, Johann Spies wrote:
> defxx.o(.text+0x15a): undefined reference to `pcibios_present'
> defxx.o(.text+0x188): undefined reference to `pcibios_find_device'
> defxx.o(.text+0x1c2): undefined reference to `pcibios_read_config_word'
> defxx.o(.text+0x20e): undefined reference to `p
27 matches
Mail list logo
