Linux MIPS Architecture development
 help / color / mirror / Atom feed
* RE: Recommended toolchain
@ 2001-03-21 14:00 Phil Thompson
  2001-03-21 12:11 ` Erik Mullinix
  2001-03-21 16:06 ` Keith M Wesolowski
  0 siblings, 2 replies; 23+ messages in thread
From: Phil Thompson @ 2001-03-21 14:00 UTC (permalink / raw)
  To: 'linux-mips@oss.sgi.com'

So, going back to the original question, what are the recommended versions -
particularly if you are building 2.4.x kernels?

Are the recomendations in the HOWTO out of date? I had to patch va-mips.h
from the egcs RPM and more fixes seem to be needed before I get a kernel
that compiles.

Thanks,
Phil

-----Original Message-----
From: Ralf Baechle [mailto:ralf@oss.sgi.com]
Sent: 20 March 2001 20:37
To: Karel van Houten
Cc: simong@oz.agile.tv; linux-mips@oss.sgi.com
Subject: Re: Recommended toolchain


On Tue, Mar 20, 2001 at 09:12:02PM +0100, Karel van Houten wrote:

> You wrote:
> > Recently I've been working with various version mixes of the gnu tool
> > chain for a mipsel-linux target and settled on a patchy binutils
> > 2.8.1/egcs 1.1.2/glibc 2.0.6 setup. However this lacks the functionality
> > that I would get from a newer toolchain for use with the linux 2.4
> > kernel. As a result, I was wondering if someone could recommend the
> > latest "stable"/recommended toolchain for a mipsel-linux target.
> 
> Well, I'm currently using:
> binutils 2.10.1
> gcc 2.95.3 (with Maciej's patches)
> glibc 2.2.2 (compiled with above toolchain).
> 
> This toolchain works for native compiles on my mipsel box.
> One drawback: I can't compile any kernels with this setup,
> For kernel compiles I use 2.8.1/egcs-2.90.27/glibc-2.0.6.

You MUST use minimum egcs-2.91.66 (1.1.2); older compilers WILL misscompile
kernels.

  Ralf

^ permalink raw reply	[flat|nested] 23+ messages in thread
* recommended toolchain
@ 2003-04-10 19:23 carbonated beverage
  0 siblings, 0 replies; 23+ messages in thread
From: carbonated beverage @ 2003-04-10 19:23 UTC (permalink / raw)
  To: linux-mips

Hi,

	What's the currently recommended toolchain for building MIPS kernels?
I'm working on a NEC VR4111 (mipsel, MIPS16, I, II, III, no LL/SC :P) and
would like to avoid tracking down toolchain bugs.

	Also, Are partial patches (i.e. platform not fully functional yet)
accepted?  Or should I finish a full port (hits userland) first?

	Vadem Clio 1000, reading the 2.4.0-test9 tree that's the last version
I see in CVS and porting to 2.5 (bk pull as of... a while ago).

	Thanks,

-- DN
Daniel

^ permalink raw reply	[flat|nested] 23+ messages in thread
* RE: Recommended toolchain
@ 2001-03-22  9:39 Phil Thompson
  2001-03-22  9:43 ` Geert Uytterhoeven
  0 siblings, 1 reply; 23+ messages in thread
From: Phil Thompson @ 2001-03-22  9:39 UTC (permalink / raw)
  To: 'Geert Uytterhoeven'; +Cc: linux-mips

Correct - I am using the standard 2.4.2 sources. I had (obviously
incorrectly) assumed that the standard sources would be up to date and not
"some months" out of date.

How are the differences in the two trees managed? At what point are the
latest non-MIPS changes applied to the MIPS tree? At what point are the MIPS
specific changes applied to the standard tree?

Thanks,
Phil

-----Original Message-----
From: Geert Uytterhoeven [mailto:Geert.Uytterhoeven@sonycom.com]
Sent: 22 March 2001 07:50
To: Phil Thompson
Cc: 'Erik Mullinix'; linux-mips@oss.sgi.com
Subject: RE: Recommended toolchain


On Wed, 21 Mar 2001, Phil Thompson wrote:
> I had to patch va-mips.h to #include <asm/sgidefs.h> rather than
> <sgidefs.h>.
> 
> The current errors are:
> 
> - warnings about struct flock64 not being declared (it's defined in
> asm-mips64/fcntl.h but not asm-mips/fcntl.h)
> 
> - compilation stops because loops_per_sec is undeclared as far as
> asm-mips/delay.h is concerned (although it seems fine in
> asm-mips64/delay.h).
> 
> This seems to imply that the mips architecture (as opposed to mips64)
isn't
> being maintained. Is this the case? Should I be using mips64 - but what
> would be the point on an embedded CPU?

You're definitely not using the Linux/MIPS CVS tree, since these things were
fixed there some months ago.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven ------------- Sony Software Development Center Europe
(SDCE)
Geert.Uytterhoeven@sonycom.com ------------------- Sint-Stevens-Woluwestraat
55
Voice +32-2-7248626 Fax +32-2-7262686 ---------------- B-1130 Brussels,
Belgium

^ permalink raw reply	[flat|nested] 23+ messages in thread
* RE: Recommended toolchain
@ 2001-03-21 18:46 Phil Thompson
  2001-03-21 22:06 ` Keith M Wesolowski
  2001-03-22  7:49 ` Geert Uytterhoeven
  0 siblings, 2 replies; 23+ messages in thread
From: Phil Thompson @ 2001-03-21 18:46 UTC (permalink / raw)
  To: 'Erik Mullinix', linux-mips

I had to patch va-mips.h to #include <asm/sgidefs.h> rather than
<sgidefs.h>.

The current errors are:

- warnings about struct flock64 not being declared (it's defined in
asm-mips64/fcntl.h but not asm-mips/fcntl.h)

- compilation stops because loops_per_sec is undeclared as far as
asm-mips/delay.h is concerned (although it seems fine in
asm-mips64/delay.h).

This seems to imply that the mips architecture (as opposed to mips64) isn't
being maintained. Is this the case? Should I be using mips64 - but what
would be the point on an embedded CPU?

Thanks,
Phil

-----Original Message-----
From: Erik Mullinix [mailto:Hesp@rainworks.org]
Sent: 21 March 2001 12:12
To: Phil Thompson; linux-mips@oss.sgi.com
Subject: Re: Recommended toolchain


What Error's are you getting?
Hesp
----- Original Message -----
From: "Phil Thompson" <Phil.Thompson@pace.co.uk>
To: <linux-mips@oss.sgi.com>
Sent: Wednesday, March 21, 2001 9:00 AM
Subject: RE: Recommended toolchain


> So, going back to the original question, what are the recommended
versions -
> particularly if you are building 2.4.x kernels?
>
> Are the recomendations in the HOWTO out of date? I had to patch va-mips.h
> from the egcs RPM and more fixes seem to be needed before I get a kernel
> that compiles.
>
> Thanks,
> Phil
>
> -----Original Message-----
> From: Ralf Baechle [mailto:ralf@oss.sgi.com]
> Sent: 20 March 2001 20:37
> To: Karel van Houten
> Cc: simong@oz.agile.tv; linux-mips@oss.sgi.com
> Subject: Re: Recommended toolchain
>
>
> On Tue, Mar 20, 2001 at 09:12:02PM +0100, Karel van Houten wrote:
>
> > You wrote:
> > > Recently I've been working with various version mixes of the gnu tool
> > > chain for a mipsel-linux target and settled on a patchy binutils
> > > 2.8.1/egcs 1.1.2/glibc 2.0.6 setup. However this lacks the
functionality
> > > that I would get from a newer toolchain for use with the linux 2.4
> > > kernel. As a result, I was wondering if someone could recommend the
> > > latest "stable"/recommended toolchain for a mipsel-linux target.
> >
> > Well, I'm currently using:
> > binutils 2.10.1
> > gcc 2.95.3 (with Maciej's patches)
> > glibc 2.2.2 (compiled with above toolchain).
> >
> > This toolchain works for native compiles on my mipsel box.
> > One drawback: I can't compile any kernels with this setup,
> > For kernel compiles I use 2.8.1/egcs-2.90.27/glibc-2.0.6.
>
> You MUST use minimum egcs-2.91.66 (1.1.2); older compilers WILL
misscompile
> kernels.
>
>   Ralf
>

^ permalink raw reply	[flat|nested] 23+ messages in thread
* Recommended toolchain
@ 2001-03-20  3:06 Simon Gee
  2001-03-20 20:12 ` Karel van Houten
  0 siblings, 1 reply; 23+ messages in thread
From: Simon Gee @ 2001-03-20  3:06 UTC (permalink / raw)
  To: linux-mips

Hello,

Recently I've been working with various version mixes of the gnu tool
chain for a mipsel-linux target and settled on a patchy binutils
2.8.1/egcs 1.1.2/glibc 2.0.6 setup. However this lacks the functionality
that I would get from a newer toolchain for use with the linux 2.4
kernel. As a result, I was wondering if someone could recommend the
latest "stable"/recommended toolchain for a mipsel-linux target.

Thanks in advance,

Simon

^ permalink raw reply	[flat|nested] 23+ messages in thread

end of thread, other threads:[~2003-04-10 19:24 UTC | newest]

Thread overview: 23+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-03-21 14:00 Recommended toolchain Phil Thompson
2001-03-21 12:11 ` Erik Mullinix
2001-03-21 16:06 ` Keith M Wesolowski
  -- strict thread matches above, loose matches on Subject: below --
2003-04-10 19:23 recommended toolchain carbonated beverage
2001-03-22  9:39 Recommended toolchain Phil Thompson
2001-03-22  9:43 ` Geert Uytterhoeven
2001-03-21 18:46 Phil Thompson
2001-03-21 22:06 ` Keith M Wesolowski
2001-03-22  7:49 ` Geert Uytterhoeven
2001-03-20  3:06 Simon Gee
2001-03-20 20:12 ` Karel van Houten
2001-03-20 20:12   ` Karel van Houten
2001-03-20 20:37   ` Ralf Baechle
2001-03-20 20:37     ` Ralf Baechle
2001-03-27 19:02   ` Maciej W. Rozycki
2001-03-29 17:28     ` Houten K.H.C. van (Karel)
2001-03-29 17:28       ` Houten K.H.C. van (Karel)
2001-03-29 17:39       ` Karel van Houten
2001-03-29 17:39         ` Karel van Houten
2001-03-29 18:10         ` Maciej W. Rozycki
2001-04-01 14:39           ` Houten K.H.C. van (Karel)
2001-04-01 18:54             ` Florian Lohoff
2001-03-29 17:51       ` Maciej W. Rozycki

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox