All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Carsten Langgaard <carstenl@mips.com>, linux-mips@oss.sgi.com
Subject: Re: Updates on RedHat 7.1/mips
Date: Wed, 18 Jul 2001 09:48:42 -0700	[thread overview]
Message-ID: <20010718094841.A24612@nevyn.them.org> (raw)
In-Reply-To: <20010718152631.A1809@bacchus.dhis.org>; from ralf@oss.sgi.com on Wed, Jul 18, 2001 at 03:26:31PM +0200

On Wed, Jul 18, 2001 at 03:26:31PM +0200, Ralf Baechle wrote:
> On Wed, Jul 18, 2001 at 09:13:20AM +0200, Carsten Langgaard wrote:
> 
> > 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 (pbuild)
> > 
> > So tcsh is needed to build perl and perl is needed to build tcsh :-(
> 
> One of the reasons why I believe that the major Linux distributions are
> fundamentally flawed - their build process doesn't account for such
> dependencies.  Point for BSD.

Debian has been going to great lengths to fix this.  We're a great deal
of the way along, too - to the point where bringing up our complete
hppa and ia64 distributions (with the exception of a few
platform-specific tool bugs and some gcc-3.0 incompatibilities) was
really relatively painless for the vast majority of packages.  Only a
tiny subset of packages are assumed installed at build time if they
aren't explicitly listed.

> The escape from this circular dependency is to build those packages manually
> which may require cheating in the configure and build process a bit.  Or
> install them from a binary package (which may require --nodeps and --force
> to install).  General rule therefore should be to only do such distribution
> package builds on systems which have a maximum installation.

Although I'm pretty sure that Debian's Perl package builds without the
use of tcsh... I've no idea where this is coming from.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2001-07-18 16:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18 13:26 Updates on RedHat 7.1/mips Ralf Baechle
2001-07-18 16:48 ` Daniel Jacobowitz [this message]
2001-07-18 22:23   ` Ralf Baechle
2001-07-19 13:29     ` Florian Lohoff
  -- strict thread matches above, loose matches on Subject: below --
2001-07-18 12:07 Gleb O. Raiko
2001-07-06  8:15 Illegal instruction Carsten Langgaard
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
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

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=20010718094841.A24612@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carstenl@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.