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 2102895 - GRASS GIS 8.0.1 and 8.2.0 g.extension module fails to compile some addons
Summary: GRASS GIS 8.0.1 and 8.2.0 g.extension module fails to compile some addons
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: grass
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: markusN
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-30 23:26 UTC by rick
Modified: 2022-07-21 16:38 UTC (History)
6 users (show)

Fixed In Version: grass-8.2.0-2.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-21 16:38:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description rick 2022-06-30 23:26:47 UTC
Description of problem:
module g.extension and g.extension.all fail to compile/install some (but not all) addons

Version-Release number of selected component (if applicable):
affects Grass 8.0.1 and 8.2

How reproducible:
always, but only for some addons

Steps to Reproduce:
1.run g.extension or g.extension.all from either console or gui
2.
3.

Actual results:
Numerous addons fail to compile/install

Expected results:
addons should compile and install

Additional info:
g.extension produces this error message for those addons that fail to compile:

**/usr/bin/ld: cannot open linker script file /builddir/build/BUILD/grass-8.0.1/.package_note-grass-8.0.1-1.fc36.x86_64.ld: No such file or directory**
collect2: error: ld returned 1 exit status
make: *** [/usr/lib64/grass80//include/Make/Module.make:18: /usr/lib64/grass80/bin/r.accumulate] Error 1

This bug had been reported and resolved in a discussion group, and I understood that it had been reported, but I cannot find the bug here or in grass bug tracking.

The problem is resolved in both grass 8.0.1 and grass 8.2 by removing:
""  -Wl,--build-id=sha1 -Wl,-dT,/builddir/build/BUILD/grass-8.0.1/.package_note-grass-8.0.1-1.fc36.x86_64.ld"" from line 78 of /usr/lib64/grass82/include/Make/Platform.make (for grass 8.0.1, substitute /grass82/ with /grass80/.

It should not be necessary to change files within distributed rpm's. Not certain whether this should be reported/fixed here, but since this same bug has found its way in two releases of grass, reporting it upstream as well.

Comment 1 markusN 2022-07-01 08:26:19 UTC
> This bug had been reported and resolved in a discussion group, and I understood that it had been reported, but I cannot find the bug here or in grass bug tracking.

Please add the link or at least some hints concerning the solution.

Comment 2 rick 2022-07-01 08:49:30 UTC
The discussion link is here:
https://ask.fedoraproject.org/t/grass-gis-grass-addons-not-compiling/22117

I'm sorry, to help with testing I should have included the list of addons this affected for me. This is the list:
r.findtheriver
r.quantile.ref
r.hants
r.gdd
r.fuzzy.system
r.univar2
m.gcp.filter
r.out.tiff
v.in.ply
r.regression.series
r.stream.segment
r.resamp.tps
r3.scatterplot
r.crater
r.change.info
r.area
r.colors.contrastbrightness
v.net.salesman.opt
v.label.sa
i.edge
i.wi
r.stream.channel
r.wateroutlet.lessmem
v.surf.mass
i.water
r.scatterplot
r.skyline
r.pi
r.flip
r.series.lwr
v.centerpoint
r.damflood
r.stream.distance
r.fuzzy.logic
i.evapo.senay
r.stream.order
r3.what
r.convergence
r.seasons
i.evapo.zk
r.stream.basins
r.stream.stats
r.stream.snap
v.surf.tps
r.stream.slope
r.massmov
r.soils.texture
r.traveltime
r.surf.idw2
r.vol.dem
v.kriging
r.sim.water.mp
r3.profile
r.hydrodem
v.ellipse
v.area.stats
v.vol.idw
r.fuzzy.set
i.gravity
i.evapo.potrad
r.bitpattern
r.smooth.seg
r.neighborhoodmatrix
r.gwr

Comment 3 markusN 2022-07-01 08:57:50 UTC
> ... the list of addons this affected for me ...

This are the addons written in C (the others are written in Python).

Does anyone know which change to add to the grass.spec file? https://src.fedoraproject.org/rpms/grass/blob/rawhide/f/grass.spec
Or an example from another SPEC file?

Comment 4 rick 2022-07-01 09:02:29 UTC
Please note that this is listed as bug #2472 on OSGeo/grass github

Comment 5 rick 2022-07-01 09:07:15 UTC
Please note that this is listed as bug #2472 on OSGeo/grass github


(In reply to markusN from comment #3)
> > ... the list of addons this affected for me ...
> 
> This are the addons written in C (the others are written in Python).
> 
Please note also that all other addons (which I assume are written in Python) compiled/installed fine with the changes made as noted above to the Platform.make file.

Comment 6 markusN 2022-07-01 09:10:40 UTC
The file to fix is the `grass.spec` file since Platform.make is generated from Platform.make.in during compilation.
The question is how.

This text is not quite clear to me (I am just a volunteer here):
https://fedoraproject.org/wiki/Changes/Package_information_on_ELF_objects

Comment 8 Fedora Update System 2022-07-12 11:55:09 UTC
FEDORA-2022-754fc63af5 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-754fc63af5

Comment 9 Fedora Update System 2022-07-13 01:28:31 UTC
FEDORA-2022-754fc63af5 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-754fc63af5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-754fc63af5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-07-21 16:38:59 UTC
FEDORA-2022-754fc63af5 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


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