I am building libselinux on openwrt, and need auditing support.
But I have really open the aduditing support in the linux kernel menuconfig, why still this error happen?
error: libaudit.h: No such file or directory.
Any sort of help is greatly appreciated, thanks.
Related
I am working with the exiv2 library. I currently faced an issue, and i can't find my way out of it. Here is the issue.
I installed the exiv2 library. When I try to run it, the following error is given.
exiv2: error while loading the shared libraries: libexiv2.so.26: cannot open shared object file: No such file or directory
But, when i open the /usr/local/lib folder, it exists there. Again when I try to locate the library using the ldd command, the command cannot locate it!
Can anyone help me to find what is going on there? Thanks in advance!
If not how to uninstall the whole library and reinstall it?
I had a similar problem when using the sources for installing.
You can remove the built files with sudo make uninstall from inside the sources folder of exiv2.
The solution to my problem was to simply use the package from the Ubuntu repository: sudo apt install exiv2 libexiv2-dev.
Hopefully this will help you too.
this is an error i got when i run radius server in debugging mode radiusd -X.
i checked a lot and i unable to get the logic,why it is really happend.
root#amsys-ThinkPad-R61:/home/amsys/freeradius-server-2.2.5# radiusd -X
radiusd: error while loading shared libraries: libfreeradius-radius-020205.so: cannot open shared object file: No such file or directory
when i prefectly installed radius server,why i got this problem??
if anyone would aware about this, kindly give prompt response to me ,that how to get out this error.you are really appreciable.
You probably moved the libraries after installation, and your linker path didn't include the location where you moved them to. Use ldd -v <path to radiusd> to show where the linker assumed the libraries were going to be located.
Love vagrant on OSX - just trying on windows 7, but I get this error:
VBoxManage.exe: error: Shared folder named '/vagrant' already exists
Can't find any reference to it in google searches. It seems like some default shared folder is being created - to be honest I don't need a shared folder, but can't immediately work out how to disable it.
I'm using vagrant 1.2.7
Anyone else had this? Any ideas how to fix?
p.s. crossposting here: https://github.com/mitchellh/vagrant/issues/2199 am I a bad person?
I would suggest that you use most up-to-date version of each software(Vagrant and VirtualBox). I had some similar problem; I got them solved after upgrading my VirtualBox. I think this may help someone.
when I am doing ./configure in opensolaris in an attempt to install software. I've got the following error:
error:C compiler cannot create executables
Then I check up on the net and find its due to a missing module call gcc-lib6-dev. But how can I install it?
Sounds like you found an answer for a completely different OS that doesn't apply to opensolaris (lib6 sounds like an old Linux release). Look in the generated config.log
for more detailed error messages that give better information as to the actual problem.
I am writing a small program using openGl and SDL. I need to use SVL for various reasons but I cannot get it to link up properly in Xcode. Has anyone done this before and could talk me through it? I followed the readme from SVL and get the following when I run make install:
ip-156-133:svl-1.5 2 Tom$ sudo make install
installing into /usr/local/include/svl /usr/local/doc
done.
installing into /usr/local/lib /usr/local/include
chmod: lib/*: No such file or directory
make: [install-libs] Error 1 (ignored)
cp: lib/*: No such file or directory
make: [install-libs] Error 1 (ignored)
done.
Could be this be part of the problem?
Also I'm not sure where to add the -lsvl flag and -lsvl.dbg etc.
Any help would be greatly appreciated.
Thanks
SVL seems rather unmaintained, given that the latest version is nearly eight years old.
I'd recommend Eigen, which is under active development and has the added benefit of being a header-only library.