On Mon, Feb 07, 2005 at 05:32:05PM +0100, [EMAIL PROTECTED] wrote:
> On Mon, Feb 07, 2005 at 09:20:28AM -0700, Kevin Rosenberg wrote:
> > [EMAIL PROTECTED] wrote:
> > > Kevin, could this be related to the first time build vs. build with
> > > a previously installed openmcl bug i recently reported t
On Mon, Feb 07, 2005 at 09:20:28AM -0700, Kevin Rosenberg wrote:
> [EMAIL PROTECTED] wrote:
> > Kevin, could this be related to the first time build vs. build with
> > a previously installed openmcl bug i recently reported to you?
>
> I don't think so. It doesn't involve building openmcl, it is
>
[EMAIL PROTECTED] wrote:
> Kevin, could this be related to the first time build vs. build with
> a previously installed openmcl bug i recently reported to you?
I don't think so. It doesn't involve building openmcl, it is
intermittant on kernel 2.6, and non-existant on kernel 2.4.
--
Kevin Rosenb
On Sun, Feb 06, 2005 at 09:20:14AM -0700, Kevin Rosenberg wrote:
> Fabian Linzberger wrote:
> > the problem seems to go away, if i apt-get source openmcl, build the
> > package locally and install that one. as far as i can tell, things
> > work fine now. let me know if i can do anything to help you
Fabian Linzberger wrote:
> the problem seems to go away, if i apt-get source openmcl, build the
> package locally and install that one. as far as i can tell, things
> work fine now. let me know if i can do anything to help you reproduce
> this.
That's odd as the package should be identical (save f
replying to myself to add more info:
the problem seems to go away, if i apt-get source openmcl, build the
package locally and install that one. as far as i can tell, things
work fine now. let me know if i can do anything to help you reproduce
this.
cheers
fabian
--
.''`. fabian linzberger
6 matches
Mail list logo
