On Sat, Feb 13, 2016 at 07:10:06PM -0500, Michael McConville wrote:
> Michael McConville wrote:
> > Have you guys had issues with wd(4) timeouts on macppc? It was
> > happening intermittently, but I figured it was because the drive was
> > old. However, I'm now experiencing it again with a brand ne
Michael McConville wrote:
> Have you guys had issues with wd(4) timeouts on macppc? It was
> happening intermittently, but I figured it was because the drive was
> old. However, I'm now experiencing it again with a brand new hard
> drive and it's making the machine unusable.
To clarify: this could
Have you guys had issues with wd(4) timeouts on macppc? It was happening
intermittently, but I figured it was because the drive was old. However,
I'm now experiencing it again with a brand new hard drive and it's
making the machine unusable.
On Thu, Feb 04, 2016 at 11:26:48PM +0100, Tobias Ulmer wrote:
> > Is this a known issue? Let me know if a full build log would be useful.
>
> News to me, I'll see whether I can reproduce it. Keep the failed build
> around for a while if possible.
Can't reproduce :/. Are you interested in debuggin
On Thu, Feb 04, 2016 at 12:29:05AM -0500, Michael McConville wrote:
> I'm getting the below error when building the GCC port on a Power Mac G5
> running the most recent snapshot. It fails reliably when I retry the
> build, so it doesn't seem like an Act of God(TM) caused by a kernel or
> hardware b
> My opinion is that there are so many things that can be improved in
> OpenBSD that I now prefer to spend my time in something else.
Ok.
> Well first thing to do is to try to use a macppc as desktop. Then
> figure out what's missing/not working then find the bugs and fix them.
That was my idea
On Thu, Feb 04, 2016 at 03:40:48PM +0100, Martin Pieuchot wrote:
> On 04/02/16(Thu) 00:29, Michael McConville wrote:
> > I'm getting the below error when building the GCC port on a Power Mac G5
> > running the most recent snapshot. It fails reliably when I retry the
> > build, so it doesn't seem li
On 04/02/16(Thu) 18:57, Christoph R. Murauer wrote:
> > macppc is starting to be unusable as desktop because nobody
> > is spending time to ensure the ports build and run correctly.
> >
>
> Seriously asked, what is the reason, that noone spent time ?
My opinion is that there are so many things th
On Thu, Feb 04, 2016 at 12:29:05AM -0500, Michael McConville wrote:
> I'm getting the below error when building the GCC port on a Power Mac G5
> running the most recent snapshot. It fails reliably when I retry the
> build, so it doesn't seem like an Act of God(TM) caused by a kernel or
> hardware b
> There's effectively no one making new PowerPC hardware and the
> existing stuff is aging. Apple certainly isn't, and our port is
> Mac-specific.
Yes, true. There are many people who reads the macppc mailing list so,
there are people out there who use the machines. It would be sad if
people kicko
Christoph R. Murauer wrote:
> > macppc is starting to be unusable as desktop because nobody
> > is spending time to ensure the ports build and run correctly.
> >
>
> Seriously asked, what is the reason, that noone spent time?
There's effectively no one making new PowerPC hardware and the existing
> macppc is starting to be unusable as desktop because nobody
> is spending time to ensure the ports build and run correctly.
>
Seriously asked, what is the reason, that noone spent time ?
If I am interested spending time, could I get some help (specially as
if I decided to learn coding) ?
On 04/02/16(Thu) 00:29, Michael McConville wrote:
> I'm getting the below error when building the GCC port on a Power Mac G5
> running the most recent snapshot. It fails reliably when I retry the
> build, so it doesn't seem like an Act of God(TM) caused by a kernel or
> hardware bug.
>
> The build
On Thu, Feb 04, 2016 at 12:29:05AM -0500, Michael McConville wrote:
> I'm getting the below error when building the GCC port on a Power Mac G5
> running the most recent snapshot. It fails reliably when I retry the
> build, so it doesn't seem like an Act of God(TM) caused by a kernel or
> hardware b
I'm getting the below error when building the GCC port on a Power Mac G5
running the most recent snapshot. It fails reliably when I retry the
build, so it doesn't seem like an Act of God(TM) caused by a kernel or
hardware bug.
The build is successful with Ada disabled.
Is this a known issue? Let
15 matches
Mail list logo
