public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel•com>
To: Jacky Lam <jackylam@astri•org>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: Queston about Walnut
Date: Fri, 03 Oct 2003 10:31:17 -0700	[thread overview]
Message-ID: <3F7DB265.8050408@kegel.com> (raw)
In-Reply-To: <001b01c389cd$c3f30310$0202a8c0@homevl9biy3v7e>


Jacky Lam wrote:
>     I upgrade my gcc to 3.3.1 on my host and start to compile my cross
> toolchain. However, while it is compiling gcc, it has strange error that I
> have never seen (seems gcc has made something that ld can't understand). So,
> I guess gcc 3.3.1 may not work very well with my old glibc (provided in
> RedHat 7.2). I don't know how to upgrade glibc safely and make it compatible
> to existing applications. That's why I would like to upgrade the whole
> Redhat.....and this is painful...

I see.  Well, you can always build and install a newer binutils;
that's not painful, and might get you past the problem.
(If you post the error message, we might be able to help.)

But I agree that doing a fresh install of e.g. Red Hat 9 is
nicer than keeping an old system alive by little patches
(unless you're going for an uptime record).

>># Download bk from http://www.bitkeeper.com
>>bk clone -r$1 bk://ppc.bkserver.net/linuxppc_2_4_devel
>
>         I use CVS to grab the linuxppc-2.4-devel module. Is it the same as
> that? Thanks.

Probably.  I dunno.
- Dan


--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-03 17:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000e01c388dc$eb525510$0202a8c0@homevl9biy3v7e>
2003-10-02 12:17 ` Queston about Walnut Wolfgang Denk
2003-10-03  1:18   ` Jacky Lam
     [not found]     ` <3F7D3238.2090400@bluewin.ch>
2003-10-03  9:40       ` Jacky Lam
2003-10-03 15:07         ` Matt Porter
2003-10-03 16:34           ` Jacky Lam
2003-10-04 16:07             ` Matt Porter
2003-10-03 16:10         ` Dan Kegel
2003-10-03 16:45           ` Jacky Lam
2003-10-03 17:31             ` Dan Kegel [this message]
     [not found]       ` <20031003151729.GC21468@ip68-0-152-218.tc.ph.cox.net>
2003-10-03 23:36         ` Kernel versions Gary Thomas
2003-10-07 13:37           ` Tom Rini
2003-10-03  4:11   ` Queston about Walnut Jacky Lam
2003-10-03  7:44     ` Jacky Lam
2003-10-03 13:51 ARIBAUD Albert
  -- strict thread matches above, loose matches on Subject: below --
2003-10-03  7:57 ARIBAUD Albert
2003-10-03  8:26 ` Jacky Lam
2003-10-02  9:17 Jacky Lam
2003-10-02 10:13 ` Wolfgang Denk

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=3F7DB265.8050408@kegel.com \
    --to=dank@kegel$(echo .)com \
    --cc=jackylam@astri$(echo .)org \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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