xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@entel.upc.edu>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: configure failure
Date: Wed, 22 Feb 2012 12:19:32 +0100	[thread overview]
Message-ID: <CAPLaKK6y6Ofygn_bwDXQK_mT+xEDb9FmFCsSSJsezgvO66z7cQ@mail.gmail.com> (raw)
In-Reply-To: <4F44C8BE.4050809@amd.com>

2012/2/22 Christoph Egger <Christoph.Egger@amd.com>:
> On 02/22/12 11:30, Roger Pau Monné wrote:
>>
>> 2012/2/22 Christoph Egger<Christoph.Egger@amd.com>:
>>>
>>> On 02/22/12 10:59, Roger Pau Monné wrote:
>>>>
>>>>
>>>> 2012/2/22 Christoph Egger<Christoph.Egger@amd.com>:
>>>>>
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> configure fails on NetBSD that there is no brctl.
>>>>> NetBSD has no brctl, NetBSD has brconfig.
>>>>
>>>>
>>>>
>>>> Sorry Christoph, the brctl test is going away (from configure at least).
>>>
>>>
>>>
>>> There are some more Linux specific tests:
>>> - ip
>>> - uuid_clear in libuuid
>>
>>
>> Thanks for reporting, I will take care of those once the patch has
>> passed the test system (sorry for that, but I cannot test on so many
>> systems).
>>
>>> Also the check for yajl_alloc in libyajl fails although I have libyajl
>>> version 1 installed. The check may be correct but configure shouldn't
>>> fail
>>> if version 1 is still supported.
>>
>>
>> Since I guess you have it in /usr/pkg/, have you set PREPEND_LIB or
>> APPEND_LIB env variables before executing configure?
>
>
> No, I have set EXTRA_LIB and EXTRA_INCLUDES.
> I tried both PREPEND_LIB and APPEND_LIB and that works.

EXTRA_LIB and EXTRA_INCLUDES is deprecated in favor of PREPEND_ and
APPEND_, which it's basically the same but allows a more fine grained
control.

>
> Oh and the integer type checks fail. Snippet from config.log:
>
> configure:7600: checking for int64_t
> configure:7600: gcc -c -I/usr/pkg/include -g -O2 conftest.c >&5
> conftest.c: In function 'main':
> conftest.c:90: error: expected ')' before ';' token
> conftest.c:91: error: expected expression before ']' token
> configure: 7600: $? = 1

This was added by default when running autoscan, I guess we can
disable those checks.

>
> The unsigned integer type checks succeed.
>
>
> Christoph
>
> --
> ---to satisfy European Law for business letters:
> Advanced Micro Devices GmbH
> Einsteinring 24, 85689 Dornach b. Muenchen
> Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
> Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
> Registergericht Muenchen, HRB Nr. 43632
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-02-22 11:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22  9:57 configure failure Christoph Egger
2012-02-22  9:59 ` Roger Pau Monné
2012-02-22 10:21   ` Christoph Egger
2012-02-22 10:30     ` Roger Pau Monné
2012-02-22 10:51       ` Christoph Egger
2012-02-22 11:19         ` Roger Pau Monné [this message]
2012-02-23  9:18     ` Roger Pau Monné
2012-02-23 13:13       ` Olaf Hering
2012-02-29 14:46         ` Ian Jackson
2012-02-29 14:46       ` Ian Jackson
2012-02-29 14:53         ` Roger Pau Monné

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=CAPLaKK6y6Ofygn_bwDXQK_mT+xEDb9FmFCsSSJsezgvO66z7cQ@mail.gmail.com \
    --to=roger.pau@entel.upc.edu \
    --cc=Christoph.Egger@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).