Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Carsten Langgaard <carstenl@mips.com>
Cc: Jun Sun <jsun@mvista.com>,
	ralf@oss.sgi.com, vhouten@kpn.com, linux-mips@oss.sgi.com
Subject: Re: Updates on RedHat 7.1/mips
Date: Wed, 18 Jul 2001 08:11:22 -0700	[thread overview]
Message-ID: <20010718081122.A10848@lucon.org> (raw)
In-Reply-To: <3B553710.8B7A4CDE@mips.com>; from carstenl@mips.com on Wed, Jul 18, 2001 at 09:13:20AM +0200

On Wed, Jul 18, 2001 at 09:13:20AM +0200, Carsten Langgaard wrote:
> "H . J . Lu" wrote:
> 
> > On Tue, Jul 17, 2001 at 09:16:05PM +0200, Carsten Langgaard wrote:
> > > Could you add a Perl rpm to you distribution, this also seems to be needed to
> > > build the RPMs natively.
> >
> > 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 look like there is a cross dependence, the build of tcsh failed with the
> following message:
> 
> /var/tmp/rpm-tmp.7250: /usr/bin/perl: No such file or directory
> error: Bad exit status from /var/tmp/rpm-tmp.7250 (%build)
> 
> So tcsh is needed to build perl and perl is needed to build tcsh :-(
> 

It is ok since the tcsh binary has been built. Just install it to
/bin/tcsh and build the perl rpm. You may have to

# rpm --nodeps --force --rebuild perl-xxx.src.rpm

You only have to do those the first time.



H.J.

  reply	other threads:[~2001-07-18 15:11 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
2001-07-18  7:13               ` Carsten Langgaard
2001-07-18 15:11                 ` H . J . Lu [this message]
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=20010718081122.A10848@lucon.org \
    --to=hjl@lucon.org \
    --cc=carstenl@mips.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=vhouten@kpn.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