2009/4/21 Marc Weber <[email protected]>: > I'm trying to add autofs to set up automatic mounting mounting of > filesystems. > > However It fails compling with this message: > > m...@nixos: > /tmp/nix-build-6ifmhynnj08p10xf0javh4sa43c6ab8r-autofs-5.0.4.drv-0/autofs-5.0.4/lib > ]$ strace -o /tmp/trace -f > /nix/store/a8922c0h87iilxzzvwn2hmv8x210aqb9-glibc-2.7/bin/rpcgen -h -o > mount.h mount.x > cannot find any C preprocessor (cpp) > > strace reveals: > > 14385 stat("/lib/cpp", 0x7fff55a89700) = -1 ENOENT (No such file or > directory) > 14385 stat("/usr/ccs/lib/cpp", 0x7fff55a89700) = -1 ENOENT (No such file or > directory) > > So is the way to go patching glibc so that rpcgen uses cpp from PATH? > > Sincerly > Marc Weber > _______________________________________________ > nix-dev mailing list > [email protected] > https://mail.cs.uu.nl/mailman/listinfo/nix-dev >
<div><br></div> Hi Marc, I apologize in advance if I'm way off here because I still don't understand the nix expression format in the way that I want to yet but looking at the problem, assuming that you are working with autofs 5, I can see : --with-path=PATH Allows the specification of the path to search for utility binaries used by autofs during the `configure' process. If any of your binaries such as `mount', `mount.cifs' etc. live in locations other than /usr/bin:/bin:/usr/sbin:/sbin you will need to use this option. In the readme and I guess it's configure script just tries to assume lsb file system layout by default. So I guess that the gcc path environment variable (Because cpp is part of gcc) Needs to be passed to --with-path= in a builder? Probably the same goes for anything else like mount that the configure script needs to find. If when you are mentioning patching, do you mean a patch to glibc sources, the expression, it's builder or nix? I'm interested in how this kind of problem is solved using nix because everything is put into the store, it's wrong when configure scripts assume like this but I'm sure that autofs aren't the only srcs that adopt this, basically wrong behavior of path assumption in their configuration scripts but I'm pretty sure it's not a common place. I hope that there is an easy solution, Tony _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
