* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> On Wednesday, 2 of January 2008, Ingo Molnar wrote:
> >
> > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> >
> > > > Try to delete your fs/ directory in your output dir. Then I expect
> > > > the same bug to surface again.
> > >
> > > It
On Wednesday, 2 of January 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > > Try to delete your fs/ directory in your output dir. Then I expect
> > > the same bug to surface again.
> >
> > It does surface indeed.
>
> could you try the patch from Sam below -
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > Try to delete your fs/ directory in your output dir. Then I expect
> > the same bug to surface again.
>
> It does surface indeed.
could you try the patch from Sam below - does it fix the problem?
Thanks,
Ingo
-->
Subject:
* Rafael J. Wysocki [EMAIL PROTECTED] wrote:
Try to delete your fs/ directory in your output dir. Then I expect
the same bug to surface again.
It does surface indeed.
could you try the patch from Sam below - does it fix the problem?
Thanks,
Ingo
--
Subject: x86
On Wednesday, 2 of January 2008, Ingo Molnar wrote:
* Rafael J. Wysocki [EMAIL PROTECTED] wrote:
Try to delete your fs/ directory in your output dir. Then I expect
the same bug to surface again.
It does surface indeed.
could you try the patch from Sam below - does it fix the
* Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Wednesday, 2 of January 2008, Ingo Molnar wrote:
* Rafael J. Wysocki [EMAIL PROTECTED] wrote:
Try to delete your fs/ directory in your output dir. Then I expect
the same bug to surface again.
It does surface indeed.
6 matches
Mail list logo