linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: mlan@cpu.lu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Compile error with Paul's pmac-devel rsync tree
Date: Wed, 09 Aug 2000 23:07:21 +0200	[thread overview]
Message-ID: <3991C809.C240929D@wanadoo.fr> (raw)
In-Reply-To: 200008091942.VAA06989@piglet.grunz.lu


Michel Lanners wrote:
>
> Hi all,
>
> Thought I let you all know so you don't have to search for yourself.
> Patch is below...
>
> - There is a problem in compiling ext2 fs support, in fs/ext2/dir.c.
>   This looks like part of a patch submitted to linux-kernel sometime in
>   June. I haven't checked whether this is wrong in kernel.org kernels as
>   well...

I think this has been corrected already earlier today. Just rsync again.
It's funny to look at this in bitkeeper: it has been changed back and
forth several times.

> - The same goes for mark_buffer_dirty_inode() in fs/ext2/truncate.c,
>   which seems to come out of the same patch...

Also fixed as of 8:30 GMT today.

I had sometimes problems loading modules with this version, even with
modutils-2.3.14. I am not quite sure what was the cause, it just didn't
work ("module de4x5 not found"). Sometimes it just worked (I am running
it right now).

Otherwise standard bugs persist:
- No mounting of HFS CDs
- No mounting of loop devices
- No strace

Another bug of Paul's devel tree in comparison with the bitkeeper tree:
There is something wrong with the passing of environment variables. I
have been seeing this at least since 2.4.0-test1-ac18, but I still
haven't quite understood what is going on.

--
Martin

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

  reply	other threads:[~2000-08-09 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-09 19:42 Compile error with Paul's pmac-devel rsync tree Michel Lanners
2000-08-09 21:07 ` Martin Costabel [this message]
2000-08-10  5:55   ` Michel Lanners

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=3991C809.C240929D@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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;
as well as URLs for NNTP newsgroup(s).