You are not logged in.
Pages: 1
I'm playing around with makeworld and I'm not having much luck with it. The command I'm using is
makeworld -ic /usr base
It looks like the make is working ok, although it's hard to say for sure. But when it comes down to the make install I see some errors.
find: pkg//lib: No such file or directory
find: pkg/usr/lib: No such file or directory
and lots of others. Then
mv: invalid option -- c
Try 'mv --help' for more information.
Am I doing something wrong or is the script?
Thanks
Offline
the script doesn't support getopt-style options. Try makeworld -c -i /usr base
Offline
What does makeworld do?
Markku
Offline
makeworld can be used to rebuild an entire package group, or the entire build tree.
Offline
Yes, I've tried -c -i and --clean --install as well, the results are the same. The problem, after further digging, appears to be with the strip portion of makepkg, not makeworld. Everything is still compiling and installing properly, but the errors are occuring when makepkg attempts to call strip, before building the archive.
Offline
For me, it is a normal behavior.
The last step of makepkg, before creating the tar.gz file, is to strip files from the package:
msg "==> Stripping debugging symbols from libraries..."
find pkg/{,usr,usr/local}/lib -type f -exec /usr/bin/strip --strip-debug '{}' ';' 2>&1
msg "==> Stripping symbols from binaries..."
find pkg/{,usr,usr/local}/{bin,sbin} -type f -exec /usr/bin/strip '{}' ';' 2>&1
It seems the package you try to build does not contains /lib and /usr/lib directories.
So this is perhaps why "find" returns such messages:
find: pkg//lib: No such file or directory
find: pkg/usr/lib: No such file or directory
In this case, these are just warnings, and you should just don't care about them.
I also get lots of these warnings each time i build a package...
Maybe a next release of makepkg could test if directories are existing before trying to strip files in it?
Offline
Yes, that makes sense. Thanks
Offline
Pages: 1