<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-devtools/gcc, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-11-07T13:31:53+00:00</updated>
<entry>
<title>The poky repository master branch is no longer being updated.</title>
<updated>2025-11-07T13:31:53+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-11-07T13:31:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8c22ff0d8b70d9b12f0487ef696a7e915b9e3173'/>
<id>urn:sha1:8c22ff0d8b70d9b12f0487ef696a7e915b9e3173</id>
<content type='text'>
You can either:

a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs

b) use the new bitbake-setup

You can find information about either approach in our documentation:
https://docs.yoctoproject.org/

Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.

Long live Poky!

Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: Pin native toolchain to GCC as well</title>
<updated>2025-10-27T11:37:43+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2025-10-22T05:08:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f5a06f0235fb273e98d4d2a261fffac94a458f79'/>
<id>urn:sha1:f5a06f0235fb273e98d4d2a261fffac94a458f79</id>
<content type='text'>
GCC is not buildable with clang and when using clang
for native compiler this fails to build native parts

(From OE-Core rev: 38825ed9e8f24a2ae31df377f7f3c971bc617a19)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: fix local include path for nativesdk-gcc</title>
<updated>2025-09-15T16:57:23+00:00</updated>
<author>
<name>Gregor Herburger</name>
<email>gregor.herburger@ew.tq-group.com</email>
</author>
<published>2025-09-10T11:38:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6c9726de09babd9cc4e81521c5762b32c42d7649'/>
<id>urn:sha1:6c9726de09babd9cc4e81521c5762b32c42d7649</id>
<content type='text'>
By default GCC uses /usr/local/include as the local include prefix.
When building the nativesdk-gcc package, this makes gcc look in the
hosts /usr/local/include and may use non-SDK headers.

Example from current poky:
$# x86_64-pokysdk-linux-gcc -v -E - &lt;/dev/null
 #include &lt;...&gt; search starts here:
  /opt/poky/5.2.99+snapshot/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/15.2.0/include
  /usr/local/include
  /opt/poky/5.2.99+snapshot/sysroots/x86_64-pokysdk-linux/usr/include
  /opt/poky/5.2.99+snapshot/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-pokysdk-linux/15.2.0/include-fixed

Define LOCAL_INCLUDE_DIR along with the other include directories in
defaults.h to set the local include directory to the directory in the
sysroot.

(From OE-Core rev: dadd1e0ec6ad4cf572964c18fa304be9f382f885)

Signed-off-by: Gregor Herburger &lt;gregor.herburger@ew.tq-group.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>recipes: cleanup CVE_STATUS which are resolved now</title>
<updated>2025-08-28T09:47:08+00:00</updated>
<author>
<name>Peter Marko</name>
<email>peter.marko@siemens.com</email>
</author>
<published>2025-08-24T16:55:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ec1ae11f7860da56b0692b265b649bfc62907ef1'/>
<id>urn:sha1:ec1ae11f7860da56b0692b265b649bfc62907ef1</id>
<content type='text'>
The don't show up in CVE metrics anymore since they were either fixed
upstream or recipe version was upgraded meanwhile.

* bind CVE-2019-6470: cpe got corrected in nvd db
* libxml2 CVE-2023-45322: version is now higher than NVD cpe
* zlib CVE-2023-45853: version is now higher than NVD cpe
* gcc CVE-2021-37322: version is now higher than NVD cpe
* python3
  * CVE-2007-4559: version is now higher than NVD cpe
  * CVE-2019-18348: version is now higher than NVD cpe
  * CVE-2020-15523: version is now higher than NVD cpe
  * CVE-2022-26488: version is now higher than NVD cpe
  * CVE-2015-20107: version is now higher than NVD cpe
  * CVE-2023-36632: version is now higher than NVD cpe
* rust
  * CVE-2024-24576: NVD has no cpe, but we have newer version as fix
  * CVE-2024-43402: version is now higher than NVD cpe
* cups CVE-2021-25317: version is now higher than NVD cpe
* ghostscript CVE-2023-38559: version is now higher than NVD cpe
* libtirpc CVE-2021-46828: version is now higher than NVD cpe
* unzip CVE-2008-0888: version is now higher than NVD cpe
* ffmpeg CVE-2023-39018: cpe got corrected in nvd db
* libxslt CVE-2022-29824: version is now higher than NVD cpe
* libyaml
  * CVE-2024-35325: CVE is now rejected in NVD DB
  * CVE-2024-35326: CVE is now rejected in NVD DB
  * CVE-2024-35328: CVE is now rejected in NVD DB

Also add comment for iputils regarding reports for FKIE/NVD2.

Also remove some trailing spaces in python recipe.

(From OE-Core rev: 73ee9789183aa95072af2b51ac9e08203f4e33f9)

Signed-off-by: Peter Marko &lt;peter.marko@siemens.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc-testsuite: Fix test failures with output pattern due to ssh warning.</title>
<updated>2025-08-25T16:47:21+00:00</updated>
<author>
<name>Harish Sadineni</name>
<email>Harish.Sadineni@windriver.com</email>
</author>
<published>2025-08-22T07:12:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9be7072616f11076a09bd8f051cb07e6ca24db14'/>
<id>urn:sha1:9be7072616f11076a09bd8f051cb07e6ca24db14</id>
<content type='text'>
when running oe-selftest for gcc some of the output pattern matchng test cases
were getting failed due to below issue.

Output line 1 was:
Warning: Permanently added '192.168.7
Should match (from /poky/poky/build-st/tmp/work-shared/gcc-15.1.0-r0/sources/
gcc-15.1.0/gcc/testsuite/gcc.dg/dg-output-file-1-lp64.txt):
This is a test output for lp64 target
Failed test for output line 1 This is a test output for lp64 target

(From OE-Core rev: 08200d7ac9d96996dbc1f913bcc0c8bee13592f8)

Signed-off-by: Harish Sadineni &lt;Harish.Sadineni@windriver.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: Oe-selftest failure analysis - fix for pr90579.c test failures</title>
<updated>2025-08-25T16:47:21+00:00</updated>
<author>
<name>Harish Sadineni</name>
<email>Harish.Sadineni@windriver.com</email>
</author>
<published>2025-08-22T07:12:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a6ce306fd35e9734b09a2a5aff6de7eff67abc92'/>
<id>urn:sha1:a6ce306fd35e9734b09a2a5aff6de7eff67abc92</id>
<content type='text'>
When gcc build with PIE enabled the following tests
were getting failed:
 FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+40
 FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+32
 FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+24
 FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+16

Detailed bug info &amp; upstream fix is here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118885

Upstream Status: Backport [https://gcc.gnu.org/cgit/gcc/commit/?id=679e24f5a751663998ff7202149a749e0f7251f9]

(From OE-Core rev: 7641e08044203ac9dde9a53b91bd01f9432d11f2)

Signed-off-by: Harish Sadineni &lt;Harish.Sadineni@windriver.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: Upgrade to 15.2.0 release</title>
<updated>2025-08-14T09:31:10+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2025-08-11T22:42:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4d0f99a61f0a2ab61758be5d14871653189cc4c7'/>
<id>urn:sha1:4d0f99a61f0a2ab61758be5d14871653189cc4c7</id>
<content type='text'>
This is a point release in GCC-15 release series with
number of bugfixes ( 123 to be exact ) as detailed here [1]

Drop backports available in this release

[1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&amp;list_id=485623&amp;resolution=FIXED&amp;target_milestone=15.2

(From OE-Core rev: a7ed61f7b16fddce40c9b2f420783ca8838a2751)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: Fix libsanitizers build with glibc 2.42</title>
<updated>2025-07-31T09:48:35+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2025-07-29T05:47:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fbea5117e22cdd8c26c814dbfbd8e5a5ad43735a'/>
<id>urn:sha1:fbea5117e22cdd8c26c814dbfbd8e5a5ad43735a</id>
<content type='text'>
(From OE-Core rev: 8246f879dcfb9ed2d674dfbc3590769ecef31a74)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: Fix fma steering segfault due to on aarch64</title>
<updated>2025-07-28T13:51:50+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2025-07-22T20:09:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c148c8fc796fb781262ef5cf4604bfa7345f9265'/>
<id>urn:sha1:c148c8fc796fb781262ef5cf4604bfa7345f9265</id>
<content type='text'>
Seen with opengl-es-cts compilation for qemuarm64

(From OE-Core rev: 79fb0c1a73e659f32bd5d86d84c583233d09e473)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: Tweak libtool patch documentation</title>
<updated>2025-07-14T16:49:48+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-07-11T15:32:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1d723321a74df73bc9e3bf0845526672dd593d48'/>
<id>urn:sha1:1d723321a74df73bc9e3bf0845526672dd593d48</id>
<content type='text'>
Update the libtool patch description with a note about the patch not
being essential now due to .la file handling changes.

(From OE-Core rev: 1294542edf327fe782b5b9c0de3dd3d3c2e38af1)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
