* [PATCH V3] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty
@ 2018-03-16 21:41 Khem Raj
2018-03-16 21:43 ` Andre McCurdy
0 siblings, 1 reply; 3+ messages in thread
From: Khem Raj @ 2018-03-16 21:41 UTC (permalink / raw)
To: openembedded-core
We allow to set LINKER_HASH_STYLE to be empty so this would fail
since --with-linker-hash-style needs an argument and cant be empty
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
Changes in v3:
- Fix typo in gcc option
Changes in v2:
- Use inline if statement instead of old syntax
meta/recipes-devtools/gcc/gcc-7.3.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc b/meta/recipes-devtools/gcc/gcc-7.3.inc
index d56d2c5e06..a80926216b 100644
--- a/meta/recipes-devtools/gcc/gcc-7.3.inc
+++ b/meta/recipes-devtools/gcc/gcc-7.3.inc
@@ -100,7 +100,7 @@ EXTRA_OECONF_BASE = "\
--disable-bootstrap \
--disable-libmudflap \
--with-system-zlib \
- --with-linker-hash-style=${LINKER_HASH_STYLE} \
+ ${@'--with-linker-hash-style=${LINKER_HASH_STYLE}' if '${LINKER_HASH_STYLE}' else ''} \
--enable-linker-build-id \
--with-ppl=no \
--with-cloog=no \
--
2.16.2
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH V3] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty
2018-03-16 21:41 [PATCH V3] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty Khem Raj
@ 2018-03-16 21:43 ` Andre McCurdy
2018-03-19 12:53 ` Burton, Ross
0 siblings, 1 reply; 3+ messages in thread
From: Andre McCurdy @ 2018-03-16 21:43 UTC (permalink / raw)
To: Khem Raj; +Cc: OE Core mailing list
On Fri, Mar 16, 2018 at 2:41 PM, Khem Raj <raj.khem@gmail.com> wrote:
> We allow to set LINKER_HASH_STYLE to be empty so this would fail
> since --with-linker-hash-style needs an argument and cant be empty
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> Changes in v3:
> - Fix typo in gcc option
>
> Changes in v2:
> - Use inline if statement instead of old syntax
>
> meta/recipes-devtools/gcc/gcc-7.3.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc b/meta/recipes-devtools/gcc/gcc-7.3.inc
> index d56d2c5e06..a80926216b 100644
> --- a/meta/recipes-devtools/gcc/gcc-7.3.inc
> +++ b/meta/recipes-devtools/gcc/gcc-7.3.inc
> @@ -100,7 +100,7 @@ EXTRA_OECONF_BASE = "\
> --disable-bootstrap \
> --disable-libmudflap \
> --with-system-zlib \
> - --with-linker-hash-style=${LINKER_HASH_STYLE} \
> + ${@'--with-linker-hash-style=${LINKER_HASH_STYLE}' if '${LINKER_HASH_STYLE}' else ''} \
What are the rules about when to use d.getVar('FOO') -vs- when to use
${FOO} in python fragments like this?
> --enable-linker-build-id \
> --with-ppl=no \
> --with-cloog=no \
> --
> 2.16.2
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH V3] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty
2018-03-16 21:43 ` Andre McCurdy
@ 2018-03-19 12:53 ` Burton, Ross
0 siblings, 0 replies; 3+ messages in thread
From: Burton, Ross @ 2018-03-19 12:53 UTC (permalink / raw)
To: Andre McCurdy; +Cc: OE Core mailing list
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
On 16 March 2018 at 21:43, Andre McCurdy <armccurdy@gmail.com> wrote:
> On Fri, Mar 16, 2018 at 2:41 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > We allow to set LINKER_HASH_STYLE to be empty so this would fail
> > since --with-linker-hash-style needs an argument and cant be empty
> >
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > ---
> > Changes in v3:
> > - Fix typo in gcc option
> >
> > Changes in v2:
> > - Use inline if statement instead of old syntax
> >
> > meta/recipes-devtools/gcc/gcc-7.3.inc | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc
> b/meta/recipes-devtools/gcc/gcc-7.3.inc
> > index d56d2c5e06..a80926216b 100644
> > --- a/meta/recipes-devtools/gcc/gcc-7.3.inc
> > +++ b/meta/recipes-devtools/gcc/gcc-7.3.inc
> > @@ -100,7 +100,7 @@ EXTRA_OECONF_BASE = "\
> > --disable-bootstrap \
> > --disable-libmudflap \
> > --with-system-zlib \
> > - --with-linker-hash-style=${LINKER_HASH_STYLE} \
> > + ${@'--with-linker-hash-style=${LINKER_HASH_STYLE}' if
> '${LINKER_HASH_STYLE}' else ''} \
>
> What are the rules about when to use d.getVar('FOO') -vs- when to use
> ${FOO} in python fragments like this?
I just had to test this in another recipe to verify it does what you expect.
${FOO} isn't expanded anymore in python functions, but it does get expanded
inside python expansions.
Ross
[-- Attachment #2: Type: text/html, Size: 2118 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-03-19 12:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-16 21:41 [PATCH V3] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty Khem Raj
2018-03-16 21:43 ` Andre McCurdy
2018-03-19 12:53 ` Burton, Ross
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.