Notice how libgnuradio-core.so points off to nothingness
Now, gnuradio-based applications seem to be just fine with this, after
running ldconfig.
But, for example, if you pull something, like gr-stream-tags off of
CGRAN, and try to build the result, it
will barf on a linker error, due to not being able to resolve
“-lgnuradio-core” (and others).
So the question is, where is cmake getting its notion of how to name
these things, and set up the
symlink hierarchy? If it comes from the “.pc” files, I’ll note that
they haven’t been updated since
I last ran an autotools build, 5 days ago. Does cmake update the
“.pc” files? How is this
dangling symlink problem happening?
–
Principal Investigator
Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org
So the question is, where is cmake getting its notion of how to name
these things, and set up the
symlink hierarchy? If it comes from the “.pc” files, I’ll note that
they haven’t been updated since
I last ran an autotools build, 5 days ago. Does cmake update the
“.pc” files? How is this
dangling symlink problem happening?
It’s a Fedora-12 32-bit machine. With cmake-2.6.4-5.fc12.i686
Thats an old fedora
That could be the issue, yes. But I’m not a Cmake guy at all.
This is part of our special LIBRARY_EXTRAS mode. You can disable it with
-DLIBRARY_EXTRAS=OFF just so you know, but I think the following patch
will solve the issue…
So, it like cmake 2.6 doesnt have LIBRARY_OUTPUT_NAME, but it does have
OUTPUT_NAME. They are both ways to rename the target, one being specific
to a library and only possible with 2.8 and up. Try this patch: http://pastebin.com/kXKgJPF7
-josh
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.