Hi BV,
Responding to your second question, I do not think it can compile without -lrt
Looking at the man page of mq_getattr: http://linux.die.net/man/3/mq_getattr
================================
Name
mq_getattr, mq_setattr - get/set message queue attributes
Synopsis
#include <mqueue.h>
int mq_getattr(mqd_t mqdes, struct mq_attr *attr);
int mq_setattr(mqd_t mqdes, struct mq_attr *newattr,
struct mq_attr *oldattr);
Link with -lrt.
==============================
Also the error pasted clearly showed that the linking went wrong.
Thanks,
Reinoud.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of bvl
Sent: Saturday, June 01, 2013 3:17 AM
To: [email protected]
Subject: [Clfs-support] gcc-4.8.0 clfs udev questions
Greetings
I in a quandry as to the best 'version' of udev for updated clfs setups with
gcc-4.8.x, eglibc-2.17, linux-3.8+. The clfs book is still based on the ageing
udev-182.
Yesterday I explained that udev-182 does not build against glibc-2.17. I also
explained that a forked udev named eudev
( https://github.com/gentoo/eudev ) does. In the meantime there were clfs-
mailing-list responses from clfs-contributers "Koornstra, Reinoud" and Martin
Ward suggesting the LDFLAGS="$LDFLAGS -lrt" switch may be used to build
udev-182 against eglibc-2.17.
I beleive that eudev might be a better route as it is taken from current
systemd ( so equivalent to ~udev-202 ) but unsure of any pitfalls viv a vis
bootscript compatibility. So I have 2 questions:-
--1. Has anyone else tried eudev and is it compatible with clfs-bootscripts ?
--2. Has anyone tried compiling udev-182 with eglibc-2.17 installed and using
the LDFLAGS="$LDFLAGS -lrt" switch ?
thanks in advnce
sincerely
bv
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
