> cc -fPIE -shared -Wall -Wextra -o alu_bit.o alu_bit.c
All your .c.o rules need to pass the -c command line option to cc.
You compile (only) all the .c files into .o files in the first instance.
Then you link all the objects and libraries to produce the executable.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Ah thank youOriginally Posted by Salem
That got me further (had to re-add the RPATH and finally remembered about adding the -L switch), just missing a function I hadn't realised I hadn't made yet but otherwise nearly able to test the base functions I need for it to be a usable library in mitsy before moving on to making and testing the speed of another function I thought of an optimised way to make (well more optimised than the previous version I made that mitsy currently includes)
