From: Ilya Volynets <ilya@theIlya.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
"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 21:01:20 -0700 [thread overview]
Message-ID: <01071721012019.04620@gateway> (raw)
In-Reply-To: <20010718005255.R10373@conectiva.com.br>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Those messages are about compiling using TinyX and KDrive, which
works with only minor modifications. Thing is, it is not what is really needed.
On Tuesday 17 July 2001 20:52, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jul 17, 2001 at 01:11:46PM -0700, H . J . Lu escreveu:
> > On Tue, Jul 17, 2001 at 01:09:00PM -0700, Ilya Volynets wrote:
> > > 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.
> >
> > I am aware of those. I want to delay it as much as I can.
>
> recent messages to the XFree86 mailing lists has the recipe to x-compile
> XFree86, IIRC Keith Packard did the work
>
> > > 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.
> >
> > Don't bother with gcc-3.0. I won't use it myself for building X.
> >
> >
> > H.J.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjtVChMACgkQtKh84cA8u2nRTACgvPDSNX0E62POj2W+QkntYE9l
pzIAnAjjprS4qWgUfELszqT94T+XGV0C
=tJST
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-07-18 4:01 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
2001-07-17 20:11 ` H . J . Lu
2001-07-18 3:52 ` Arnaldo Carvalho de Melo
2001-07-18 4:01 ` Ilya Volynets [this message]
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=01071721012019.04620@gateway \
--to=ilya@theilya.com \
--cc=acme@conectiva.com.br \
--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