GitLab

Spotted by Dominic Steinitz

As the .o files will not exist.

It's even atomic on windows so we don't need the workaround.

Rather than taking a specific dir to create.
Update the one use of the function.

Also clean up imports

The check should now be accurate enough that we can make it an
error rather than just a warning.

In partiular this is needed for packages that use ./configure
scripts to write .buildinfo files since they typically do not
split the cpp/cc/ldoptions into the more specific fields.

This lets us pick up build info discovered by the ./configure script

Optimize for succesful case. First try all libs and includes in one command, 
proceed with further tests only if the first test fails. The same goes for libs 
and headers: look for an offending one only when overall test fails.

Also use simplified implementation in terms of recently added functions.

All remaining uses of it do not require copying permissions

instead of get/setPermissions which don't really work properly.

Instead if copyDirectoryRecursiveVerbose use installDirectoryContents
and for smartCopySources use findModuleFiles and installExecutableFiles
In both cases the point is so that we use functions for installing
files rather than functions to copy files.

instead of copyFileVerbose

We want to separate the functions that do ordinary file copies
from the functions that install files because in the latter
case we have to do funky things with file permissions.

This lets us get rid of the Compat.Permissions module

This is just a basic check - generate a sample program and check if it compiles and links with relevant flags. Error messages (warning messages, 
actually) could use some improvement.

This is to work around the file permissions problems with the
standard System.Directory.copyFile function. When installing
files we do not want to copy permissions or attributes from the
source files. On unix we want to use specific permissions and
on windows we want to inherit default permissions. On unix:
copyOrdinaryFile   sets the permissions to -rw-r--r--
copyExecutableFile sets the permissions to -rwxr-xr-x

No idea why this was ever added, they've never been built.

It's totally unnecessary and messes up profiling in older ghc versions.

fdToHandle calls fdGetMode which does not work with ghc-6.6 on
windows, the workaround is not to call fdToHandle, but call
openFd directly. Bug reported by Alistair Bayley, ticket #473.

Fixes #317. Based on a patch by gleb.alexeev@gmail.com

Previously for 'install-includes: subdir/blah.h' we would not
create the subdir in the target location.