Re: lang/gcc on macppc
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.
Re: lang/gcc on macppc
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 be because of a worn out motherboard. I think this machine was heavily used back in the day.
Re: lang/gcc on macppc
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 new hard > > drive and it's making the machine unusable. > > To clarify: this could be because of a worn out motherboard. I think > this machine was heavily used back in the day. I doubt it, it's much more likely you have a machine for which we miss some small workaround. Apple hardware is buggy as hell.
Re: lang/gcc on macppc
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 debugging this? Ports gdb should work. You can iirc set a breakpoint on 'constraint_error' (exception handler), the function that caused the SIGBUS should be in the stack trace. > > > > > > > true DO=all multi-do # gmake > > gmake[4]: Leaving directory '/home/build/build-powerpc/libbacktrace' > > gmake[3]: Leaving directory '/home/build/build-powerpc/libbacktrace' > > gmake[3]: Entering directory '/home/build/build-powerpc/libcpp' > > test -f config.h || (rm -f stamp-h1 && gmake stamp-h1) > > gmake[3]: Leaving directory '/home/build/build-powerpc/libcpp' > > gmake[3]: Entering directory '/home/build/build-powerpc/libdecnumber' > > gmake[3]: Nothing to be done for 'all'. > > gmake[3]: Leaving directory '/home/build/build-powerpc/libdecnumber' > > gmake[3]: Entering directory '/home/build/build-powerpc/gcc' > > /home/build/build-powerpc/./prev-gcc/gnatbind -nostdinc -I- -I. -Iada > > -I/home/build/gcc-4.9.3/gcc/ada > > -I/home/build/gcc-4.9.3/gcc/ada/gcc-interface -o b_gnat1.adb -n > > ada/gnat1drv.ali > > > > raised CONSTRAINT_ERROR : SIGBUS > > /home/build/gcc-4.9.3/gcc/ada/gcc-interface/Make-lang.in:932: recipe for > > target 'ada/b_gnat1.adb' failed > > gmake[3]: *** [ada/b_gnat1.adb] Error 1 > > gmake[3]: Leaving directory '/home/build/build-powerpc/gcc' > > Makefile:4256: recipe for target 'all-stage2-gcc' failed > > gmake[2]: *** [all-stage2-gcc] Error 2 > > gmake[2]: Leaving directory '/home/build/build-powerpc' > > Makefile:18532: recipe for target 'stage2-bubble' failed > > gmake[1]: *** [stage2-bubble] Error 2 > > gmake[1]: Leaving directory '/home/build/build-powerpc' > > Makefile:18551: recipe for target 'bootstrap2' failed > > gmake: *** [bootstrap2] Error 2 > > >
Re: Spending time for macppc - taken from [Re: lang/gcc on macppc]
> 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. As it depends on the defination - what a desktop is, also the help of other macppc users is needed. > It's an insane amount of work since freesotfware application are no > longer tested on bigendian and/or powerpc machines. Then we should change that - as long as OpenBSD/macppc is alive.
Re: lang/gcc on macppc
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 bug. > > The build is successful with Ada disabled. > > 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. > > > true DO=all multi-do # gmake > gmake[4]: Leaving directory '/home/build/build-powerpc/libbacktrace' > gmake[3]: Leaving directory '/home/build/build-powerpc/libbacktrace' > gmake[3]: Entering directory '/home/build/build-powerpc/libcpp' > test -f config.h || (rm -f stamp-h1 && gmake stamp-h1) > gmake[3]: Leaving directory '/home/build/build-powerpc/libcpp' > gmake[3]: Entering directory '/home/build/build-powerpc/libdecnumber' > gmake[3]: Nothing to be done for 'all'. > gmake[3]: Leaving directory '/home/build/build-powerpc/libdecnumber' > gmake[3]: Entering directory '/home/build/build-powerpc/gcc' > /home/build/build-powerpc/./prev-gcc/gnatbind -nostdinc -I- -I. -Iada > -I/home/build/gcc-4.9.3/gcc/ada -I/home/build/gcc-4.9.3/gcc/ada/gcc-interface > -o b_gnat1.adb -n ada/gnat1drv.ali > > raised CONSTRAINT_ERROR : SIGBUS > /home/build/gcc-4.9.3/gcc/ada/gcc-interface/Make-lang.in:932: recipe for > target 'ada/b_gnat1.adb' failed > gmake[3]: *** [ada/b_gnat1.adb] Error 1 > gmake[3]: Leaving directory '/home/build/build-powerpc/gcc' > Makefile:4256: recipe for target 'all-stage2-gcc' failed > gmake[2]: *** [all-stage2-gcc] Error 2 > gmake[2]: Leaving directory '/home/build/build-powerpc' > Makefile:18532: recipe for target 'stage2-bubble' failed > gmake[1]: *** [stage2-bubble] Error 2 > gmake[1]: Leaving directory '/home/build/build-powerpc' > Makefile:18551: recipe for target 'bootstrap2' failed > gmake: *** [bootstrap2] Error 2 >
Re: lang/gcc on macppc
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 is successful with Ada disabled. > > Is this a known issue? Let me know if a full build log would be useful. Are you using GENERIC.MP or GENERIC? Does it make a difference? Could it be related to a bug in our binutils? macppc is starting to be unusable as desktop because nobody is spending time to ensure the ports build and run correctly.
Spending time for macppc - taken from [Re: lang/gcc on macppc]
> 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) ?
Re: Spending time for macppc - taken from [Re: lang/gcc on macppc]
> 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 kickout good old working things which they payed many years ago for a high amount. And there is also good used hardware out there. >> If I am interested spending time, could I get some help (specially >> as >> if I decided to learn coding)? > > With the PowerPC part, yeah, but you'll have to learn to code on your > own. That is clear. My point is, that it is also sad if the platform dies (I know, the time when it will be end of life will come). I have no plans to become a professional coder. Just what you read often, work on what annoys you. As I wrote at misc@ I have no problem to admit, that I don't know many things but I am willing to learn - that needs (often many) help. > Do you have macppc hardware? A PowerMac G5 should be on the way to me. I also have a look at other nice machines.
Re: Spending time for macppc - taken from [Re: lang/gcc on macppc]
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 stuff is aging. Apple certainly isn't, and our port is Mac-specific. > If I am interested spending time, could I get some help (specially as > if I decided to learn coding)? With the PowerPC part, yeah, but you'll have to learn to code on your own. Do you have macppc hardware?
Re: lang/gcc on macppc
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 bug. > > The build is successful with Ada disabled. For ada bugs, add always to tobiasu@ to the CC. > > Is this a known issue? Let me know if a full build log would be useful. > > > true DO=all multi-do # gmake > gmake[4]: Leaving directory '/home/build/build-powerpc/libbacktrace' > gmake[3]: Leaving directory '/home/build/build-powerpc/libbacktrace' > gmake[3]: Entering directory '/home/build/build-powerpc/libcpp' > test -f config.h || (rm -f stamp-h1 && gmake stamp-h1) > gmake[3]: Leaving directory '/home/build/build-powerpc/libcpp' > gmake[3]: Entering directory '/home/build/build-powerpc/libdecnumber' > gmake[3]: Nothing to be done for 'all'. > gmake[3]: Leaving directory '/home/build/build-powerpc/libdecnumber' > gmake[3]: Entering directory '/home/build/build-powerpc/gcc' > /home/build/build-powerpc/./prev-gcc/gnatbind -nostdinc -I- -I. -Iada > -I/home/build/gcc-4.9.3/gcc/ada -I/home/build/gcc-4.9.3/gcc/ada/gcc-interface > -o b_gnat1.adb -n ada/gnat1drv.ali > > raised CONSTRAINT_ERROR : SIGBUS > /home/build/gcc-4.9.3/gcc/ada/gcc-interface/Make-lang.in:932: recipe for > target 'ada/b_gnat1.adb' failed > gmake[3]: *** [ada/b_gnat1.adb] Error 1 > gmake[3]: Leaving directory '/home/build/build-powerpc/gcc' > Makefile:4256: recipe for target 'all-stage2-gcc' failed > gmake[2]: *** [all-stage2-gcc] Error 2 > gmake[2]: Leaving directory '/home/build/build-powerpc' > Makefile:18532: recipe for target 'stage2-bubble' failed > gmake[1]: *** [stage2-bubble] Error 2 > gmake[1]: Leaving directory '/home/build/build-powerpc' > Makefile:18551: recipe for target 'bootstrap2' failed > gmake: *** [bootstrap2] Error 2 > -- Juan Francisco Cantero Hurtado http://juanfra.info
Re: Spending time for macppc - taken from [Re: lang/gcc on macppc]
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 that can be improved in OpenBSD that I now prefer to spend my time in something else. > If I am interested spending time, could I get some help (specially as > if I decided to learn coding) ? 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. It's an insane amount of work since freesotfware application are no longer tested on bigendian and/or powerpc machines.
Re: lang/gcc on macppc
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 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 me know if a full build log would be useful. > > Are you using GENERIC.MP or GENERIC? Does it make a difference? > > Could it be related to a bug in our binutils? > > macppc is starting to be unusable as desktop because nobody is spending > time to ensure the ports build and run correctly. Someone with enough skills should work with landry@ to reduce the bulk build times. The packages are almost always outdated because a full bulk build takes weeks(?). A slow architecture without a weekly update to the packages is not going to attract a lot of desktop users :( -- Juan Francisco Cantero Hurtado http://juanfra.info
lang/gcc on macppc
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 me know if a full build log would be useful. true DO=all multi-do # gmake gmake[4]: Leaving directory '/home/build/build-powerpc/libbacktrace' gmake[3]: Leaving directory '/home/build/build-powerpc/libbacktrace' gmake[3]: Entering directory '/home/build/build-powerpc/libcpp' test -f config.h || (rm -f stamp-h1 && gmake stamp-h1) gmake[3]: Leaving directory '/home/build/build-powerpc/libcpp' gmake[3]: Entering directory '/home/build/build-powerpc/libdecnumber' gmake[3]: Nothing to be done for 'all'. gmake[3]: Leaving directory '/home/build/build-powerpc/libdecnumber' gmake[3]: Entering directory '/home/build/build-powerpc/gcc' /home/build/build-powerpc/./prev-gcc/gnatbind -nostdinc -I- -I. -Iada -I/home/build/gcc-4.9.3/gcc/ada -I/home/build/gcc-4.9.3/gcc/ada/gcc-interface -o b_gnat1.adb -n ada/gnat1drv.ali raised CONSTRAINT_ERROR : SIGBUS /home/build/gcc-4.9.3/gcc/ada/gcc-interface/Make-lang.in:932: recipe for target 'ada/b_gnat1.adb' failed gmake[3]: *** [ada/b_gnat1.adb] Error 1 gmake[3]: Leaving directory '/home/build/build-powerpc/gcc' Makefile:4256: recipe for target 'all-stage2-gcc' failed gmake[2]: *** [all-stage2-gcc] Error 2 gmake[2]: Leaving directory '/home/build/build-powerpc' Makefile:18532: recipe for target 'stage2-bubble' failed gmake[1]: *** [stage2-bubble] Error 2 gmake[1]: Leaving directory '/home/build/build-powerpc' Makefile:18551: recipe for target 'bootstrap2' failed gmake: *** [bootstrap2] Error 2
Re: lang/gcc on macppc
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 bug. Macppc reliably failing to build stuff is a normal behaviour :) I get random toolchain failures all the time on macppc*.ports Landry
