Last kernel compilation 2.6.31.1

At Mon, 28 Sep 2009 16:01:11 GMT Tauno Voipio <tauno.voipio.DeleteThis@INVALIDiki.fi> wrote:

>
> macruzq wrote:
> > Hi everybody:
> >
> > When compiling last stable kernel, I go the following at the end of
> > make
> >
> > . . . . . . . . . .
> >
> > CC init/version.o
> > LD init/built-in.o
> > LD .tmp_vmlinux1
> > drivers/built-in.o(.init.text+0x4905): In function `con_init':
> > : undefined reference to `.L1714'
> > make: *** [.tmp_vmlinux1] Error 1
> >
> > . . . . . . . . . .
> >
> > How can I solve it?
> >
> > Previously, I took my former .config file from the current kernel I am
> > using (2.6.23.12) and ran 'make oldconfig', then I made 'make'.
> >
> > Any help will be appreciated.
>
> The .Lnnnn labels are GCC code generation internal
> labels, which should always be defined in the same
> compilation unit. It seems that the compilation of
> the drivers/built-in.o object file has gone awry.
>
> Try to delete the object file and re-make.

Wondering aloud: did the OP run out of disk space somewhere? Maybe /tmp
or /usr/tmp is full?

>

--
Robert Heller -- 978-544-6933
Deepwoods Software -- Download the Model Railroad System
http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows
heller.DeleteThis@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/

On Sep 28, 11:01 am, Tauno Voipio <tauno.voi... DeleteThis @INVALIDiki.fi> wrote:
> macruzqwrote:
> > Hi everybody:
>
> > When compiling last stable kernel, I go the following at the end of
> > make
>
> > . . . . . . . . . .
>
> > CC init/version.o
> > LD init/built-in.o
> > LD .tmp_vmlinux1
> > drivers/built-in.o(.init.text+0x4905): In function `con_init':
> > : undefined reference to `.L1714'
> > make: *** [.tmp_vmlinux1] Error 1
>
> > . . . . . . . . . .
>
> > How can I solve it?
>
> > Previously, I took my former .config file from the current kernel I am
> > using (2.6.23.12) and ran 'make oldconfig', then I made 'make'.
>
> > Any help will be appreciated.
>
Hi,
> The .Lnnnn labels are GCC code generation internal
> labels, which should always be defined in the same
> compilation unit. It seems that the compilation of
> the drivers/built-in.o object file has gone awry.
>
> Try to delete the object file and re-make.
I deleted drivers/built-in.o but the issue persists.
Also, I have plenty of room in my HD so there is no problem with
space.

I will keep on trying,

Thanks

Marco

>
> --
>
> Tauno Voipio
> tauno voipio (at) iki fi

"Marco A. Cruz Quevedo" <macruzq DeleteThis @myway.com> wrote:
> On Sep 28, 11:01 am, Tauno Voipio <tauno.voi... DeleteThis @INVALIDiki.fi> wrote:
> > > When compiling last stable kernel, I go the following at the end of
> > > make
> >
> > > . . . . . . . . . .
> >
> > > CC init/version.o
> > > LD init/built-in.o
> > > LD .tmp_vmlinux1
> > > drivers/built-in.o(.init.text+0x4905): In function `con_init':
> > > : undefined reference to `.L1714'
> > > make: *** [.tmp_vmlinux1] Error 1
> >
> > > . . . . . . . . . .
> >
> > > How can I solve it?
> >
> > > Previously, I took my former .config file from the current kernel I am
> > > using (2.6.23.12) and ran 'make oldconfig', then I made 'make'.
> >
> > > Any help will be appreciated.
> >
> Hi,
> > The .Lnnnn labels are GCC code generation internal
> > labels, which should always be defined in the same
> > compilation unit. It seems that the compilation of
> > the drivers/built-in.o object file has gone awry.
> >
> > Try to delete the object file and re-make.
> I deleted drivers/built-in.o but the issue persists.
> Also, I have plenty of room in my HD so there is no problem with
> space.
>
> I will keep on trying,
>
> Thanks
>
> Marco
>

Have you the required build tools?
Ideally, upgrade both gcc and binutils to recent versions.
See Documentation/Changes
To upgrade a config file.
Copy the old config file to .config.
Perform a:
$ make oldconfig
or:
$ make silentoldconfig
Then:
$ make clean

I don't know if that matters, but you may have to reset CFLAGS and LDFLAGS if you had set unusual values.
$ CFLAGS= LDFLAGS= make
I don't think kbuild read them anyway.

It looks like an issue with ld(1). Line numbers are supposed to be both imported and exported by the same module.
--
André Gillibert