On Sun, 23 Dec 2018, spiky0011 via blfs-dev wrote:


On 23/12/2018 14:44, Ryan Marsaw via blfs-dev wrote:
On Sun, 23 Dec 2018, spiky0011 via blfs-dev wrote:


I think this Package needs looking at. It requires cmake to build, but cmake
requires it as a dep?

The configure needs to be changed back to

sh autogen.sh && ./configure --prefix=/usr --disable-static && make

make install




Technically, system libuv is not required to build CMake.  I don't use
libuv for any BLFS packages.  Here's my CMake bootstrap line:

./bootstrap --prefix=/usr        \
            --system-libs        \
            --mandir=/share/man  \
            --no-system-jsoncpp  \
            --no-system-librhash \
            --docdir=/share/doc/cmake-3.13.2 \
            -- -DCMAKE_USE_SYSTEM_LIBRARY_LIBUV=false

That last part (-- -DCMAKE_...) allows the built-in version of libuv to
be used, instead of the system one.  However, the BLFS philosophy, as I
take it, is to build system versions of libraries whenever possible, in
order to address issues of security that may not have been addressed in
the in-tree versions of packages.

I agree though that if system libuv is a *required* dependency then
there is a circular dependency which should be addressed...

Happy Holidays,

   -- Ryan

Then the configure script for cmake needs to have that added to it, or change the script  for "libuv".

The other issue is, is the LIBUV with cmake upto date?

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


According to cmake-3.13.2/Utilities/cmlibuv/include/uv-version.h:

#define UV_VERSION_MAJOR 1
#define UV_VERSION_MINOR 20
#define UV_VERSION_PATCH 3
#define UV_VERSION_IS_RELEASE 0
#define UV_VERSION_SUFFIX "dev"

So it looks like they're using 1.20.3, and by the looks of it, a
development version at that.

   -- Ryan
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to