Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 785709 - dev-lang/lazarus-2.2.0 calls ld directly
Summary: dev-lang/lazarus-2.2.0 calls ld directly
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Amy Liffey
URL:
Whiteboard:
Keywords:
: 890477 (view as bug list)
Depends on:
Blocks: tc-directly
  Show dependency tree
 
Reported: 2021-04-25 20:13 UTC by Agostino Sarubbo
Modified: 2023-05-26 01:11 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,108.79 KB, text/plain)
2021-04-25 20:13 UTC, Agostino Sarubbo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2021-04-25 20:13:47 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-lang/lazarus-2.0.6 calls ld directly.
Discovered on: amd64 (internal ref: ci)

NOTE:
As per QA policy, toolchain tools must not be called directly because they can cause issue in cross-compiling and because is not possible use a different LD implementation (like llvm-link). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks].
Comment 1 Agostino Sarubbo gentoo-dev 2021-04-25 20:13:50 UTC
Created attachment 702489 [details]
build.log

build log and emerge --info
Comment 2 Agostino Sarubbo gentoo-dev 2021-04-25 20:13:52 UTC
Possible context of error(s):

Could not find libgcc
Could not find libgcc
Could not find libgcc
Could not find libgcc
Could not find libgcc
Could not find libgcc
Comment 3 Andreas Sturmlechner gentoo-dev 2021-04-25 20:27:16 UTC
I never did anything with 2.0.6.
Comment 4 Agostino Sarubbo gentoo-dev 2022-02-02 16:09:42 UTC
ci has reproduced this issue with version 2.2.0 - Updating summary.
Comment 5 Matt Turner gentoo-dev 2023-05-26 01:11:11 UTC
*** Bug 890477 has been marked as a duplicate of this bug. ***