[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to compile a 2.5.x Kernel



Ok found g++ .... stupid me ... 
Now I get:
scripts/kconfig/qconf.cc: In destructor `virtual ConfigItem::~ConfigItem()':
scripts/kconfig/qconf.cc:291: error: non-lvalue in unary `&'

And that doesn't tell me anything ...

google told me that:
http://groups.google.de/groups?q=/qconf.cc:+In+destructor+%60virtual+ConfigItem::~ConfigItem()%27:+scripts/kconfig/qconf.cc:291:+error:+non-lvalue+in+unary&hl=de&lr=&ie=UTF-8&selm=20030429095010%243d33%40gated-at.bofh.it&rnum=1

Someone changed the kernel sources to get it running. Alright ... I now 
believe Hugh was right. I am probably not up to the job. I was just assuming 
that shortly before 2.5. will turn into 2.6.x rc it would be installable by 
me, but was wrong.

Thanks for all the help and comments...

Mariano
--->>>
make[1]: Entering directory `/usr/src/kernel-source-2.5.69'
/usr/bin/make -f scripts/Makefile.build obj=scripts
/usr/bin/make -f scripts/Makefile.build obj=scripts/kconfig 
scripts/kconfig/qconf
  g++ -Wp,-MD,scripts/kconfig/.qconf.o.d -O2  -I/usr/share/qt/include  -c -o 
scripts/kconfig/qconf.o scripts/kconfig/qconf.cc
scripts/kconfig/qconf.cc: In destructor `virtual ConfigItem::~ConfigItem()':
scripts/kconfig/qconf.cc:291: error: non-lvalue in unary `&'
make[2]: *** [scripts/kconfig/qconf.o] Error 1
make[1]: *** [scripts/kconfig/qconf] Error 2
make[1]: Leaving directory `/usr/src/kernel-source-2.5.69'
make: *** [stamp-kernel-configure] Error 2
<<<---


On Saturday 14 June 2003 14:13, you wrote:
> Ok, I missed libqt-dev .... Now I am looking to solve
>
> --->>>
> make[1]: Entering directory `/usr/src/kernel-source-2.5.69'
> /usr/bin/make -f scripts/Makefile.build obj=scripts
> /usr/bin/make -f scripts/Makefile.build obj=scripts/kconfig
> scripts/kconfig/qconf
>   g++ -Wp,-MD,scripts/kconfig/.qconf.o.d -O2  -I/usr/share/qt/include  -c
> -o scripts/kconfig/qconf.o scripts/kconfig/qconf.cc
> /bin/sh: line 1: g++: command not found
> <<<---
>
> gcc-3.0 didn't do the trick ... cpp-3.0/3.2/3.3 is also installed ...
>
> Hmmh? Still looking ...
>
> Mariano
>
> On Saturday 14 June 2003 14:01, you wrote:
> > Nicos,
> >
> >   thanks for taking the time ...
> >
> > > I tried on testing, and it worked quite fine with the regular make-kpkg
> > > routine. You'll have to install the proper module handling utilities (I
> > > don't know what the name was, but it's listed in the kernel doc and
> > > available as a debian package).
> >
> > Hmmh. I tried that before ...
> > I did
> > apt-get install module-init-tools (Don't know if that is the right
> > package) and also installed the sources.
> > I unpacked the sources and ran
> >
> > 	make-kpkg -config=x --revision=xp2600.1 kernel_image
> >
> > Unfortunately I got the following errors ...
> > ---->>>
> > black:/usr/src/linux# make-kpkg -config=x --revision=xp2600.1
> > kernel_image /usr/bin/make    \
> >                                  ARCH=i386 xconfig
> > make[1]: Entering directory `/usr/src/kernel-source-2.5.69'
> > /usr/bin/make -f scripts/Makefile.build obj=scripts
> > /usr/bin/make -f scripts/Makefile.build obj=scripts/kconfig
> > scripts/kconfig/qconf
> > *
> > * Unable to find the QT installation. Please make sure that the
> > * QT development package is correctly installed and the QTDIR
> > * environment variable is set to the correct location.
> > *
> > make[2]: *** [scripts/kconfig/.tmp_qtcheck] Error 1
> > make[1]: *** [scripts/kconfig/qconf] Error 2
> > make[1]: Leaving directory `/usr/src/kernel-source-2.5.69'
> > make: *** [stamp-kernel-configure] Error 2
> >
> > <<<----
> >
> > My QTDIR variable is not set, but I don't know what to set it to. What
> > package do I have to install? "apt-cache search qt dev" returns at least
> > two pages of packages.
> >
> > Regarding the kernel docs ... You are talking about
> > /usr/share/doc/kernel-doc-2.5.69/Documentation/, right? What file to
> > read? There are so many files and I found none named "READ ME FIRST",
> > "Bull starts here" or at least index.html ;-) I also looked in the kbuild
> > subdirectory with not much of a success.
> >
> > Mariano



Reply to: