On 3/29/19 6:05 PM, Wayne Blaszczyk wrote:
On Fri, 2019-03-29 at 12:26 -0500, Bruce Dubbs via blfs-dev wrote:
On 3/29/19 12:16 PM, Ryan Marsaw via blfs-dev wrote:
On Fri, 29 Mar 2019, Bruce Dubbs via blfs-dev wrote:
On 3/29/19 6:42 AM, Roger Koehler via blfs-dev wrote:
I am using the Sys V version:
make[1]: Entering directory '/sources/yaml/libyaml-0.2.2'
make[1]: *** No rule to make target 'build'. Stop
You are supposed to be IN directory build.
mkdir build &&
cd build &&
cmake ... &&
make
If you are scripting, note that after extracting, you need to cd to
libyaml-0.2.2 and not yaml-0.2.2.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
The first line of the installation of YAML 0.2.2 reads:
make build &&
cd build &&
That should be "mkdir build && cd build &&"
I believe that's what's causing Rogers's error.
LOL. It is a problem. Fixed in revision 21411.
-- Bruce
Hi Bruce,
You didn't address the second issue that Ryan reported?
I had the same problem where appstream-glib could not find yaml.
The cmake instructions as they are now, do not install the following files:
/usr/lib/libyaml-0.so.2.0.6
/usr/lib/libyaml-0.so.2
/usr/lib/pkgconfig/yaml-0.1.pc
Using autotools fixes the above issue.
Hmm. It does install /usr/lib/libyaml-0.so as a library file, but that
is normally a symlink. It also installs .cmake files so other packages
that that use cmake can find it. I took a look at libblockdev and that
uses pkgconfig to find it, so it wouldn't be found in this case.
I guess we need to revert to autotools.
I've reported the problem upstream.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
