Issue 37 in nsscache: Can't build libnsscache on Centos

40 views
Skip to first unread message

nssc...@googlecode.com

unread,
Sep 29, 2014, 11:40:06 AM9/29/14
to nsscache...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 37 by hughes.m...@gmail.com: Can't build libnsscache on Centos
https://code.google.com/p/nsscache/issues/detail?id=37

What steps will reproduce the problem?
1. Take the latest downloads
2. Follow installation instructions

What is the expected output? What do you see instead?

When I run 'make install' in libnss-cache, I get

[ -d //usr/lib ] || install -d //usr/lib
install .libs/libnss_cache.so.2.0 //usr/lib
install: cannot stat `.libs/libnss_cache.so.2.0': No such file or directory
make: *** [install] Error 1


See Dockerfile and results.txt for all output and exact steps to recreate.

Attachments:
results.txt 28.7 KB
Dockerfile 473 bytes

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

nssc...@googlecode.com

unread,
Oct 20, 2014, 1:15:10 AM10/20/14
to nsscache...@googlegroups.com

Comment #1 on issue 37 by j...@spacepants.org: Can't build libnsscache on
Centos
https://code.google.com/p/nsscache/issues/detail?id=37

thanks for the detailed reproduction information. I've not used docker
before, and your Dockerfile was pretty interesting!

The problem looks like a simple dependency bug in the Makefile. Try 'make
&& make install' first as a workaround.

Also, you'll have permission problems installing to /usr/lib unless you're
running the install as root, so have a look at the Makefile for how to set
an install prefix -- the debian package uses this to build packages.

nssc...@googlecode.com

unread,
Oct 20, 2014, 1:16:10 AM10/20/14
to nsscache...@googlegroups.com
Updates:
Status: Fixed

Comment #2 on issue 37 by j...@spacepants.org: Can't build libnsscache on
Centos
https://code.google.com/p/nsscache/issues/detail?id=37

Fixed in github/master.
Reply all
Reply to author
Forward
0 new messages