Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Cc: Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: [PATCH v2] epiphany-2.30.2: unbreak do_configure by setting ca-file path
Date: Mon, 25 Oct 2010 14:07:59 +0200	[thread overview]
Message-ID: <4CC5731F.2030009@dresearch.de> (raw)
In-Reply-To: <1288006635.3793.38.camel@mattotaupa>

Am 25.10.2010 13:37, schrieb Paul Menzel:
> Am Montag, den 25.10.2010, 11:55 +0200 schrieb Steffen Sledz:
>> * Disable existence check for ca-bundle file in configure.ac because
>>   it does not work in OE cross compile environment (location at build
>>   host may differ from location at target).
>> * Explicitely set ca-bundle file path according to the one used by
>>   ca-certificates package.
>> ...
>> ++# disable this check because it does not work in all environments
>> ++# (location at build host may differ from target)
>> ++#    if ! test -f "$with_ca_file"; then
>> ++#        AC_MSG_ERROR([No such file '$with_ca_file'. Use --with-ca-file=path to set, or --without-ca-file to disable])
>> ++#    fi
> 
> Would adding the following check also work?
> 
>         if test "$cross_compiling" != "yes"; then
>          …
>         fi

I don't think this is a good idea. It is not a problem of cross compiling. Cross compiling is just one case where it occurs.

Also if i build for the same architecture it is not a good idea to check for the existence of a file *at buildtime* and compile this path into the binary.

The existence of such a file should be checked and handled at runtime only.

> I think this would be more portable. Could you report that issue
> upstream too please.

I'll try.

Steffen




  reply	other threads:[~2010-10-25 12:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 21:56 testing branch 2010-10-14 Cliff Brake
2010-10-15 10:21 ` Cliff Brake
2010-10-16  7:24 ` Petr Štetiar
2010-10-19  6:21   ` Frans Meulenbroeks
2010-10-19 11:06     ` Cliff Brake
2010-10-19 11:13       ` Koen Kooi
2010-10-17 12:27 ` testing branch 2010-10-14 - configure epiphany still fails Sledz, Steffen
2010-10-20 11:08   ` Steffen Sledz
2010-10-20 11:10     ` [PATCH 1/2] ca-certificates: unbreak do_configure of packages depending on ca-bundle.pem Steffen Sledz
2010-10-21  9:59       ` Thomas Zimmermann
2010-10-20 11:10     ` [PATCH 2/2] epiphany-2.30.2: unbreak do_configure by setting ca-file path Steffen Sledz
2010-10-21  9:14       ` Steffen Sledz
2010-10-21  9:54         ` Holger Freyther
2010-10-21 12:11           ` Steffen Sledz
2010-10-23 12:27             ` Sledz, Steffen
2010-10-25  9:55               ` [PATCH v2] " Steffen Sledz
2010-10-25 10:03                 ` Steffen Sledz
2010-10-25 11:37                 ` Paul Menzel
2010-10-25 12:07                   ` Steffen Sledz [this message]
2010-10-25 15:36                     ` Steffen Sledz
2010-10-25 18:02                     ` Khem Raj

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=4CC5731F.2030009@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paulepanter@users.sourceforge.net \
    /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