public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Scott Kasten" <jscottkasten@yahoo.com>
To: gentoo-mips@lists.gentoo.org
Cc: Michael Bevilacqua <michael@bevilacqua.us>
Subject: Re: [gentoo-mips] O2 IP32 | mips-sources fails to find ldscripts
Date: Mon, 19 Feb 2007 17:54:17 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0702191723150.24546@bluefang.tetracon-eng.net> (raw)
In-Reply-To: <20976ae0702190831wde18e41o6e646c716a005936@mail.gmail.com>


Hi,

The ldscripts directory that you mention is a part of the bintuils ebuild. 
Not sure why your other tools are having problems.  Here's the present 
levels of all my relevant stuff:

binutils-2.16.1-r3
binutils-config-1.9-r3
gcc-3.4.6-r1
gcc-4.1.1
gcc-config-1.3.13-r4
kgcc64-3.4.6
kgcc64-4.1.1

As I look at it, it appears that only gcc-4.1.1 and kgcc64-4.1.1 are new. 
The others all came from the mips4 stage3 tarball when I installed the 
system a few weeks ago.

When I call mips64-unknown-linux-gnu-gcc with the -v flag, it is clearly 
the 3.4.6 compiler.  So the 4.1.1 versions would appear somewhat 
irrelevant at the moment.  I built the kernel I'm running on now, and by 
appearances, it must have been the kgcc/gcc 3.4.6 that was used.  It seems 
the only way I can call the 4.1.1 compiler is by using an explicit path 
down into it's tree.

-S-


On Mon, 19 Feb 2007, Michael Bevilacqua wrote:

> During kernel compile ld(1) is unable to find
> /usr/lib/binutils/mips-unknown-linux-gnu/2.16.1/ldscripts
>
> I was able to compile my current kernel without problems prior to changing
> to gcc 4.1.1 and rebuilding world with the -e flag, so I have a bad feeling
> something was altered to make this error occur.
>
> To get through the compile I created a link within /usr/src/linux like so:
>
> ln -s /usr/lib/binutils/mips-unknown-linux-gnu/2.16.1/ldscripts .
>
> However, even with the working .config that is running on my machine or the
> default ip32 config, I can't get this newly compiled kernel to work. It just
> hangs or does even load.
>
>
> Here is the original error:
>
> nano linux # make vmlinux.32 modules modules_install
> CROSS_COMPILE=mips64-unknown-linux-gnu-
>  CHK     include/linux/version.h
>  SPLIT   include/linux/autoconf.h -> include/config/*
>  CC      arch/mips/kernel/asm-offsets.s
>  GEN     include/asm-mips/asm-offsets.h
>  CC      scripts/mod/empty.o
>  HOSTCC  scripts/mod/mk_elfconfig
>  MKELF   scripts/mod/elfconfig.h
>  HOSTCC  scripts/mod/file2alias.o
>  HOSTCC  scripts/mod/modpost.o
>  HOSTCC  scripts/mod/sumversion.o
>  HOSTLD  scripts/mod/modpost
>  HOSTCC  scripts/pnmtologo
>  HOSTCC  scripts/conmakehash
>  HOSTCC  scripts/bin2c
>  CC      init/main.o
>  CHK     include/linux/compile.h
>  UPD     include/linux/compile.h
>  CC      init/version.o
>  CC      init/do_mounts.o
>  LD      init/mounts.o
> mips64-unknown-linux-gnu-ld: cannot open linker script file
> ldscripts/elf64btsmip.xr: No such file or directory
> make[1]: *** [init/mounts.o] Error 1
> make: *** [init] Error 2
>
>
> Here is some system information that I hope will assist someone in pointing
> me at any mistakes I might have made:
>
> [ebuild   R   ] sys-devel/binutils-2.16.1-r3  USE="-multislot -multitarget
> -nls -test -vanilla" 12,368 kB
>
> [ebuild   R   ] sys-devel/gcc-4.1.1  USE="(-altivec) -bootstrap -build -doc
> -fortran -gcj -gtk (-hardened) -ip28 -ip32r10k -mudflap (-multilib)
> -multislot (-n32) (-n64) -nls -nocxx -objc -objc++ -objc-gc -test -vanilla"
> 38,303 kB
>
> nano linux # gcc-config -l
> [1] mips-unknown-linux-gnu-4.1.1 *
> [2] mips64-unknown-linux-gnu-4.1.1 *
>
>
>
> -- 
> Michael D. Bevilacqua
> michael@bevilacqua.us
>
>
-- 
gentoo-mips@gentoo.org mailing list



  reply	other threads:[~2007-02-19 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 16:31 [gentoo-mips] O2 IP32 | mips-sources fails to find ldscripts Michael Bevilacqua
2007-02-19 22:54 ` J. Scott Kasten [this message]
2007-02-26  4:17 ` Kumba

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=Pine.LNX.4.64.0702191723150.24546@bluefang.tetracon-eng.net \
    --to=jscottkasten@yahoo.com \
    --cc=gentoo-mips@lists.gentoo.org \
    --cc=michael@bevilacqua.us \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox