discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Installing under /usr


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Installing under /usr
Date: Sun, 3 Apr 2011 22:15:28 -0400

On Sun, Apr 3, 2011 at 8:38 PM, Marcus D. Leech <address@hidden> wrote:
I have a client/customer who has a machine where /usr/local isn't writable (it's a network mount point), but the local disk
 infrastructure is writeable by local root.

I've tried doing an install of Gnu Radio using:

./configure --prefix=/usr --exec-prefix=/usr

Then:

make

sudo make install

The install fails inside libtool for libgnuradio-core due to a "permission denied" error:

test -z "/usr/lib" || /bin/mkdir -p "/usr/lib"
 /bin/sh ../../../libtool   --mode=install /usr/bin/install -c   libgnuradio-core.la '/usr/lib'
libtool: install: warning: relinking `libgnuradio-core.la'
libtool: install: (cd /home/radiolab/gnuradio/gnuradio-core/src/lib; /bin/sh /home/radiolab/gnuradio/libtool  --tag CXX --mode=relink g++ -g -O2 -Wall -Woverloaded-virtual -pthread -version-info 0:0:0 -release 3.4.0git -o libgnuradio-core.la -rpath /usr/lib bug_work_around_6.lo filter/libfilter.la g72x/libccitt.la viterbi/libviterbi.la general/libgeneral.la gengen/libgengen.la io/libio.la missing/libmissing.la reed-solomon/librs.la runtime/libruntime.la hier/libhier.la /home/radiolab/gnuradio/gruel/src/lib/libgruel.la -lfftw3f -lm -lgsl -lgslcblas -lm -lgslcblas )
mv: cannot move `libgnuradio-core-3.4.0git.so.0.0.0' to `libgnuradio-core-3.4.0git.so.0.0.0U': Permission denied
libtool: install: error: relink `libgnuradio-core.la' with the above command before installing it


Any hints about how to make it all install nicely under /usr ?

--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org


I hope this doesn't sound patronizing, but are you sure /usr (and /usr/lib) are writable? Can you do a "sudo touch /usr/local/testme"? From the error, it really does look like a simple permission problem.

Tom


reply via email to

[Prev in Thread] Current Thread [Next in Thread]