This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: [PATCH] RDOS support for newlib
1. Files from the top-level directory require special approval since
these files are shared with other projects. See the
top-level MAINTAINERS file for details on which mailing
lists to send various patches to.
The patch to libtool.m4 is approved and applied to libtool-project.
However, the CVS-version of libtool.m4 is not identical to the
GCC / newlib version. Configure is generated and the configure.in
patch is required to build newlib-directory for target RDOS.
2. You have patches to generated files (configure, aclocal.m4).
You must only provide patches for the files that generate these and
do not post the generated diffs.
OK, I'll omit those.
3. You make libtool changes. Do you intend on using libtool to
build rdos under newlib? There is more involved in this.
No, but without these patches newlib and libstdc++-v3 will
not build correctly.
Note the code below that only allows libtool for x86-linux:
case "${host}" in
i[34567]86-pc-linux-*)
use_libtool=yes
have_sys_mach_dir=yes
stdio64_dir=stdio64
oext=lo
aext=la ;;
*) ;; #shared library not supported for ${host}
esac
I'm not using libtool for dynamic linking.
4. You must submit the initial patch for your new files. You may
request to be the maintainer of said files once they are
approved and to check-in patches without prior permission, but
that right is never given to anyone sight-unseen and may
require a few patches to build up a trust factor.
OK, I'll repost and include all files in rdos-directory as well.
Leif Ekblad
www.rdos.net/rdos