hi there,
I collected the problems I have on this wiki page to make this message short:
http://www.lug-owl.de/cgi-bin/wiki/ErrorCompilingKernel20031125
Thanks for any hints
Regards
Ralf
On Wed, 2003-11-26 at 11:34, rgx wrote:
> hi there,
>
> I collected the problems I have on this wiki page to make this message short:
> http://www.lug-owl.de/cgi-bin/wiki/ErrorCompilingKernel20031125
>
> Thanks for any hints
> Regards
> Ralf
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Ralf,
Did you 'make oldconfig'?
Bob...
> Did you 'make oldconfig'?
Yes, sure :) The NLS_DEFAULT... is not defined for some reason...
I could replace it with the needed content in the source code if I knew its
format...
>
> Bob...
On Wed, 2003-11-26 at 11:49, rgx wrote:
> > Did you 'make oldconfig'?
>
> Yes, sure :) The NLS_DEFAULT... is not defined for some reason...
> I could replace it with the needed content in the source code if I knew its
> format...
Sorry, had to ask.
My 2.4.20 .config defines:
CONFIG_NLS_DEFAULT="iso8859-1"
Bob Chiodini schrieb am Mittwoch, 26. November 2003 19:13:
> On Wed, 2003-11-26 at 11:49, rgx wrote:
> > > Did you 'make oldconfig'?
> >
> > Yes, sure :) The NLS_DEFAULT... is not defined for some reason...
> > I could replace it with the needed content in the source code if I
> > knew its format...
>
> Sorry, had to ask.
>
> My 2.4.20 .config defines:
>
> CONFIG_NLS_DEFAULT="iso8859-1"
yes, this is in my .config file, too, but for gcc it has to be converted
to a
#define CONFIG_NLS_DEFAULT <something> line - and I think that it
shouldn't be just a string there...
On Wed, 2003-11-26 at 13:35, rgx wrote:
> Bob Chiodini schrieb am Mittwoch, 26. November 2003 19:13:
> > On Wed, 2003-11-26 at 11:49, rgx wrote:
> > > > Did you 'make oldconfig'?
> > >
> > > Yes, sure :) The NLS_DEFAULT... is not defined for some reason...
> > > I could replace it with the needed content in the source code if I
> > > knew its format...
> >
> > Sorry, had to ask.
> >
> > My 2.4.20 .config defines:
> >
> > CONFIG_NLS_DEFAULT="iso8859-1"
>
> yes, this is in my .config file, too, but for gcc it has to be converted
> to a
> #define CONFIG_NLS_DEFAULT <something> line - and I think that it
> shouldn't be just a string there...
See include/linux/autoconf.h: around line 2167, my 2.4.20 source:
#define CONFIG_NLS_DEFAULT "iso8859-1"
Which corresponds to its usage in /data/src/linux-2.4.22/fs/fat/inode.c,
char *.
Is this a ix86 kernel?
Bob..
Bob Chiodini schrieb am Mittwoch, 26. November 2003 20:03:
...
> See include/linux/autoconf.h: around line 2167, my 2.4.20 source:
>
> #define CONFIG_NLS_DEFAULT "iso8859-1"
>
> Which corresponds to its usage in
> /data/src/linux-2.4.22/fs/fat/inode.c, char *.
here we go! seems as we are approaching the core of all trouble: my
include/linux/autoconf.h lacks the corresponding entry. How big is your
autoconf.h? Mine is about 19k. For now, I'll add that line and go
on ...
>
> Is this a ix86 kernel?
it is (amd 1800+)
thanx!
ralf
>
> Bob..
Hi @ll :)
bug fixed, found next:
...
make -C lockd
make[2]: Entering directory `/data/src/linux-2.4.22/fs/lockd'
make all_targets
make[3]: Entering directory `/data/src/linux-2.4.22/fs/lockd'
gcc -D__KERNEL__ -I/data/src/linux-2.4.22/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-nostdinc -iwithprefix include -DKBUILD_BASENAME=svc4proc -c -o
svc4proc.o svc4proc.c
svc4proc.c:564: error: `nlm4svc_decode_void' undeclared here (not in a
function)
svc4proc.c:564: error: initializer element is not constant
svc4proc.c:564: error: (near initialization for `nlmsvc_procedures4
[0].pc_decode')
...
Further details added to
http://www.lug-owl.de/cgi-bin/wiki/ErrorCompilingKernel20031125
Thanks 4Ur <F1> :)
Ralf
On Wed, Nov 26, 2003 at 05:34:23PM +0100, rgx wrote:
> hi there,
Hi Ralf,
> I collected the problems I have on this wiki page to make this message short:
> http://www.lug-owl.de/cgi-bin/wiki/ErrorCompilingKernel20031125
<-- snip -->
...
#
# Automatically generated by kcmlinuz: don't edit
#
...
<-- snip -->
WTF is kcmlinuz???
I bet your problems will be gone if you run "make oldconfig" before
"make bzImage"...
> Thanks for any hints
> Regards
> Ralf
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Adrian Bunk schrieb am Sonntag, 30. November 2003 04:40:
> On Wed, Nov 26, 2003 at 05:34:23PM +0100, rgx wrote:
> > hi there,
>
> Hi Ralf,
Hello Adrian :)
> ...
> #
> # Automatically generated by kcmlinuz: don't edit
> #
> ...
>
> <-- snip -->
>
>
> WTF is kcmlinuz???
It's a GUI for selecting what to include for compiling a kernel that
integrates in the KDE control center. Like make configmenu (IIRC)
>
>
> I bet your problems will be gone if you run "make oldconfig" before
> "make bzImage"...
I did "make oldconfig", and then I selected my personal hardware.
Nope, it was the gcc that caused the trouble. I found gcc-2.95 on my
machine, too, and changed the link of /usr/bin/gcc to this version.
Then the kernel compiled! It was just to large - now I put most drivers
to modules - mh, and get some other errors, but let this be another
thread :)
Just have to find out how to pipe stdout and stderr simultanously into
ONE log file. something like "make bzImage 1&2>logfile"
Thanx for replying
Regards
Ralf
>
> > Thanks for any hints
> > Regards
> > Ralf
>
> cu
> Adrian