From: Ilya Volynets <ilya@theIlya.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux-mips@oss.sgi.com
Subject: Re: Updates on RedHat 7.1/mips
Date: Tue, 17 Jul 2001 13:09:00 -0700 [thread overview]
Message-ID: <01071713090011.04620@gateway> (raw)
In-Reply-To: <20010717125718.A24725@lucon.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 17 July 2001 12:57, H . J . Lu wrote:
> On Tue, Jul 17, 2001 at 12:50:27PM -0700, Daniel Jacobowitz wrote:
> > > Perl has to be built natively. I uploaded mysql-3.23.36-1.1.src.rpm,
> > > perl-5.6.0-12.1.src.rpm, apache-1.3.19-5.src.rpm,
> > > mod_perl-1.24_01-2.src.rpm, tcsh-6.10-5.src.rpm and
> > > zsh-3.0.8-8.src.rpm. Just installed my RedHat 7.1. Then you can build
> > > perl yourself. You may need to build/install the tcsh rpm first.
> >
> > It's not yet available for MIPS (later this week), but MontaVista
> > Journeyman contains the patches to cross-compile Perl. It's not pretty,
> > though.
>
> That is a reason why I didn't bother with cross-compile Perl :-). The
> next thing on my todo list is to cross compile XFree86 :-(.
If you can get cross-compiling full XFree86, you'll be a hero of all times.
It shouldn't be hard to get it with KDriveArchitecture & TinyX enabled.
I was working on it a while ago, and here are few pointers:
Some tools have to be run natively (i.e. xkbcomp), but also need to
be installed on target. I din't find a rule that does both. I think new
rule is needed.
gcc-3.0 crashes when compiling some parts of Xserver and Xlib,
with very obscure bug. Minimal test case I came up with is
~45(!) lines long. Keith filed report to gcc team on my behalf,
but there seems to be no responce. I do not know if your
gcc has same problem, but someone mentioned similar problem
with 2.9x.y series on this list not so long ago.
Hmm... I can't remember any other interesting things at this moment, but if I
will, I'll follow up...
Ilya.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjtUm18ACgkQtKh84cA8u2ll+QCfSjexRpQ2H7Qa16JYrun/vvVd
vCQAoIKb1BRxJ/508SWu9uHEP0okhH00
=kWTa
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-07-17 20:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 8:15 Illegal instruction Carsten Langgaard
2001-07-06 9:27 ` Houten K.H.C. van (Karel)
2001-07-06 11:42 ` Maciej W. Rozycki
2001-07-06 13:26 ` Dan Aizenstros
2001-07-06 22:04 ` Jun Sun
2001-07-10 11:14 ` Carsten Langgaard
2001-07-10 17:31 ` H . J . Lu
2001-07-16 11:26 ` Carsten Langgaard
2001-07-16 21:28 ` Updates on RedHat 7.1/mips H . J . Lu
2001-07-17 19:16 ` Carsten Langgaard
2001-07-17 19:29 ` H . J . Lu
2001-07-17 19:50 ` Daniel Jacobowitz
2001-07-17 19:57 ` H . J . Lu
2001-07-17 20:09 ` Ilya Volynets [this message]
2001-07-17 20:11 ` H . J . Lu
2001-07-18 3:52 ` Arnaldo Carvalho de Melo
2001-07-18 4:01 ` Ilya Volynets
2001-07-18 7:13 ` Carsten Langgaard
2001-07-18 15:11 ` H . J . Lu
2001-07-18 15:23 ` Carsten Langgaard
2001-07-18 20:53 ` Seth Mos
2001-07-19 0:36 ` H . J . Lu
2001-07-19 21:03 ` Seth Mos
-- strict thread matches above, loose matches on Subject: below --
2001-07-18 12:07 Gleb O. Raiko
2001-07-18 13:26 Ralf Baechle
2001-07-18 16:48 ` Daniel Jacobowitz
2001-07-18 22:23 ` Ralf Baechle
2001-07-19 13:29 ` Florian Lohoff
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=01071713090011.04620@gateway \
--to=ilya@theilya.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
/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