Also some style cleanup.
Note that defining an empty-string variable *does* change the hash.
I would like to change this behaviour one day
(clean up attrs when compiling the derivation).
From https://lists.macosforge.org/pipermail/macports-dev/2011-July/015263.html:
5) Building with a compiler that doesn't support newer __builtins
If your port uses MacPorts compilers rather than the default compiler,
you may run into trouble with string functions. You'll see errors at
link time about undefined __builtin_* functions. If this happens, you
may want to compile with -D_FORTIFY_SOURCE=0 to tell the headers to
use unfortified versions which do not use compiler builtins.
This also fixes the annoying issue that minicom doesn't work out of the
box:
$ minicom
minicom: there is no global configuration file /etc/minirc.dfl
Ask your sysadmin to create one (with minicom -s).
$ sudo minicom -s
minicom: there is no global configuration file /etc/minirc.dfl
Ask your sysadmin to create one (with minicom -s).
minicom 2.4 basically refuses to enter setup unless /etc/minirc.dfl
already exists. sudo touch /etc/minirc.dfl is enough to fix that though,
but with this commit "sudo minicom -s" will work out of the box.
This is in order to prepare for fetching the build output from the corresponding
target machine to even further speed up deployment.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This should prevent some annoying messages such as:
tar: usr/bin/nix-build: time stamp 2013-07-09 07:45:19 is 0.159248271 s in the f
uture
tar: usr/bin/nix-channel: time stamp 2013-07-09 07:45:19 is 0.159088763 s in the
future
tar: usr/bin/nix-collect-garbage: time stamp 2013-07-09 07:45:19 is 0.15901664 s
in the future
tar: usr/bin/nix-copy-closure: time stamp 2013-07-09 07:45:19 is 0.158948028 s i
n the future
tar: usr/bin/nix-daemon: time stamp 2013-07-09 07:45:19 is 0.158888042 s in the
future
Signed-off-by: aszlig <aszlig@redmoonstudios.org>