Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sanity: removed broken compiler check
Date: Tue, 22 Nov 2016 12:11:45 +0100	[thread overview]
Message-ID: <ly4m2zojke.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CABcZANmqH9gEhO67-9_0fEinU6FhMxRsgaC0hcVrkxd9_cH1HA@mail.gmail.com> (Christopher Larson's message of "Mon, 21 Nov 2016 20:22:32 -0700")

Christopher Larson <clarson@kergoth.com> writes:

>> |    Please install the following missing utilities: C Compiler (ccache gcc ),C++ Compiler (ccache g++ )
>>
>> Remove this check for now.
>> [...]
>> +++ b/meta/classes/sanity.bbclass
>> [...]
>> -    if not check_app_exists('${BUILD_CC}', d):
>> -        missing = missing + "C Compiler (%s)," % d.getVar("BUILD_CC", True)
>> -
>> -    if not check_app_exists('${BUILD_CXX}', d):
>> -        missing = missing + "C++ Compiler (%s)," % d.getVar("BUILD_CXX", True)
>> -
>>
>
> Is there a reason check_app_exists() wasn’t fixed to handle symlinks
> instead?

This will not help. 'check_app_exist()' checks for the existence of a
file (e.g. like 'test -x "${BUILD_CC}"' with iterating $PATH).  But
'ccache gcc' is not a single file but a chain of files.

A more reliable method would be to call the program with '--version' or
so and check the exit code.

But gcc and g++ are elementary tools which are existing very likely on
every developers machine and which will not introduce silent and difficulty
to detect breakage.  So I removed the check for now instead to implement
the method above.


Enrico


  reply	other threads:[~2016-11-22 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 11:39 [PATCH] sanity: removed broken compiler check Enrico Scholz
2016-11-22  3:22 ` Christopher Larson
2016-11-22 11:11   ` Enrico Scholz [this message]
2016-11-22 11:42   ` Burton, Ross
2016-11-22 12:01     ` Enrico Scholz
2016-11-22 12:11       ` Burton, Ross
2016-11-22 12:16         ` Enrico Scholz
2016-11-22 20:33           ` Andre McCurdy

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=ly4m2zojke.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --cc=clarson@kergoth.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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