(/usr/include, /usr/local/include, etc.).
* Immediate pay-off: we see that the glibc header files depend on the Linux
kernel header files. So I've added a package that extracts the appropriate
headers from Linux 2.4.22.
svn path=/nixpkgs/trunk/; revision=361
directories for libraries. (Fortunately, the build would still fail because
Perl's idea of "standard" library directories no longer matched that of the
linker.)
* `stdenv-linux/setup.sh' now puts the path of glibc in an environment
variable so that it can be used by other packages (for example, we need to
pass it to Perl's configure, because otherwise it will think that, e.g.,
libm.so doesn't exist).
svn path=/nixpkgs/trunk/; revision=359
(/lib, ...). So unless a directory is explicitly added using `-L' it won't we
searched. This has already revealed that libxml has a hidden dependance on libz.
svn path=/nixpkgs/trunk/; revision=357
getopt has been added.
As part of the build of sdf2 we patch sdf2table to store the full path of
getopt. This is so that packages that use sdf2 do not have to declare
getopt as an input.
svn path=/nixpkgs/trunk/; revision=347
TODO: clean up the Perl build. Currently it's still using some external
libraries, and it doesn't pass all its unit tests.
svn path=/nixpkgs/trunk/; revision=326
Note that I added bzip2 to stdenv, but not unzip. This raises an interesting
point: what packages should be in stdenv?
svn path=/nixpkgs/trunk/; revision=320
with the standard untar; bootstrap; configure; make; make install
interface. The script is parameterized with arguments for
configure. That is, all arguments are passed verbatim to
configure.
* asfix-tools, gpp, sc, srts, stratego-front, xtc: Fix expressions
and (trivial) build script for basic strategoxt packages. All
packages are abstracted on subversion revision.
svn path=/nixpkgs/trunk/; revision=319
where we don't use any tools from outside the Nix environment. For this we
need the basic POSIX utilities (e.g., GNU coreutils), a shell, GCC, and the
binutils.
Normal packages just need to include stdenv/stdenv.fix, which on Linux will
use the Nixified environment. However, for the tools in the build
environment itself we have a bootstrapping problem. Therefore, these depend
on the external environment (and include stdenv-linux/stdenv-nativetools).
The package `baseenv' provides some generic setup and GCC wrappers used by
both fully Nixified and native environments.
svn path=/nixpkgs/trunk/; revision=305
source from Subversion, runs autoreconf and configure, and does a `make
dist'.
The revision number is currently hard-coded into `nix-dist.fix'.
svn path=/nixpkgs/trunk/; revision=302
against the right dynamic libraries. set-env.sh add the right linker flags to the
NIX_LDFLAGS environment variable, which is passed by gcc-wrapper to the linker.
(In many cases these flags could just be passed through LDFLAGS to configure
scripts; however, in many other cases this doesn't work properly.)
--This line, and those below, will be ignored--
M pkgs/atk/atk-build.sh
M pkgs/glibc/glibc-build.sh
M pkgs/expat/expat-build.sh
M pkgs/freetype/freetype-build.sh
M pkgs/system/populate-linkdirs.pl
M pkgs/sdf2/sdf2-build.sh
M pkgs/pspell/pspell-build.sh
M pkgs/subversion/subversion-build.sh
M pkgs/helpers/set-env.sh
M pkgs/pango/pango-build.sh
M pkgs/strategoxt/strategoxt-build.sh
M pkgs/aterm/aterm-build.sh
M pkgs/libxml2/libxml2-build.sh
M pkgs/glib-1/glib-build.sh
M pkgs/glib/glib-build.sh
M pkgs/pan/pan.fix
M pkgs/pan/pan-build.sh
M pkgs/libxslt/libxslt-build.sh
M pkgs/httpd/httpd-build.sh
M pkgs/openssl/openssl-build.sh
M pkgs/gtkspell/gtkspell-build.sh
M pkgs/fontconfig/fontconfig.fix
M pkgs/fontconfig/fontconfig-build.sh
M pkgs/gnet/gnet-build.sh
M pkgs/gtk+-1/gtk+-build.sh
M pkgs/gtk+/gtk+-build.sh
M pkgs/stdenv/gcc-wrapper.sh
M pkgs/stdenv/stdenv-build.sh
M pkgs/db4/db4-build.sh
M pkgs/db4/db4.fix
M pkgs/MPlayer/MPlayer-build.sh
M pkgs/swig/swig-build.sh
svn path=/nixpkgs/trunk/; revision=213
* Disabled gtkspell support in pan since it (and it alone) has a conflict with the
system glibc.
* Use CPU detection in MPlayer so that it also works on systems with different CPUs
than the build system's.
svn path=/nixpkgs/trunk/; revision=206
the build and execution environment.
This is very useful. For example, it allows packages built on a SuSE
8.2 system to run on a SuSE 8.1 system (this is because 8.2 has a newer
glibc; packages built against it cannot be dynamically linked against
older glibcs).
Of course, Fix packages should not directly import glibc since that is
very system-specific. Rather, they should import stdenv/stdenv.fix and
in their build scripts source in $stdenv/setup, which will setup the
right environment variables. The idea is that stdenv.fix provides the
basic C/Unix build environment (C compiler, POSIX utilities, etc.).
Note that only the ATerm package currently uses this.
svn path=/nixpkgs/trunk/; revision=203
