Since Whinlatter [1], FORTRAN is set by a weak assignment, so the
':forcevariable' is no longer needed.

Update the example accordingly, and replace the outdated comments above.

[1]: 
https://git.openembedded.org/openembedded-core/commit/?id=50abae55eda0115d073bbc6552f2fcb4ecbb7949

Signed-off-by: João Marcos Costa <[email protected]>
---
 meta/conf/templates/default/local.conf.sample.extended | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/meta/conf/templates/default/local.conf.sample.extended 
b/meta/conf/templates/default/local.conf.sample.extended
index 999a09dac1..f4e35d94fd 100644
--- a/meta/conf/templates/default/local.conf.sample.extended
+++ b/meta/conf/templates/default/local.conf.sample.extended
@@ -305,10 +305,9 @@
 #USERADD_ERROR_DYNAMIC = "1"
 
 # Enabling FORTRAN
-# Note this is not officially supported and is just illustrated here to
-# show an example of how it can be done
-# You'll also need your fortran recipe to depend on libgfortran
-#FORTRAN:forcevariable = ",fortran"
+# This variable will fall into LANGUAGES variable (i.e., "c,c++${FORTRAN}"),
+# which is then consumed in gcc-configure-common.inc.
+#FORTRAN = ",fortran"
 
 #
 # Kernel image features
-- 
2.47.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#239276): 
https://lists.openembedded.org/g/openembedded-core/message/239276
Mute This Topic: https://lists.openembedded.org/mt/119920836/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to