Hi Alex, (01)
I'm hoping that we can suggest something that will be ok by Ken, since
he is the maintainer of klh10. I understand his point that he doesn't
want to change code purely due to a gcc compiler bug. I am also hoping
that we can find a way to make it more convenient to compile klh10 on
the current version of gcc until the bug gets fixed. (02)
I am also hoping you will hear back from your vendor, as the best
solution of course would be just for gcc to get fixed. (03)
We have now opened up the NLS Restoration wiki page (and mail archives): (04)
http://chm.cim3.net/cgi-bin/wiki.pl?NLS_Restoration
http://chm.cim3.net/forum/ (05)
We have a lot of work to do to organize content and put a lot more
content on the wiki. It is pretty sparse right now, but that will come
over time. (06)
In the meantime, I have started putting a list of things that we need
help with on the wiki:
http://chm.cim3.net/cgi-bin/wiki.pl?NlsTechnical/NeedHelp (07)
Feel free to look over what's on there and see if anything else grabs
your interest! (08)
Thanks for your help so far. (09)
Jonathan (010)
Alex Bochannek wrote:
> I haven't seen anything else with regards to the GCC 4.1.1 patches, so
> I assume you are OK with it. We have sent the bug report about the
> register variable to our compiler support vendor, but haven't heard
> back yet. Let me know what else I can help with.
>
> Alex. (011)
_________________________________________________________________
Message Archives: http://chm.cim3.net/forum/nls-technical/
Shared Files: http://chm.cim3.net/file/work/project/nls-restore/
Community Portal: http://www.computerhistory.org/
To Post: mailto:nls-technical@chm.cim3.net
Community Wiki: http://chm.cim3.net/cgi-bin/wiki.pl?NLS_Restoration (012)
|