From: Marcel Holtmann <marcel@holtmann.org>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: Brian Gix <bgix@codeaurora.org>, linux-bluetooth@vger.kernel.org
Subject: Re: Building master on Debian systems fails at linking "check".
Date: Tue, 15 Nov 2011 11:25:15 +0900 [thread overview]
Message-ID: <1321323919.15441.475.camel@aeonflux> (raw)
In-Reply-To: <20111114225100.c75e709827f4b22fa83e0327@studenti.unina.it>
Hi Antonio,
> > > The workaround I use for now is:
> > > - run "make" and let the build system fail
> > > - show the failing command with "make V=1"
> > > - change -lcheck to -lcheck_pic and rerun the command
> > > - "make" will now proceed with the build
> >
> >
> > This same solution works for me: After running ./bootstrap-configure, I
> > change the unit_test_eir_LDADD line in the Makefile to:
> >
> > unit_test_eir_LDADD = lib/libbluetooth-private.la -lglib-2.0 -lcheck_pic
> >
>
> Eh Brian, this is surely a little prettier than what I am doing :)
>
> > There is probably a way to make this happen automatically, but I don't
> > know enough about the configure mechanism to know how to do this.
> >
>
> I think using a “libcheck_pic aware” m4 macro is the way to go, ideally
> this should be provided in the check package itself, I'll try asking the
> Debian maintainers if there is no interest for a solution in BlueZ.
why on earth does Debian has to do everything different than any other
distribution. I am getting pretty sick of that :(
The easiest way is to just disable any kind of unit testing when the
check support is not found. Simple as that. I am not bothering to make
this work on Debian.
Regards
Marcel
next prev parent reply other threads:[~2011-11-15 2:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 14:56 Building master on Debian systems fails at linking "check" Antonio Ospite
2011-11-14 18:12 ` Brian Gix
2011-11-14 21:51 ` Antonio Ospite
2011-11-15 2:25 ` Marcel Holtmann [this message]
2011-11-15 2:31 ` Brian Gix
2011-11-15 2:53 ` Marcel Holtmann
2011-11-15 2:58 ` Brian Gix
2011-11-15 2:59 ` Marcel Holtmann
2011-11-18 9:37 ` Antonio Ospite
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1321323919.15441.475.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bgix@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ospite@studenti.unina.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox