Description of problem: 1) Configure fails if the value of RPM variable %{distribution} consists of more than 1 word. When parsing the args list of configure the second word is taken as an argument of configure (outside "-Dcf_by=%{distribution}" value) and all the following args are ignored. What is generated is wrong. Solution: turn -Dcf_by=%{distribution} into -Dcf_by="%{distribution}" 2) A 2nd install immediately following a first one (without anything else in between) fails because the directory created by the 1st install is not removed and cmds such as "ln -s" (without "f") or "mkdir" (without "-p") fail Solution: either remove build root as the 1st operation or turn some "ln -s" into "ln -sf" and "mkdir" into "mkdir -p" 3) Test of perl fails if built with static libperl (as a consequence of point 1) because of many undefined symbols from perl modules used in rebuilding the just deleted perl (CCDLFLAGS is empty : "-Wl,E" is not used by the rebuild and needed symbols are no more exported). If libperl is a dynamic library, deleting and rebuilding perl before (and after) test is useless because LD_LIBRARY_PATH is set to the right value (which override the "rpath" if any). See the value of "RUN_PERL" and LDLIBPTH" in Makefile (they are used to start the tests) Solution: the content of "%check" can be as simple as 'RPM_BUILD_ROOT="" TEST_JOBS=%{nbprocs} make test_harness_notty'. This works fine in both cases (static or dynamic libperl) Version-Release number of selected component (if applicable): 5.16.3-1.mga3 (and may be beyond) How reproducible: Very easily Steps to Reproduce: 1.Start a perl rebuild using a 2 words value for "%{distribution}" (points 1 & 3) 2.Try 2 consecutive install operation (point 2) 3. Reproducible: Steps to Reproduce:
looks also valid in cauldron (regarding spec)
Keywords: (none) => TriagedAssignee: bugsquad => jquelin
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD