On 15/10/12 22:00, Chris Staub wrote:
On 10/15/2012 04:44 PM, William Harrington wrote:
Hello CLFS community,
We have an issue that needs to be addressed.
Util-linux used to provide su, which we used when testing coreutils.
We've always installed and used shadow's su, and shadow is installed
after coreutils, and we can't use that su as of right now, unless we
test coreutils after installing shadow.
I was thinking, maybe when building coreutils, add to the instructions
to extract shadow's su src file and build it to use for the test suite
phase of coreutils. I haven' t tested this, and I'm coming up with ideas
on a whim.
I tried that, but you'd really be better off configuring and compiling
all of Shadow - as su would need various other headers and stuff - and
cp'ing the su binary. Though, even when I tried installing all of
Shadow into /tools, it still failed - according to message on the LFS
mailing lists, it seems to require /etc/login.defs - just having
/tools/etc/login.defs doesn't work, even when --prefix=/tools, though
of course that might be fixed by editing the source somehow.
I agree
I symlinked that and login.access, as i install everything in tools,
only symlinks in the final system, which get overwritten as and when
We can move shadow before coreutils. I'm not sure how much of the final
system it needs before being built. I think one time I did build shadow
before coreutils and didn't see anyting weird, but really all we need is
su at that point.
Yeah, that should work.
Any input is greatly appreciated.
Sincerely,
William Harrington
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
regards
Martin
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
