[PATCH] top level configure.in (kaOS)

Uwe Stieber uwe@wwws.de
Tue Feb 4 09:39:00 GMT 2003


Hi,

> Your ChangeLog entries are missing periods at the end of each sentence,
> and your name should be two spaces (not a tab) after the date.

Ok, I can change this. It looked for me like a TAB.

> You probably want target-libiberty in noconfigdirs like all the other
> targets.  Do you really not support libiberty?

If I'm not wrong, putting target-libiberty within noconfigdirs leads to
a "loud" remove, means you get an message during configure. I do not
like to see that message, because this looks like, as something is going
wrong. That's why I put target-libiberty within the skipdirs.

And the support of libiberty: Well, libiberty is a fantastic OS
abstraction library. I really do like nice libraries, but libiberty does
not fit to the target OS. I short words, libiberty is to complete and to
POSIX for the target. If we do support libiberty, we had to made an
almost POSIX compliant C-API available, but this is exactly what we do
not want. The only available API to application programmes should be an
C++ API. We do know that this is quite exceptional, but this is exactly
the fun to do.

> This patch also needs to be sent to gcc-patches@gcc.gnu.org as it has
> changes that affect gcc, and the toplevel files are kept in sync
> between gcc and src.

Ok. I put gcc-patches as well within the recipient list.

Thanks in advance, 
Best regards,
Uwe Stieber
mailto: uwe@wwws.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: top_level_configure_patch_4kaOS.tgz
Type: application/x-gzip
Size: 822 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20030204/4f54a563/attachment.bin>


More information about the Gdb-patches mailing list