Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Brian Gix <bgix@codeaurora.org>
Cc: Antonio Ospite <ospite@studenti.unina.it>,
	linux-bluetooth@vger.kernel.org
Subject: Re: Building master on Debian systems fails at linking "check".
Date: Tue, 15 Nov 2011 11:53:27 +0900	[thread overview]
Message-ID: <1321325610.15441.479.camel@aeonflux> (raw)
In-Reply-To: <4EC1CEEB.2000702@codeaurora.org>

Hi Brian,

> >> 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.
> 
> This is *not* a Debian issue, as it also happens on Ubuntu.

actually Ubuntu just copies from Debian. So they are both the same and
make the same mistakes.

> I believe it is more likely an X86-64 issue.  And support for libcheck 
> is checked (and is there), but for some reason fails in this instance.

So what does "pkg-config --libs check" actually tells you?

Regards

Marcel



  reply	other threads:[~2011-11-15  2:53 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
2011-11-15  2:31       ` Brian Gix
2011-11-15  2:53         ` Marcel Holtmann [this message]
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=1321325610.15441.479.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