From: "Steven Liu" <stevenliu@psdc.com>
To: "Keith M Wesolowski" <wesolows@foobazco.org>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: mips-tfile
Date: Thu, 17 May 2001 18:09:17 -0700 [thread overview]
Message-ID: <001201c0df37$2befb920$dde0490a@pcs.psdc.com> (raw)
In-Reply-To: 20010305205516.A25870@foobazco.org
Hi, All:
I have a question about GCC:
How can we make gcc do not use the MIPS instructions lwl, lwr, swl, and swr?
Thanks,
Steven
----- Original Message -----
From: "Keith M Wesolowski" <wesolows@foobazco.org>
To: "Steven Liu" <stevenliu@psdc.com>
Cc: <linux-mips@oss.sgi.com>
Sent: Monday, March 05, 2001 9:55 PM
Subject: Re: mips-tfile
> On Mon, Mar 05, 2001 at 04:49:28AM -0800, Steven Liu wrote:
>
> > I am working on cross-compiler for mips R3000 on Linux now and meet a
problem in egcs.
> >
> > My host system is i386 with Rad Hat 7.0 installed.
> >
> > First, I successfully built and installed binutils-2.8.1 by using
> > binutils-2.8.1.tar.gz and egcs-mips-linux-1.1.2-2.i386.rpm. This created
> > bin, lib, mips-linux subdirectories.
>
> This makes no sense...how/why did you use an rpm of egcs to build
> binutils from source? That doesn't really make any sense. Could you
> please indicate what exact files you are using and where you got them
> from? If you are applying patches, please mention those as well.
>
> > Second, I installed the linux kernel source code for mips by using
> > linux-2.2.14-000715.tar.gz and configured it and enabled
> > CONFIG_CROSSCOMPILE. Made soft links: let mips-linux/include/asm
> > pointd to linux-2.2.14-000715/include/asm-mips and
> > mips-linux/include/linux pointd to linux-2.2.14-000715/include/linux.
>
> This is not needed to build either gcc or the kernel.
>
> > Third, unziped the egcs-1.1.2.tar.gz, added the patch
> > egcs-mips-linux-1.1.2-2.i386.rpm and configured it as following:
> > ./configure --prefix=3D/home/sliu --with-newlib --target=mips-linux
> > and made it this way:
> > make SUBDIRS=3D"libiberty texinfo gcc" ALL_TARGET_MODULES=3D =
> > CONFIGURE_TARGET_MODULES=3D INSTALL_TARGET_MODULES=3D LANGUAGES=3D"c"
>
> What are you doing with both an rpm and a source tarball? An RPM is
> surely not a patch. Also, it is traditional to build gcc outside the
> source directory; it's possible that that is a source of trouble. The
> random "3D" in your output there is either another source of trouble
> or an artifact of your mailer; in either case it should be fixed.
>
> If you are having trouble building a cross-toolchain, you might
> consider getting make-cross from
> ftp://oss.sgi.com/pub/linux/mips/mips-linux/simple/crossdev - it takes
> most of the hard parts out of it. There's also a source toolchain
> there that seems to work fairly well; it compiles glibc, for example,
> which no version of egcs 1.1.2 I have seen will. Of course, if you
> want to use different versions you can do that as well.
>
> --
> Keith M Wesolowski <wesolows@foobazco.org> http://foobazco.org/~wesolows
> ------(( Project Foobazco Coordinator and Network Administrator ))------
> "I should have crushed his marketing-addled skull with a fucking bat."
>
WARNING: multiple messages have this Message-ID (diff)
From: "Steven Liu" <stevenliu@psdc.com>
To: Keith M Wesolowski <wesolows@foobazco.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: mips-tfile
Date: Thu, 17 May 2001 18:09:17 -0700 [thread overview]
Message-ID: <001201c0df37$2befb920$dde0490a@pcs.psdc.com> (raw)
Message-ID: <20010518010917.U-1oCIGMKphLk5ciTjtnMz3gwn47V7gvVEQNAvwl0L8@z> (raw)
In-Reply-To: 20010305205516.A25870@foobazco.org
Hi, All:
I have a question about GCC:
How can we make gcc do not use the MIPS instructions lwl, lwr, swl, and swr?
Thanks,
Steven
----- Original Message -----
From: "Keith M Wesolowski" <wesolows@foobazco.org>
To: "Steven Liu" <stevenliu@psdc.com>
Cc: <linux-mips@oss.sgi.com>
Sent: Monday, March 05, 2001 9:55 PM
Subject: Re: mips-tfile
> On Mon, Mar 05, 2001 at 04:49:28AM -0800, Steven Liu wrote:
>
> > I am working on cross-compiler for mips R3000 on Linux now and meet a
problem in egcs.
> >
> > My host system is i386 with Rad Hat 7.0 installed.
> >
> > First, I successfully built and installed binutils-2.8.1 by using
> > binutils-2.8.1.tar.gz and egcs-mips-linux-1.1.2-2.i386.rpm. This created
> > bin, lib, mips-linux subdirectories.
>
> This makes no sense...how/why did you use an rpm of egcs to build
> binutils from source? That doesn't really make any sense. Could you
> please indicate what exact files you are using and where you got them
> from? If you are applying patches, please mention those as well.
>
> > Second, I installed the linux kernel source code for mips by using
> > linux-2.2.14-000715.tar.gz and configured it and enabled
> > CONFIG_CROSSCOMPILE. Made soft links: let mips-linux/include/asm
> > pointd to linux-2.2.14-000715/include/asm-mips and
> > mips-linux/include/linux pointd to linux-2.2.14-000715/include/linux.
>
> This is not needed to build either gcc or the kernel.
>
> > Third, unziped the egcs-1.1.2.tar.gz, added the patch
> > egcs-mips-linux-1.1.2-2.i386.rpm and configured it as following:
> > ./configure --prefix=3D/home/sliu --with-newlib --target=mips-linux
> > and made it this way:
> > make SUBDIRS=3D"libiberty texinfo gcc" ALL_TARGET_MODULES=3D =
> > CONFIGURE_TARGET_MODULES=3D INSTALL_TARGET_MODULES=3D LANGUAGES=3D"c"
>
> What are you doing with both an rpm and a source tarball? An RPM is
> surely not a patch. Also, it is traditional to build gcc outside the
> source directory; it's possible that that is a source of trouble. The
> random "3D" in your output there is either another source of trouble
> or an artifact of your mailer; in either case it should be fixed.
>
> If you are having trouble building a cross-toolchain, you might
> consider getting make-cross from
> ftp://oss.sgi.com/pub/linux/mips/mips-linux/simple/crossdev - it takes
> most of the hard parts out of it. There's also a source toolchain
> there that seems to work fairly well; it compiles glibc, for example,
> which no version of egcs 1.1.2 I have seen will. Of course, if you
> want to use different versions you can do that as well.
>
> --
> Keith M Wesolowski <wesolows@foobazco.org> http://foobazco.org/~wesolows
> ------(( Project Foobazco Coordinator and Network Administrator ))------
> "I should have crushed his marketing-addled skull with a fucking bat."
>
next prev parent reply other threads:[~2001-05-18 1:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 12:49 mips-tfile Steven Liu
2001-03-05 12:49 ` mips-tfile Steven Liu
2001-03-06 4:55 ` mips-tfile Keith M Wesolowski
2001-03-09 16:58 ` mips-tfile Ralf Baechle
2001-05-18 1:09 ` Steven Liu [this message]
2001-05-18 1:09 ` mips-tfile Steven Liu
2001-05-18 1:31 ` mips-tfile Ralf Baechle
2001-05-18 23:42 ` mips-tfile Steven Liu
2001-05-18 23:42 ` mips-tfile Steven Liu
2001-05-18 23:50 ` mips-tfile Justin Carlson
2001-05-19 3:23 ` mips-tfile Ralf Baechle
2001-03-09 17:15 ` Scrabled headers, was: mips-tfile Ralf Baechle
2001-03-09 17:15 ` Ralf Baechle
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='001201c0df37$2befb920$dde0490a@pcs.psdc.com' \
--to=stevenliu@psdc.com \
--cc=linux-mips@oss.sgi.com \
--cc=wesolows@foobazco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox