How to Write Portable C Without Complicating Your Build

Re:How to Write Portable C Without Complicating Your Build by derefr on Friday March 31, 2017 @03:07PM (#14007089)

The usual reason to separate them is that if you're installing to a prefix that needs root privileges to write to, then you'll be doing something like:

    ./configure && make && sudo make install

If you do this instead:

    ./configure && sudo make install

...then the compiler toolchain gets invoked as root and all the intermediate build products end up owned by root.

[ Parent | on HN ]

Re:How to Write Portable C Without Complicating Your Build by xtreme on Saturday April 01, 2017 @02:29AM (#14010841)

There is another reason. `make -j4 && make install' would be faster than just `make install' (multi-process vs. single-process).

[ Parent | on HN ]

Re:How to Write Portable C Without Complicating Your Build by atso on Saturday April 01, 2017 @07:05AM (#14011550)

You can do `make -j4 install`. Works as intended.

[ Parent | on HN ]