Remove <malloc.h> from the system.Originally, I wanted to follow FreeBSD which errors if __STDC__ isdefined and silently includes <stdlib.h>, which has the malloc()and friends prototypes, if it i
Remove <malloc.h> from the system.Originally, I wanted to follow FreeBSD which errors if __STDC__ isdefined and silently includes <stdlib.h>, which has the malloc()and friends prototypes, if it is not defined. The only case where__STDC__ isn't defined used to be when -traditional was passed toGCC, which used to attempt an emulation of a pre-standard compiler.But -traditional has since been made a cpp(1) specific option innewer releases of GCC, so it becomes more and more pointless tosupport <malloc.h>, even if we went with FreeBSD's version.Therefore, remove it completely.Also disable its usage in a number of contrib/ software whichexpected it due to its presence at the time when the software wasconfigured.Suggested-by: marino, who also fixed the resultant dports breakage
show more ...
Revert "<malloc.h>: Restrict support for <malloc.h> to !defined(__STDC__)."This reverts commit 1b3342693b737646f3cab0715e31ec6ab5216b38.It caused too many issues in the package department.Repor
Revert "<malloc.h>: Restrict support for <malloc.h> to !defined(__STDC__)."This reverts commit 1b3342693b737646f3cab0715e31ec6ab5216b38.It caused too many issues in the package department.Reported-by: marino
<malloc.h>: Restrict support for <malloc.h> to !defined(__STDC__).In essence this is what FreeBSD did: error if __STDC__ is defined, andsilently include <stdlib.h> if not.Packages are expected t
<malloc.h>: Restrict support for <malloc.h> to !defined(__STDC__).In essence this is what FreeBSD did: error if __STDC__ is defined, andsilently include <stdlib.h> if not.Packages are expected to now fail their config checks for <malloc.h>but to build nevertheless, which was confirmed with building ~500packages as a test.Adjust a few config.h files of contrib/ code as well, notablylibssp's, which gets rid of the malloc.h warnings from the buildworldoutput.
libssp47, libobjc47: install headersHeaders for both libssp and libobjc were not getting installed for thegcc47 library set. As an aside, the gcc44 libobjc is also missing theseheaders. There i
libssp47, libobjc47: install headersHeaders for both libssp and libobjc were not getting installed for thegcc47 library set. As an aside, the gcc44 libobjc is also missing theseheaders. There installation required an mtree change, but it can bebuilt with quickworld.Additionally, CFLAGS were moved to above an include for libobjc whichshould ensure the local config.h is included before a different versionand this in turn likely improves libobjc functionality.
gcc47: Add libssp and libssp_nosharedThese libraries were not part of the gcc 4.4 system compiler set.Some pkgsrc packages assume the ssp libraries come with the compiler,so add them to the gcc 4
gcc47: Add libssp and libssp_nosharedThese libraries were not part of the gcc 4.4 system compiler set.Some pkgsrc packages assume the ssp libraries come with the compiler,so add them to the gcc 4.7 library set.