Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Cc: Laurentiu Palcu
	<laurentiu.palcu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 1/1] flex: fix m4 issue on target
Date: Tue, 05 Nov 2013 17:16:45 +0100	[thread overview]
Message-ID: <ly38nau8lu.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <f61f1d9fc224cc017996769e23b08d0af13f3722.1383663447.git.laurentiu.palcu@intel.com> (Laurentiu Palcu's message of "Tue, 5 Nov 2013 16:58:05 +0200")

Laurentiu Palcu
<laurentiu.palcu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> writes:

> Flex needs m4 to run (see below) and, since the create_wrapper
> introduces a bash dependency, export the right m4 path when /etc/profile
> is sourced by the shell.
>
> Snippet from the flex documentation:
> "The macro processor m4 must be installed wherever flex is installed.
> <...>
> m4 is only required at the time you run flex."

Content at profile.d/ won't be evaluated when program is started without
a shell (e.g. by 'execlp("flex", "flex", ...)').  


> [YOCTO #5329]

This should be solved by defining a correct path for the m4 binary at
build time.

EXTRA_OECONF += " ac_cv_path_M4=${M4}"
EXTRA_OEMAKE += " m4=${M4_class-native}"

is probably a better solution.



Enrico


  reply	other threads:[~2013-11-05 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 14:58 [PATCH 0/1] flex: fix m4 issue on target Laurentiu Palcu
2013-11-05 14:58 ` [PATCH 1/1] " Laurentiu Palcu
2013-11-05 16:16   ` Enrico Scholz [this message]
2013-11-06 10:39     ` Laurentiu Palcu

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=ly38nau8lu.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --cc=laurentiu.palcu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --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