musl - musl - an implementation of the standard library for Linux-based systems

Age	Commit message (Collapse)	Author	Lines
2018-08-02	fix musl-gcc wrapper to be compatible with default-pie gcc toolchains	Rich Felker	-2/+2
	the specfile for the wrapper was written assuming output is pie only if -pie appears on the command line. recent (and older patched) versions of gcc can be configured to produce pie output by default, adn when used with such a toolchain, the wrapper linked the wrong startfiles (crt*) containing pic-incompatible code. rather than trying to figure out gcc's default, simply always use the pic-compatible start files.
2013-06-07	fix mixup in previous change to gcc wrapper	Rich Felker	-1/+1

2013-06-07	make gcc-specific headers (intrinsics, etc.) available with wrapper	Rich Felker	-2/+2
	they are intentionally listed after the libc include directory so that the gcc float.h, etc. don't get used in place of the libc ones.
2012-07-23	gcc wrapper improvement: leave libgcc dir in the library path	Rich Felker	-1/+1
	this is needed in case -lgcc is passed explicitly on the link command line, for example if the wrapper is being used to build musl itself.
2012-06-06	make gcc wrapper rewrite link options rather than just extending them	Rich Felker	-3/+1
	this is not tested yet, but should work to get rid of unwanted --hash-style=gnu hacks present in some distro-patched gcc versions.
2012-05-30	fix musl-gcc wrapper to work with -pie	Rich Felker	-1/+1
	linking the wrong crt1.o resulted in textrels and thus crashing
2012-04-22	new gcc wrapper, entirely specfile based	Rich Felker	-0/+39
	the _concept_ of this wrapper has been tested extensively, but the integration with the build/install system, and using a persistent specfile rather than one generated at build-time, have not been heavily tested and may need minor tweaks. this approach should be a lot more robust (and easier to improve) than writing a shell script that's responsible for trying to mimic gcc's logic about whether it's compiling or linking, building shared libs or executable files, etc. it's also lighter weight and should result in mildly faster builds when using the wrapper.