Repository navigation
/etc/ld.so.cache regeneration #5217
Description
With source based package manager I do run regenerating /etc/ld.so.cache everytime I compile new package to system.
After make & make install rust I'm getting below messages there:
/sbin/ldconfig: File /usr/local/lib/librusti.so is empty, not checked.same about librustc.so , librust.so and other
To be honest I don't like it but what does it mean? How can I resolve this?
by the way I'm not sure if local is correct place for installed by package manager package so maybe I need to move package manually after make install?
Activity
brson commentedon Mar 5, 2013
The problem is that
librusti.sois just a 0-byte placeholder file used by the build system to manage dependencies. Rust libraries have names likelibrusti-[hex]-[vers].so, and the hex string in the middle is not a stable identifier, so we use the names without all the gunk just somakecan identify the dependencies.We should not be installing these files. One thing we could do to solve this easily might be to name these something like
librusti.so.dummy(this is what servo does).These files have caused confusion before.
Cynede commentedon Mar 5, 2013
User confusion is better then my build system confusion though. Maybe it's really better to not install those files?
And what about installing to
local?brson commentedon Mar 6, 2013
Yes, I agree they should not be installed (see #4486 for a little more on this subject).
Your package probably shouldn't install to
/usr/localand instead install to/usr(I imagine, depends on your package manager). To do this you'll want to use the--prefix=/usrflag toconfigure, and not just copy the files. There are some behaviors related to library loading that base their paths on the configured prefix, so things could break in subtle ways if you simply copy the installed files to a different location.Cynede commentedon Mar 6, 2013
Thank you. May I rename them myself to *.dummy ?
brson commentedon Mar 6, 2013
Yes, absolutely you may, though I'm not sure exactly what you intend. I think the proper way to do this is to modify this bit of the makefiles that controls library naming. That
CFG_LIB_NAMEmacro produces the name of a library as appropriate for the target architecture, e.g.librust.so. Adding.dummyto those definitions (except forCFG_RUNTIMEandCFG_RUSTLLVM, which are native libraries, not Rust crates) will probably do what we want. Additionally the rules formake cleaninmk/clean.mkwill need to be changed to account for the new extension.Cynede commentedon Mar 11, 2013
rename is wrong solution...
Cynede commentedon Mar 11, 2013
What about removing them after installation?
brson commentedon Mar 11, 2013
The intent of renaming them during the build is that the install script will then not install them (since it doesn't, or shouldn't, install
*.dummyfiles). If you want to avoid hacking the makefiles then yes, deleting them should be fine.Cynede commentedon Mar 12, 2013
Fine. Here is the ebuild (gentoo build script) then https://github.com/Cynede/gentoo-rust/blob/master/dev-lang/rust/rust-9999.ebuild
So I close this question because it's solved for myself even in hacky way.
Reopen if you prefer to keep it open to solve it in makefile.
fix(rustfmt): fix struct field formatting with doc comments present (r…
Merge pull request rust-lang#5217 from moabo3li/local-value-bytes-han…
Merge rust-lang#5414