Bug 12868 - archiver ARCHIVER_MODE[src] = "patched" and ="configured" fails to build. Morty works. Pyro, sumo, master etc fail
Summary: archiver ARCHIVER_MODE[src] = "patched" and ="configured" fails to build. Mo...
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.3.4
Hardware: x86 arm
: Medium+ normal
Target Milestone: 4.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-07-30 19:25 UTC by Sue Wolber
Modified: 2022-06-24 14:38 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
error log 1 of 2 building 'configured' (3.07 KB, text/plain)
2018-10-09 16:44 UTC, Sue Wolber
no flags Details
error log 2 of 2 building 'configured' (19.38 KB, text/plain)
2018-10-09 16:45 UTC, Sue Wolber
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sue Wolber 2018-07-30 19:25:22 UTC
# Steps to reproduce with poky:

git clone git://git.yoctoproject.org/poky
cd poky
git checkout sumo
source oe-init-build-env
cat > archiverConfigured.conf << EOF
INHERIT += "archiver"
ARCHIVER_MODE[src] = "configured"
EOF

bitbake core-image-minimal -R archiverConfigured.conf
# This fails on various packagegroups recipes eg:
[blduser:build]$ bitbake core-image-minimal -R archiverConfigured.conf
WARNING: Host distribution "rhel-7.4" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Parsing recipes: 100% |#########################################################################################################################| Time: 0:00:13
Parsing of 814 .bb files complete (0 cached, 814 parsed). 1282 targets, 44 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.38.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "rhel-7.4"
TARGET_SYS           = "i586-poky-linux"
MACHINE              = "qemux86"
DISTRO               = "poky"
DISTRO_VERSION       = "2.5"
TUNE_FEATURES        = "m32 i586"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp       = "sumo:86aaecf94852c8893770c86183bd6db4d4c61241"

NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/2.1/x86_64-nativesdk-libc.tar.bz2;sha256sum=d43555df8d5a056ef5b20c7d8e0287207974e09df1e969a3e19302c8b4ea6b4b
ERROR: Task do_ar_configured in /var/lib/jenkins/workspace/manual_archiverConfiguredBug/poky/meta/recipes-core/packagegroups/packagegroup-core-standalone-sdk-target.bb depends upon non-existent task do_configure in /var/lib/jenkins/workspace/manual_archiverConfiguredBug/poky/meta/recipes-core/packagegroups/packagegroup-core-standalone-sdk-target.bb
ERROR: Command execution failed: 1

Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


# 'morty' branch of poky works.  pyro, rocko, sumo, master and master-next as of 30 July 2018 all fail.
Comment 1 Ross Burton 2018-09-28 13:45:56 UTC
Patches on the list.
Comment 2 Ross Burton 2018-10-01 15:16:18 UTC
Fixed as of oe-core master fe26382f94d8cb7d2453d9937aee451b757252b8.
Comment 3 Sue Wolber 2018-10-03 21:38:11 UTC
Ross - confirmed with latest 'master', ARCHIVER_MODE[src] = "patched" now works :-)
Remaining issues:
1) ARCHIVER_MODE[src] = "configured"  still fails, you may be planning to drop this capability?
2) kernel and busybox .config files are NOT included in the archives (or if they are, I can't find them in the tarballs)   This is a biggie for me, this is the reason I thought I wanted the '="configured"' option!

In email conversation you had thought the .config files should have been included even with ARCHIVER_MODE[src] = "original"...???
Comment 4 Ross Burton 2018-10-04 09:47:26 UTC
Configure works here, what failure are you seeing?
Comment 5 Ross Burton 2018-10-04 14:48:32 UTC
Marking as NEEDINFO
Comment 6 Sue Wolber 2018-10-04 18:37:40 UTC
git clone git://git.yoctoproject.org/poky
cd poky
git checkout master

git log -2 meta/classes/archiver.bbclass
# Notice your 2 commits are there.  Are there other commits to fix this issue?

source oe-init-build-env
cat > archiverConfigured.conf << EOF
INHERIT += "archiver"
ARCHIVER_MODE[src] = "configured"
EOF

# Bitbake throws warnings on many recipes doing do_configure
# Then bitbake errors ~1813/2970 tasks 
bitbake core-image-minimal -R archiverConfigured.conf
Comment 7 Stephen K Jolley 2018-10-05 17:18:29 UTC
Ross, your question has been answered.  It this satisfactory? If not, please ask the question again and place back in NEEDINFO.
Comment 8 Ross Burton 2018-10-08 13:57:10 UTC
To save my time, what recipe does it fail on for you?
Comment 9 Sue Wolber 2018-10-08 16:48:49 UTC
(In reply to comment #8)
> To save my time, what recipe does it fail on for you?

# this fails:
bitbake core-image-minimal -R archiverConfigured.conf
Comment 10 Ross Burton 2018-10-09 10:53:07 UTC
I meant what recipe fails during the execution.  Sharing the error log would be much appreciated.
Comment 11 Sue Wolber 2018-10-09 16:43:31 UTC
(In reply to comment #10)
> I meant what recipe fails during the execution.  Sharing the error log would
> be much appreciated.

Ok 2 error logs attached
Comment 12 Sue Wolber 2018-10-09 16:44:35 UTC
Created attachment 4377 [details]
error log 1 of 2 building 'configured'
Comment 13 Sue Wolber 2018-10-09 16:45:16 UTC
Created attachment 4378 [details]
error log 2 of 2 building 'configured'
Comment 14 Ross Burton 2020-01-16 16:08:08 UTC
CCing Paul Barker.

Paul: you actually appear to know the archiver. Would you be able to take this? :)
Comment 15 Paul Barker 2020-01-16 22:37:47 UTC
I can take a look at least. There is now selftest coverage for `ARCHIVER_MODE[src] = "configured"` but it only builds for a single recipe to keep the execution time short.
Comment 16 Ross Burton 2022-06-24 14:38:42 UTC
Those failures are in the kernel, which was fixed in oe-core d7776a23cbea836ddb8ac5ec77012af2449ab875.