Subject: Re: Still toolchain mysteries
To: None <martin@duskware.de, port-sparc64@NetBSD.ORG>
From: None <eeh@netbsd.org>
List: port-sparc64
Date: 10/27/2000 15:01:23
So, now that there is a working toolchain on the ftp site I could rebuild
the world and nearly everything works (awk being the notable exception).
What I still can not do is: rebuild a working toolchain from source. That is
exspecially painfull as mycroft modified something in the configurtion to
make Mozilla work (not on sparc64 yet, but coming closer).
I don't know how the toolchain in the snapshot is build, but I'm quite
positively sure it is *not* from the same sources that are in -current
right now.
What's up?
The toolchain is generated from the -current sources. The only
modification from what you see in-tree is:
Index: include/libiberty.h
===================================================================
RCS file: /cvsroot/gnusrc/gnu/dist/toolchain/include/libiberty.h,v
retrieving revision 1.2
diff -c -u -r1.2 libiberty.h
cvs server: conflicting specifications of output style
--- include/libiberty.h 2000/08/10 13:52:05 1.2
+++ include/libiberty.h 2000/10/27 14:57:33
@@ -190,8 +190,10 @@
/* Like vsprintf but provides a pointer to malloc'd storage, which
must be freed by the caller. */
+#if 0
extern int vasprintf PARAMS ((char **, const char *, va_list))
ATTRIBUTE_PRINTF(2,0);
+#endif
#ifdef __cplusplus
}
Everything else is exactly what you get from the -current tree.
Eduardo