All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martín Chikilian" <slack@efn.uncor.edu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Weird problem when compiling kernel
Date: Fri, 03 Sep 2004 10:32:45 -0300	[thread overview]
Message-ID: <4138727D.8040602@efn.uncor.edu> (raw)
In-Reply-To: <20040902201945.GB15298@mars.ravnborg.org>

On Wed, Sep 01, 2004 at 09:50:04AM -0300, Mart?n Chikilian wrote:

>>Hello linux-kernel:
>>I'm running Linux Slackware 10.0, kernel 2.6.7. I compiled such kernel 
>>when using Slackware 9.1, and after i *upgraded* to 10.0 and tried to 
>>compile 2.6.8.1, i noticed that i couldn't do that. When i wanted to 
>>modify my 2.6.7 configuration and tried to compile it again, i noticed 
>>that i couldn't do it either.
>>I tried with all flavors off gcc, binutils, etc
>>So, there is my prob.
>>Error is:
>>*rm -rf .tmp_versions
>>mkdir -p .tmp_versions
>>make -f scripts/Makefile.build obj=scripts/basic
>>make -f scripts/Makefile.build obj=scripts
>>make -f scripts/Makefile.build obj=arch/i386/kernel 
>>arch/i386/kernel/asm-offsets.s
>>make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
>>make -f scripts/Makefile.build obj=init
>>make -f scripts/Makefile.build obj=usr
>>  ld -m elf_i386  -r -o usr/built-in.o
>>ld: no input files
>>scripts/Makefile.build:229: *** [usr/built-in.o] Error 1
>>Makefile:600: *** [usr] Error 2
>>--
>>When make V=1.
>>.config is in http://jumper.bounceme.net:81/slackatefn/.config
>>
>>gcc version: 3.4.1, make: 3.80, binutils: 2.15.90.0.3
>>I would appreciate any help/suggestion/hint.
>>    
>>
>
>
>Please try to do:
>rm usr/*o
>make V=1
>
>and post output.
>
>  
>
rm -rf .tmp_versions
mkdir -p .tmp_versions
make -f scripts/Makefile.build obj=scripts/basic
make -f scripts/Makefile.build obj=scripts
make -f scripts/Makefile.build obj=arch/i386/kernel 
arch/i386/kernel/asm-offsets.s
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
make -f scripts/Makefile.build obj=init
make -f scripts/Makefile.build obj=usr
  gcc -Wp,-MD,usr/.gen_init_cpio.d -Wall -Wstrict-prototypes -O2 
-fomit-frame-pointer        -o usr/gen_init_cpio usr/gen_init_cpio.c
  ./usr/gen_init_cpio > usr/initramfs_data.cpio
  gcc -Wp,-MD,usr/.initramfs_data.o.d -nostdinc -iwithprefix include 
-D__KERNEL__ -Iinclude  -D__ASSEMBLY__ 
-Iinclude/asm-i386/mach-default    -c -o usr/initramfs_data.o 
usr/initramfs_data.S
   ld -m elf_i386  -r -o usr/built-in.o
ld: no input files
scripts/Makefile.build:229: *** [usr/built-in.o] Error 1
Makefile:600: *** [usr] Error 2

>Also please check that you have gzip in your path.
>
>
>  
>
which gzip:
/usr/bin/gzip

>Your .config was far away from a valid 2.6.8.1 .config??
>
>  
>
It's not a 2.6.8.1 config, its a 2.6.7 one

I hope all this information would be useful for you.
Cya,
Martin

  reply	other threads:[~2004-09-03 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01 12:50 Weird problem when compiling kernel Martín Chikilian
2004-09-02 20:19 ` Sam Ravnborg
2004-09-03 13:32   ` Martín Chikilian [this message]
2004-09-03 19:28     ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4138727D.8040602@efn.uncor.edu \
    --to=slack@efn.uncor.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.