Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1865074 - nss: FTBFS in Fedora rawhide/f33
Summary: nss: FTBFS in Fedora rawhide/f33
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nss
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daiki Ueno
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-08-03 20:29 UTC by Fedora Release Engineering
Modified: 2020-08-13 12:06 UTC (History)
6 users (show)

Fixed In Version: nss-3.55.0-3.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-13 12:06:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2020-08-03 20:29 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2020-08-03 20:29 UTC, Fedora Release Engineering
no flags Details
state.log (945 bytes, text/plain)
2020-08-03 20:29 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2020-08-03 20:29:31 UTC
nss failed to build from source in Fedora rawhide/f33

https://koji.fedoraproject.org/koji/taskinfo?taskID=48346778


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix nss at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
nss will be orphaned. Before branching of Fedora 34,
nss will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source

Comment 1 Fedora Release Engineering 2020-08-03 20:29:33 UTC
Created attachment 1708413 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Comment 2 Fedora Release Engineering 2020-08-03 20:29:34 UTC
Created attachment 1708414 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2020-08-03 20:29:35 UTC
Created attachment 1708415 [details]
state.log

Comment 4 Daiki Ueno 2020-08-04 14:40:21 UTC
Looks like this is caused by the recent LTO enablement, though the actual errors look like a false-positive:

 alg1485.c: In function 'AppendAVA.constprop':
 alg1485.c:1049:21: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
 alg1485.c:928:10: note: at offset -1 to object 'tmpBuf' with size 2048 declared here
 alg1485.c:1050:21: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
 alg1485.c:928:10: note: at offset -2 to object 'tmpBuf' with size 2048 declared here
 alg1485.c:1051:21: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
 alg1485.c:928:10: note: at offset -3 to object 'tmpBuf' with size 2048 declared here

where tmpBuf is accessed with something like:

 char tmpBuf[TMPBUF_LEN];
 char *end = encodedAVA /* points to tmpBuf */ + nameLen + valueLen;
 end[-1] = '.';

Perhaps we can work it around with explicitly specifying the positive index.

Comment 5 Jeff Law 2020-08-08 17:31:59 UTC
Let me take this in the immediate term.  I'll disable LTO in the immediate term and pull together a testcase for the false positive as that's something we'll want to dig into upstream in GCC.

Comment 6 Ben Cotton 2020-08-11 15:00:51 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 7 Jeff Law 2020-08-11 17:35:18 UTC
I've disabled LTO for nss.  But further work is needed as I'm still seeing failures:

dbmshim.c:8:10: fatal error: mcom_db.h: No such file or directory

The package owner needs to take it from here.

Comment 8 Daiki Ueno 2020-08-13 12:06:38 UTC
Yes, should be fixed now.


Note You need to log in before you can comment on or make changes to this bug.