Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 2.4.0 merge mangle our tree?
Date: Thu, 25 Jan 2001 12:00:27 +0000	[thread overview]
Message-ID: <20010125120027.P3571@linuxcare.com> (raw)
In-Reply-To: <20010125101918.M3571@linuxcare.com>; from rhirst@linuxcare.com on Thu, Jan 25, 2001 at 10:19:18AM +0000

On Thu, Jan 25, 2001 at 10:19:18AM +0000, Richard Hirst wrote:
> Main branch is certainly broken.  e.g. drivers/pci/Makefile makes
> drivers/pci/pci.a but Makefile tries to link drivers/pci/drivers.o
> I fixed that in my tree but then got masses of unresolved
> references on the final link.

For the main branch, Makefile appears to be from 2.4.0, but
drivers/pci/Makefile isn't.  I dropped in a new drivers/pci/Makefile
and the next problem is that it isn't building anything in arch/parisc/lib.
Make.Rules change, maybe.

Giving up for now,
  Richard

  reply	other threads:[~2001-01-25 12:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25  3:46 [parisc-linux] 2.4.0 merge mangle our tree? Grant Grundler
2001-01-25  4:19 ` Michael Ang
2001-01-25 13:02   ` Matthew Wilcox
2001-01-25 14:56     ` Michael Ang
2001-01-25 15:06       ` Matthew Wilcox
2001-01-25 10:19 ` Richard Hirst
2001-01-25 12:00   ` Richard Hirst [this message]
2001-01-25 17:33   ` [parisc-linux] C100 improvements, problems Greg Ingram
2001-01-25 17:36     ` Richard Hirst
2001-01-26 18:16       ` Greg Ingram
2001-02-04 12:11         ` Richard Hirst
2001-01-25 17:42     ` Matthew Wilcox
2001-01-26 18:17       ` [parisc-linux] C100 report, latest CVS bits Greg Ingram
2001-01-25 18:24   ` [parisc-linux] 2.4.0 merge mangle our tree? Grant Grundler
2001-01-25 17:24 ` Matthew Wilcox

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=20010125120027.P3571@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.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