Bug 924665

Summary:	dev-db/libiodbc-3.52.15-r1 fails to compile: SQLRemoveDSNFromIni.c:87:13: error: type of ValidDSNW does not match original declaration [-Werror=lto-type-mismatch]
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	Current packages	Assignee:	No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed>
Status:	RESOLVED FIXED
Severity:	normal	CC:	eschwartz
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://github.com/openlink/iODBC/issues/100
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	618550
Attachments:	build.log

Description Agostino Sarubbo gentoo-dev

2024-02-15 16:00:23 UTC

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-db/libiodbc-3.52.15-r1 fails to compile.
Discovered on: amd64 (internal ref: lto_tinderbox)
System: LTO-SYSTEM (https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#LTO)

Info about the issue:
https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0014

Comment 1 Agostino Sarubbo gentoo-dev

2024-02-15 16:00:25 UTC

Created attachment 885051 [details]
build.log

build log and emerge --info

Comment 2 Larry the Git Cow gentoo-dev

2024-03-05 04:48:46 UTC

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b5b7e0e12cecdc1c58742dd05a1033089470c974

commit b5b7e0e12cecdc1c58742dd05a1033089470c974
Author:     Eli Schwartz <eschwartz93@gmail.com>
AuthorDate: 2024-03-05 01:31:58 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2024-03-05 04:47:50 +0000

    dev-db/libiodbc: mark as LTO-unsafe
    
    Closes: https://bugs.gentoo.org/924665
    Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
    Signed-off-by: Sam James <sam@gentoo.org>

 dev-db/libiodbc/libiodbc-3.52.15-r1.ebuild | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

Comment 3 Eli Schwartz gentoo-dev

2024-03-05 17:34:01 UTC

Upstream has committed a fix in git develop, so we should be able to remove our local workaround on the next version bump.