RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1582545 - GNU Make 3.82 generates an error "*** mixed implicit and normal rules. Stop." that does not exist is 3.81 or 4.1
Summary: GNU Make 3.82 generates an error "*** mixed implicit and normal rules. Stop."...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: make
Version: 7.4
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: DJ Delorie
QA Contact: Michal Kolar
Vladimír Slávik
URL:
Whiteboard:
Depends On:
Blocks: 1594286 1643040
TreeView+ depends on / blocked
 
Reported: 2018-05-25 14:19 UTC by Alan Matsuoka
Modified: 2019-08-06 12:39 UTC (History)
8 users (show)

Fixed In Version: make-3.82-24
Doc Type: Bug Fix
Doc Text:
.Makefiles containing explicit targets before implicit work again Previously, mixing implicit (pattern) and explicit targets in Makefiles was deprecated. After update to version 3.82, the `make` build tool returned errors for mixed targets. As a consequence, legacy Makefiles containing mixed targets could not be used. With this update, `make` can correctly parse situations where an explicit target is listed before an implicit target. As a result, certain legacy Makefiles can now be used again without modification. However, implicit targets before explicit targets still result in an error. Note that mixing explicit and implicit targets in Makefiles is deprecated and should *not* be added to new Makefiles.
Clone Of:
Environment:
Last Closed: 2019-08-06 12:39:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
patch that fixes problem (552 bytes, patch)
2018-05-25 14:19 UTC, Alan Matsuoka 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
GNU Savannah 33034 0 None None None 2018-05-28 11:49:43 UTC
Red Hat Product Errata RHBA-2019:2056 0 None None None 2019-08-06 12:39:37 UTC

Description Alan Matsuoka 2018-05-25 14:19:10 UTC 
Created attachment 1441589 [details]
patch that fixes problem

Description of problem:
Build with GNU make 3.82 fails due to "*** mixed implicit and normal rules.  Stop." However, the same source code and makefiles build successfully with GNU make 3.81 and 4.1. It appears make 3.82 introduced a bug that complains about multiple targets in a make rules:


Where are you experiencing the behavior?  What environment?

Build failure during cross compilation of Linux kernel 2.6.35 for PowerPC.



Version-Release number of selected component (if applicable):

GNU make 3.82: Always
GNU make 3.81: Never
GNU make 41.: Never

How reproducible:


Steps to Reproduce:
1.[nuevo] make CROSS_COMPILE=/opt/powerpc-idirect-linux-gnuspe-4.9/bin/powerpc-idirect-linux-gnuspe- AS=/opt/powerpc-idirect-linux-gnuspe-4.9/bin/powerpc-idirect-linux-gnuspe-as -C linux-2.6.35 ARCH=powerpc oldconfig
[nuevo] make[3]: Entering directory `/builds/workspace/feature_mhassani_VELO-10068-T2FQTEFW4KOSKC2S3ITYUZ446YAO564ZYWAVUXX2XH6E3TKA3MRQ/freescale/kernel/linux-2.6.35'
[nuevo] /builds/workspace/feature_mhassani_VELO-10068-T2FQTEFW4KOSKC2S3ITYUZ446YAO564ZYWAVUXX2XH6E3TKA3MRQ/freescale/kernel/linux-2.6.35/arch/powerpc/Makefile:188: *** mixed implicit and normal rules.  Stop.
[nuevo] make[3]: Leaving directory `/builds/workspace/feature_mhassani_VELO-10068-T2FQTEFW4KOSKC2S3ITYUZ446YAO564ZYWAVUXX2XH6E3TKA3MRQ/freescale/kernel/linux-2.6.35'
[nuevo] make[2]: *** [build_kernel] Error 2
[nuevo] make[2]: Leaving directory `/builds/workspace/feature_mhassani_VELO-10068-T2FQTEFW4KOSKC2S3ITYUZ446YAO564ZYWAVUXX2XH6E3TKA3MRQ/freescale/kernel'
[nuevo] make[1]: *** [build_kernel] Error 2
[nuevo] make[1]: Leaving directory `/builds/workspace/feature_mhassani_VELO-10068-T2FQTEFW4KOSKC2S3ITYUZ446YAO564ZYWAVUXX2XH6E3TKA3MRQ'
[nuevo] make: *** [fast] Error 2

The error point to the following lines in Makefile:
BOOT_TARGETS = zImage zImage.initrd uImage zImage% dtbImage% treeImage.% cuImage.% simpleImage.%

PHONY += $(BOOT_TARGETS)

$(BOOT_TARGETS): vmlinux
	$(Q)$(MAKE) ARCH=ppc64 $(build)=$(boot) $(patsubst %,$(boot)/%,$@)

bootwrapper_install %.dtb:
	$(Q)$(MAKE) ARCH=ppc64 $(build)=$(boot) $(patsubst %,$(boot)/%,$@)


Actual results:
Failure

Expected results:

Make should complete.

Additional info:
see http://savannah.gnu.org/bugs/?33034
Comment 5 Michal Kolar 2019-01-03 09:18:44 UTC 
Reproduced against make-3.82-23.el7 and verified against make-3.82-24.el7.
Comment 9 errata-xmlrpc 2019-08-06 12:39:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2056
Note You need to log in before you can comment on or make changes to this bug.