Re: [yocto] ERRORS while building customized yocto image for Raspberrypi #yocto

[Quentin Schulz]

Hi Bhavya,

On Fri, Jul 24, 2020 at 09:12:09PM -0700, paruchuribhavyas...@gmail.com wrote:
> Hi Quentin
> 
> I tried changing it but facing same kind of error during Build.
> 

Your S = "${WORKDIR}" is probably wrong then.

Is there only a directory "at the root" of the tarball? I mean if you
untar it, do you get one directory where all your source code is? In
that case, if the subdirectory is named "gsm-${PV}" (replace PV with the
correct and full number), you don't need to define S because the default
should be just enough IIRC.

Otherwise, S = "${WORKDIR}/"

Finally, since your license is not in the tarball (but it should really
be actually), you need to prefix your LIC_FILES_CHKSUM with "../"
otherwise the license won't be found.

Moreover, you can't reassign twice the same variable and expect them to
be merged. That's what you did for SRC_URI but I missed that you also
did it for LICENSE, if it's dual licensed: LICENSE = "GNUC | GPLv3" or
LICENSE = "GNUC & GPLv3", the meaning is obviously not the same but you
only can know what to put there.

N.B.: You still need the SRC_URI as I gave you in an earlier mail.

Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50096): https://lists.yoctoproject.org/g/yocto/message/50096
Mute This Topic: https://lists.yoctoproject.org/mt/75765727/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-java] icedtea7-native fails to build with error: cc1plus: all warnings being treated as errors

[ithijme]

Hi,

I am trying to build openjdk-8-native, however its icedtea7 dependency fails to 
build.
The error is a little hard to parse but it appears to be due to warnings being 
treated as errors.
There are a lot of logs like the following:

| In function ‘int fprintf(FILE*, const char*, ...)’,
| inlined from ‘void ADLParser::frame_parse()’ at 
.../build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk-boot/hotspot/src/share/vm/adlc/adlparse.cpp:1118:34:
| /usr/include/x86_64-linux-gnu/bits/stdio2.h:100:24: error: ‘%s’ directive 
argument is null [-Werror=format-overflow=]
|   100 |   return __fprintf_chk (__stream, __USE_FORTIFY_LEVEL - 1, __fmt,
|   |  ~~^~
|   101 |    __va_arg_pack ());
|   |    ~
| cc1plus: all warnings being treated as errors
| make[7]: *** 
[.../build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/openjdk-boot/hotspot/make/linux/makefiles/adlc.make:207:
 ../generated/adfiles/adlparse.o] Error 1
| make[7]: *** Waiting for unfinished jobs
| cc1plus: all warnings being treated as errors

I am using the following bblayers:
* poky/meta
* poky/meta-poky
* meta-openembedded/meta-oe
* meta-java

All layers are from the dunfell branch of their respective repositories and are 
up to date.

Can anybody offer any advice on how to successfully build the openjdk-8-native 
recipe ? Anybody have it working themselves ?

Cheers
Jeff
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50097): https://lists.yoctoproject.org/g/yocto/message/50097
Mute This Topic: https://lists.yoctoproject.org/mt/75821964/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [bitbake-devel] [yocto] Stable Warrior branch

[akuster]

Adrian,

On 7/21/20 1:53 AM, Richard Purdie wrote:
> On Tue, 2020-07-14 at 16:56 +0300, Adrian Bunk wrote:
>> On Thu, Jun 04, 2020 at 09:28:00PM -0700, akuster wrote:
>>> Hello,
>>>
>>> The Warrior branch of Poky has had its last official dot release.
>>> It
>>> will be moving to Community support and EOL within 6 weeks if no
>>> one
>>> steps up.
>>> If someone is interested in taking on the responsibilities of
>>> maintaining the "Warrior" branch moving forward, please email this
>>> list.
>> I have an interest in keeping warrior branch alive in poky and meta-
>> oe,
>> and I'll take this responsibility since noone else seems to be
>> interested.

Are you still interested?

-armin
>>> Please look at the
>>> https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS for what
>>> will
>>> be expected.
>> I have some ideas, but not yet a fixed plan how I will set this up.
> Ok. FWIW we are struggling a little with keeping the older releases
> building on the autobuilder as the workers change. We do have plans for
> handling this with buildtools but its not rolled out on the older
> autobuilder-helper branches.
>
> I do have work in progress working with Jeremy for thud
> (contrib/rpurdie/thud), much of which should apply to warrior too
> (contrib/rpurdie/warrior is a guess). I just really want to highlight
> that there may be some initial work to get these older branches to the
> point where they continue to work on the infrastructure.
>
> I think we may have to accept backporting a lot of patches in helper to
> bring things more into sync with master/dunfell to make all this easier
> to maintain/get working.
>
> Cheers,
>
> Richard
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50098): https://lists.yoctoproject.org/g/yocto/message/50098
Mute This Topic: https://lists.yoctoproject.org/mt/75699867/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Offline Build #yocto

[Fred Baksik]

On Mon, Jul 27, 2020, at 12:38 AM, Amrun Nisha.R wrote:
> Hi Fred,
> 
> check whether the downloads folder has all the files. I found that while 
> checking the folders, I can't able to find the branches and ref folders in 
> the git2 folder (downloads/git2). Once i placed the empty folders branch and 
> ref, it works fine for me. And I didnt update on the config file. 
> -=-=-=-=-=-=-=-=-=-=-=-
> 

https://www.yoctoproject.org/docs/2.7.4/mega-manual/mega-manual.html#replicating-a-build-offline

The downloads folder that I used to setup the pre-mirror didn't even contain 
the git2 folder.  From the directions:
*Optionally Remove Any Git or other SCM Subdirectories From the Downloads 
Directory:* If you want, you can clean up your downloads directory by removing 
any Git or other Source Control Management (SCM) subdirectories such as 
`${DL_DIR}/git2/*`. The tarballs already contain these subdirectories.

FYI, the documentation states for DL_DIR:
By default, `DL_DIR` gets files suitable for mirroring for everything except 
Git repositories. If you want tarballs of Git repositories, use the 
`BB_GENERATE_MIRROR_TARBALLS` 

 variable.

All I can say is that following these directions for replicating the build 
offline worked.
When skipping any of the steps I saw similar errors like the one in the 
original post.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50099): https://lists.yoctoproject.org/g/yocto/message/50099
Mute This Topic: https://lists.yoctoproject.org/mt/75676959/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

[Scott Whitney]

Hi Yocto group,

I'm working with a newly-released copy of Yocto Zeus from Variscite for the 
i.MX8MM Mini, although the same option seems to apply to the previous Yocto 
Warrior.

I understand that a Linux real-time kernel can be enabled by setting 
LINUX_KERNEL_TYPE = "preempt-rt".  Where does this option need to be set so 
that when I bitbake fsl-image-qt5, I get the Linux "preempt-rt" kernel instead 
of the "standard" kernel?

Is there a specific configuration file that needs to be modified, or a new 
recipe in a layer?  I am confused and hoping that you can help.

Best regards,

Scott D. Whitney
Principal Software Engineer
[cid:image001.png@01D6642D.AAEAAA60]
Intertech Engineering Associates, Inc.
100 Lowder Brook Drive, Suite 2500
Westwood, MA  02090
s...@inea.com| T: 781-801-1152| F: 
781-801-1108| www.inea.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50100): https://lists.yoctoproject.org/g/yocto/message/50100
Mute This Topic: https://lists.yoctoproject.org/mt/75830848/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[Stephen Jolley]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 336
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.1", "3.2, "3.99" and "Future", the more pressing/urgent issues
being in "3.1" and then "3.2".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50101): https://lists.yoctoproject.org/g/yocto/message/50101
Mute This Topic: https://lists.yoctoproject.org/mt/75834766/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.2

[Stephen Jolley]

All,

Below is the list as of top 30 bug owners as of the end of WW30 of who have
open medium or higher bugs and enhancements against YP 3.2.   There are 67
possible work days left until the final release candidates for YP 3.2 needs
to be released.


Who

Count


david.re...@windriver.com

10


mark.mor...@windriver.com

7


bluelightn...@bluelightning.org

7


r...@burtonini.com

7


richard.pur...@linuxfoundation.org

7


mich...@yoctoproject.org

5


qi.c...@windriver.com

5


raj.k...@gmail.com

3


randy.macl...@windriver.com

2


chee.yang@intel.com

2


kai.k...@windriver.com

2


kerg...@gmail.com

2


yi.z...@windriver.com

2


sakib.sa...@windriver.com

2


trevor.gamb...@windriver.com

2


jpewhac...@gmail.com

2


timothy.t.orl...@intel.com

2


rpj...@crashcourse.ca

2


changqing...@windriver.com

1


mark.ha...@kernel.crashing.org

1


jae...@xilinx.com

1


maxime.roussinbelan...@gmail.com

1


matthew.z...@windriver.com

1


jpuhl...@mvista.com

1


bruce.ashfi...@gmail.com

1


liu.min...@gmail.com

1


kai.ruh...@live.com

1


hongxu@windriver.com

1


matt.ranos...@konsulko.com

1


anuj.mit...@intel.com

1


Grand Total

83

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50102): https://lists.yoctoproject.org/g/yocto/message/50102
Mute This Topic: https://lists.yoctoproject.org/mt/75834892/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW30!

[Stephen Jolley]

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


richard.pur...@linuxfoundation.org

5


st...@sakoman.com

1


trevor.gamb...@windriver.com

1


kexin@windriver.com

1


guillaume.bon...@epitech.eu

1


timothy.t.orl...@intel.com

1


Grand Total

10

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50103): https://lists.yoctoproject.org/g/yocto/message/50103
Mute This Topic: https://lists.yoctoproject.org/mt/75834976/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

[Bruce Ashfield]

On Mon, Jul 27, 2020 at 3:51 PM Scott Whitney  wrote:

> Hi Yocto group,
>
>
>
> I’m working with a newly-released copy of Yocto Zeus from Variscite for
> the i.MX8MM Mini, although the same option seems to apply to the previous
> Yocto Warrior.
>
>
>
> I understand that a Linux real-time kernel can be enabled by setting
> LINUX_KERNEL_TYPE = “preempt-rt”.  Where does this option need to be set so
> that when I bitbake fsl-image-qt5, I get the Linux “preempt-rt” kernel
> instead of the “standard” kernel?
>
>
>
> Is there a specific configuration file that needs to be modified, or a new
> recipe in a layer?  I am confused and hoping that you can help.
>
>
If you aren't using linux-yocto, you'll need to arrange for the preempt-rt
patch(es) to be applied to whatever kernel you are using. Which means you
are creating a new recipe, bbappending an existing one, or if you are lucky
the kernel provider already has a -rt recipe available.

If you are using linux-yocto, it's as simple as setting the preferred
provider of the kernel as linux-yocto-rt  and building.

Bruce



>
>
> Best regards,
>
>
>
> *Scott D. Whitney*
>
> Principal Software Engineer
>
>
> Intertech Engineering Associates, Inc.
> 100 Lowder Brook Drive, Suite 2500
> Westwood, MA  02090
> *s...@inea.com *| T: 781-801-1152|
> F: 781-801-1108| *www.inea.com *
>
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50104): https://lists.yoctoproject.org/g/yocto/message/50104
Mute This Topic: https://lists.yoctoproject.org/mt/75830848/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-java] icedtea7-native fails to build with error: cc1plus: all warnings being treated as errors

[Robert Joslyn]

On Mon, 2020-07-27 at 06:16 -0700, ithi...@gmail.com wrote:
> Hi,
> 
> I am trying to build openjdk-8-native, however its icedtea7 dependency
> fails to build.
> The error is a little hard to parse but it appears to be due to warnings
> being treated as errors.
> There are a lot of logs like the following:
> 
> | In function ‘int fprintf(FILE*, const char*, ...)’,
> | inlined from ‘void ADLParser::frame_parse()’ at
> .../build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-
> 2.1.3/build/openjdk-boot/hotspot/src/share/vm/adlc/adlparse.cpp:1118:34:
> | /usr/include/x86_64-linux-gnu/bits/stdio2.h:100:24: error: ‘%s’
> directive argument is null [-Werror=format-overflow=]
> |   100 |   return __fprintf_chk (__stream, __USE_FORTIFY_LEVEL - 1,
> __fmt,
> |   | 
> ~~^~
> |   101 |__va_arg_pack ());
> |   |~
> | cc1plus: all warnings being treated as errors
> | make[7]: *** [.../build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-
> r1.0/icedtea-2.1.3/build/openjdk-
> boot/hotspot/make/linux/makefiles/adlc.make:207:
> ../generated/adfiles/adlparse.o] Error 1
> | make[7]: *** Waiting for unfinished jobs
> | cc1plus: all warnings being treated as errors
> 
> I am using the following bblayers:
> * poky/meta
> * poky/meta-poky
> * meta-openembedded/meta-oe
> * meta-java
> 
> All layers are from the dunfell branch of their respective repositories
> and are up to date.
> 
> Can anybody offer any advice on how to successfully build the openjdk-8-
> native recipe ? Anybody have it working themselves ?
> 
> Cheers
> Jeff
> 

I had the same problem about a month ago. My quick fix was to create an
icedtea7-native_%.bbappend in my own layer to disable turning that warning
into an error:

CFLAGS_append = " -Wno-error=format-overflow"

I assume it's due to the compiler on your build machine being newer (or at
least different) than what the recipe is expecting.

Robert

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50105): https://lists.yoctoproject.org/g/yocto/message/50105
Mute This Topic: https://lists.yoctoproject.org/mt/75821964/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] #toolchain #yocto #devtool #linux

[andymishra97]

Hi,
I am trying to build a yocto *demo-coreip-cli* image for my custom RISC-V SOC 
which only supports *imafd* instructions. For the compilation of cross 
toolchain that is used by Bitbake, I tried changing cross-binutils.inc recipe 
and cross-gcc.inc recipe in openembedded-core layer by including “ 
*–with-arch=rv64imafd* ” in " *EXTRA_OECONF* " variable. Is there anything else 
I am missing or doing wrong? Thank You.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50106): https://lists.yoctoproject.org/g/yocto/message/50106
Mute This Topic: https://lists.yoctoproject.org/mt/75838691/21656
Mute #devtool: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/devtool
Mute #linux: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/linux
Mute #toolchain: 
https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/toolchain
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Remove connman package from yocto sdk.

[NIKHIL PATIL]

hi,
 Still we ar facing same issue  ,
  If anyone know, please help.

On Fri, Jul 24, 2020 at 6:14 PM NIKHIL PATIL  wrote:

> Hi team,
>   We want to use NetworkManager to access internet using LTE
> module . but connman and Networkmaanger both are installed.
>
>   I struggled so much to remove connman,  I tried as follows :-
>1) Added IMAGE_INSTALL_remove = "connman"  in local.conf
> but it still come with sato image.
>
> 2) Added DISTRO_FEATURE_remove = "connman"  in local.conf
> but it still come with sato image.
>
> By default connman is coming in image , how to remove connman ?
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50107): https://lists.yoctoproject.org/g/yocto/message/50107
Mute This Topic: https://lists.yoctoproject.org/mt/75765466/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-java] icedtea7-native fails to build with error: cc1plus: all warnings being treated as errors

[Jeff Ithier]

Hi Robert,

Thanks for the tip, it seems to have worked and I've gotten past the 
compilation step.


Unfortunately, now the build seems to be failing the do_package_rpm task 
with the following error:


Exception: bb.process.ExecutionError: Execution of 
'../build/tmp/work/aarch64-poky-linux/icedtea7-native/%-r0/temp/run.BUILDSPEC.153296' 
failed with exit code 127:
../build/tmp/work/aarch64-poky-linux/icedtea7-native/%-r0/temp/run.BUILDSPEC.153296: 
106: rpmbuild: not found

WARNING: exit code 127 from a shell command.

Did you also encounter this ?

Cheers
Jeff

On 7/28/20 5:28 AM, Robert Joslyn wrote:

On Mon, 2020-07-27 at 06:16 -0700, ithi...@gmail.com wrote:

Hi,

I am trying to build openjdk-8-native, however its icedtea7 dependency
fails to build.
The error is a little hard to parse but it appears to be due to warnings
being treated as errors.
There are a lot of logs like the following:

| In function ‘int fprintf(FILE*, const char*, ...)’,
| inlined from ‘void ADLParser::frame_parse()’ at
.../build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-
2.1.3/build/openjdk-boot/hotspot/src/share/vm/adlc/adlparse.cpp:1118:34:
| /usr/include/x86_64-linux-gnu/bits/stdio2.h:100:24: error: ‘%s’
directive argument is null [-Werror=format-overflow=]
|   100 |   return __fprintf_chk (__stream, __USE_FORTIFY_LEVEL - 1,
__fmt,
|   |
~~^~
|   101 |__va_arg_pack ());
|   |~
| cc1plus: all warnings being treated as errors
| make[7]: *** [.../build/tmp/work/x86_64-linux/icedtea7-native/2.1.3-
r1.0/icedtea-2.1.3/build/openjdk-
boot/hotspot/make/linux/makefiles/adlc.make:207:
../generated/adfiles/adlparse.o] Error 1
| make[7]: *** Waiting for unfinished jobs
| cc1plus: all warnings being treated as errors

I am using the following bblayers:
* poky/meta
* poky/meta-poky
* meta-openembedded/meta-oe
* meta-java

All layers are from the dunfell branch of their respective repositories
and are up to date.

Can anybody offer any advice on how to successfully build the openjdk-8-
native recipe ? Anybody have it working themselves ?

Cheers
Jeff


I had the same problem about a month ago. My quick fix was to create an
icedtea7-native_%.bbappend in my own layer to disable turning that warning
into an error:

CFLAGS_append = " -Wno-error=format-overflow"

I assume it's due to the compiler on your build machine being newer (or at
least different) than what the recipe is expecting.

Robert

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50108): https://lists.yoctoproject.org/g/yocto/message/50108
Mute This Topic: https://lists.yoctoproject.org/mt/75821964/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-