[openbeos] Various development problems and BeOS annoyances
- From: "Ryan Leavengood" <leavengood@xxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 14 Nov 2006 20:08:46 -0800 (PST)
I decided to try to fix bugs #177 and #180 where the input server is
not notified when the system is shutting down. This seemed easy enough.
So I started reading code and making some experimental changes to the
registrar and input server, but of course testing this is tricky. I
decided to use QEMU since there is the option to output the serial
debugging to standard out.
Anyhow, my problems started when I set my DEBUG level to 2. When
compiling at this level two files in the storage kit cannot be compiled
due to some compiler error:
C++ ../../../generated/objects/haiku/x86/debug_1/kits/storage/
DiskDeviceList.o
/work/gg/src/i686-beos-branch/gg/be/gnupro/gcc/dwarf2out.c:7659:
Internal compiler error in function scope_die_for
Please submit a full bug report to Be at http://bebugs.be.com.
C++ ../../../generated/objects/haiku/x86/debug_1/kits/storage/
DiskDeviceRoster.o
/work/gg/src/i686-beos-branch/gg/be/gnupro/gcc/dwarf2out.c:7659:
Internal compiler error in function scope_die_for
Please submit a full bug report to Be at http://bebugs.be.com.
This of course caused the build of the registrar and input server to
fail at this debug level (and also at debug level 1.)
OK, so I figured my GCC must be out of date (even though I think it
isn't.) So since I had already downloaded all the build tools from SVN
to build a working Jam, I had the sources for GCC and binutils. So I
tried to follow the directions for building those two tools and
bintutils was fine, but GCC had the following error:
stage1/xgcc -Bstage1/ -B/boot/develop/tools/gnupro/i586-pc-beos/bin/ -
DIN_GCC -O2 -O2 -DHAVE_CONFIG_H -o gencheck \
gencheck.o ` case "obstack.o" in ?*) echo obstack.o ;; esac ` ` case
"alloca.o" in ?*) echo alloca.o ;; esac ` ` case "" in ?*) echo ;;
esac ` ` case "" in ?*) echo ;; esac ` ` case "" in ?*) echo ;; esac
`
/boot/develop/lib/x86/libroot.so: undefined reference to
`memset_internal'
/boot/develop/lib/x86/libroot.so: undefined reference to
`memcpy_internal'
collect2: ld returned 1 exit status
make[2]: *** [gencheck] Error 1
make[2]: Leaving directory `/boot/home/develop/buildtools/legacy/gcc-
obj/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/boot/home/develop/buildtools/legacy/gcc-
obj/gcc'
make: *** [bootstrap] Error 2
So again I'm at a standstill. I don't give up too easily but this is
starting to get really frustrating. In fact here are other BeOS
problems I've been having:
1. No version of Firefox can ever send emails in Gmail. I don't know
why this happens, but it sure is annoying. Can anyone else use the
Gmail web interface in BeOS?
2. So since I use Gmail for this list I had to set it up here in BeOS.
But to do that I had to compile my own Mail Daemon Replacement with SSL
support (thanks to mmadia for his very useful instructions in the
Talkback for the MDR on BeBits.) I can handle this but I don't see how
any average user could.
3. More often than I would like my machine locks up. But it only seems
to be the app_server because if I'm playing music it still plays, but
the display does not update. Anyone have a trick for solving this
problem? Maybe something with SpicyKeys and restarting the app_server?
Also how could I determine the source of this lock-up? I imagine it is
probably the video driver...
4. Damn the net_server is slow and inefficient. I'm not very happy when
downloading a page in FireFox consumes most of my CPU time. Of course I
know this is well known and I may look into Bone. I'm thankful Haiku is
coming up with a better solution for networking.
On a more positive note I finally got the SSL keys sorted out with
berlios.de so I can use SVN without logging in. If anyone else has had
trouble with this, let me know, I can help.
In regards to the other problems: Please help be Obi Wan Kenobi (or
Axel or Stephan or Ingo, etc), you are my only hope,
Ryan
- Follow-Ups:
- [openbeos] Re: Various development problems and BeOS annoyances
- From: Stephan Assmus
- [openbeos] Re: Various development problems and BeOS annoyances
- From: Mathew Schofield
Other related posts:
- » [openbeos] Various development problems and BeOS annoyances
- » [openbeos] Re: Various development problems and BeOS annoyances
- » [openbeos] Re: Various development problems and BeOS annoyances
- » [openbeos] Re: Various development problems and BeOS annoyances
- » [openbeos] Re: Various development problems and BeOS annoyances
- » [openbeos] Re: Various development problems and BeOS annoyances
- » [openbeos] Re: Various development problems and BeOS annoyances
- » [openbeos] Re: Various development problems and BeOS annoyances
- » [openbeos] Re: Various development problems and BeOS annoyances
- [openbeos] Re: Various development problems and BeOS annoyances
- From: Stephan Assmus
- [openbeos] Re: Various development problems and BeOS annoyances
- From: Mathew Schofield