|
Re: meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'
as i read it, this issue is also related to -pthread versus
-lpthread:
https://blog.jiejiss.com/A-RISC-V-gcc-pitfall-revealed-by-a-glibc-update/
rday
as i read it, this issue is also related to -pthread versus
-lpthread:
https://blog.jiejiss.com/A-RISC-V-gcc-pitfall-revealed-by-a-glibc-update/
rday
|
By
Robert P. J. Day
·
#57476
·
|
|
Re: Installing gfortran into native sysroot for libgfortran
You shouldn't have to disable the sstate cache but glad you got it
working. Which release series is that with?
It does sound like there is a bug to fix somewhere in there.
Cheers,
Richard
You shouldn't have to disable the sstate cache but glad you got it
working. Which release series is that with?
It does sound like there is a bug to fix somewhere in there.
Cheers,
Richard
|
By
Richard Purdie
·
#57475
·
|
|
Minutes: Yocto Project Weekly Triage Meeting 7/7/2022
Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage
Attendees: Steve Sakoman, Joshua Watt, Saul Wold, Alexandre Belloni, Paulo Neves, Richard Purdie, Aryaman Gupta, Randy Macleod,
Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage
Attendees: Steve Sakoman, Joshua Watt, Saul Wold, Alexandre Belloni, Paulo Neves, Richard Purdie, Aryaman Gupta, Randy Macleod,
|
By
sakib.sajal@...
·
#57474
·
|
|
Re: meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'
it does indeed fix the curl build error, thanks. i haven't tested
its operation yet, but getting a build was all i was after at the
moment.
rday
it does indeed fix the curl build error, thanks. i haven't tested
its operation yet, but getting a build was all i was after at the
moment.
rday
|
By
Robert P. J. Day
·
#57473
·
|
|
Re: meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'
does backporting
https://github.com/curl/curl/commit/50efb0822aa0e0ab165158dd0a26e65a2290e6d2
to curl help ?
does backporting
https://github.com/curl/curl/commit/50efb0822aa0e0ab165158dd0a26e65a2290e6d2
to curl help ?
|
By
Khem Raj
·
#57472
·
|
|
Re: Installing gfortran into native sysroot for libgfortran
Problem solved: the issue was actually that I was using a network sstate cache,
and the cached output of gcc-cross did not contain gfortran. Disabling the
sstate cache for gcc-cross causes gfortran to
Problem solved: the issue was actually that I was using a network sstate cache,
and the cached output of gcc-cross did not contain gfortran. Disabling the
sstate cache for gcc-cross causes gfortran to
|
By
Gregory Anders <greg@...>
·
#57471
·
|
|
Re: meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'
another data point, matches exactly what i'm referring to:
https://github.com/curl/curl/issues/9055
rday
another data point, matches exactly what i'm referring to:
https://github.com/curl/curl/issues/9055
rday
|
By
Robert P. J. Day
·
#57470
·
|
|
meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'
on admittedly unsupported ubuntu 22.04 platform but it's clear this
is a known issue as it's pretty much identical to what one reads here:
on admittedly unsupported ubuntu 22.04 platform but it's clear this
is a known issue as it's pretty much identical to what one reads here:
|
By
Robert P. J. Day
·
#57469
·
|
|
Re: Installing gfortran into native sysroot for libgfortran
in your fortran app recipe you have to add DEPENDS = "libgfortran"
in your fortran app recipe you have to add DEPENDS = "libgfortran"
|
By
Khem Raj
·
#57468
·
|
|
Installing gfortran into native sysroot for libgfortran
Hello,
I'm trying to compile libgfortran for a Xilinx Zynq SoC, which uses the arm-xilinx-linux-gnueabi toolchain.
I have added
FORTRAN:forcevariable = ",fortran"
to my local.conf, which causes
Hello,
I'm trying to compile libgfortran for a Xilinx Zynq SoC, which uses the arm-xilinx-linux-gnueabi toolchain.
I have added
FORTRAN:forcevariable = ",fortran"
to my local.conf, which causes
|
By
Gregory Anders <greg@...>
·
#57467
·
|
|
Re: Minutes: Yocto Project Weekly Triage Meeting 6/30/2022
On 2022-06-30 11:21, Sakib Sajal wrote:
This issue is understood, documented and resolved so
I closed the defect with a short explanation.
../Randy
-- # Randy
On 2022-06-30 11:21, Sakib Sajal wrote:
This issue is understood, documented and resolved so
I closed the defect with a short explanation.
../Randy
-- # Randy
|
By
Randy MacLeod
·
#57466
·
|
|
Re: [PATCH yocto-autobuilder-helper 2/2] config.json: remove non-gpl3 job
Maybe ‘deprecated’ isn’t quite the right word to use here.
However, meta-gpl2 is unmaintained. It has no active maintainers, and is worked on only when absolutely needed: in the last year
Maybe ‘deprecated’ isn’t quite the right word to use here.
However, meta-gpl2 is unmaintained. It has no active maintainers, and is worked on only when absolutely needed: in the last year
|
By
Ross Burton
·
#57465
·
|
|
Re: [PATCH yocto-autobuilder-helper 2/2] config.json: remove non-gpl3 job
Where and how the decision was made?
Alex
Where and how the decision was made?
Alex
|
By
Alexander Kanavin
·
#57464
·
|
|
[PATCH yocto-autobuilder-helper 2/2] config.json: remove non-gpl3 job
meta-gplv2 is deprecated, so remove it from the autobuilder in master.
Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 11 -----------
1 file changed, 11 deletions(-)
diff --git
meta-gplv2 is deprecated, so remove it from the autobuilder in master.
Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 11 -----------
1 file changed, 11 deletions(-)
diff --git
|
By
Ross Burton
·
#57463
·
|
|
[PATCH yocto-autobuilder-helper 1/2] config.json: remove meta-gplv2 from the check-layer job
The meta-gplv2 layer is deprecated in master, so remove it from the
check-layer job.
Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 5 +----
1 file changed, 1 insertion(+), 4
The meta-gplv2 layer is deprecated in master, so remove it from the
check-layer job.
Signed-off-by: Ross Burton <ross.burton@...>
---
config.json | 5 +----
1 file changed, 1 insertion(+), 4
|
By
Ross Burton
·
#57462
·
|
|
Re: cve check report package version mismatch
#yocto
Re-adding yocto@.
It’s not always a trivial “this version”, there’s a fairly complex expression in the CVE (see the CPE entry) which needs to be evaluated. Or there may not be a fixed
Re-adding yocto@.
It’s not always a trivial “this version”, there’s a fairly complex expression in the CVE (see the CPE entry) which needs to be evaluated. Or there may not be a fixed
|
By
Ross Burton
·
#57461
·
|
|
Re: cve check report package version mismatch
#yocto
Hello Gaurav,
The CVE STATUS "Patched" means that there was an issue in the past,
but it is either fixed or otherwise mitigated. Open issues are marked
as "Unpatched". If you'd like to see only
Hello Gaurav,
The CVE STATUS "Patched" means that there was an issue in the past,
but it is either fixed or otherwise mitigated. Open issues are marked
as "Unpatched". If you'd like to see only
|
By
Marta Rybczynska
·
#57460
·
|
|
using Devtool upgrade with --no-patch subcommand
#yocto
#devtool
is there anything i am missing here .
is there anything i am missing here .
|
By
ksmanjunath681@...
·
#57459
·
|
|
Recommended boot method for system using rauc, intel and efi.
Hi all
I am building a yocto BSP for an Intel system. The system is using rauc for updating and contains three sections, rescue, A and B, where A/B is the actual SW running. Since the system is Intel
Hi all
I am building a yocto BSP for an Intel system. The system is using rauc for updating and contains three sections, rescue, A and B, where A/B is the actual SW running. Since the system is Intel
|
By
Anders Gnistrup
·
#57458
·
|
|
Re: Unable to fetch repository from GitLab. Checksum mismatch
Hi Rashmi,
You only need to add ;protocol=https to your SRC_URI which starts with git://.
git:// in SRC_URI is NOT the protocol used to download the sources, it is the way Bitbake knows which
Hi Rashmi,
You only need to add ;protocol=https to your SRC_URI which starts with git://.
git:// in SRC_URI is NOT the protocol used to download the sources, it is the way Bitbake knows which
|
By
Quentin Schulz
·
#57457
·
|