FS#66889 - Set FFLAGS for debug package

Attached to Project: Pacman
Opened by Yichao Yu (yuyichao) - Thursday, 04 June 2020, 03:33 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 December 2022, 10:43 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Eli Schwartz (eschwartz)
Architecture All
Severity Low
Priority Normal
Reported Version 5.2.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

Fortran sourrce file does not seem to be installed to the correct place in a debug package. Manually setting `-fdebug-prefix-map` for a fortran package (openblas) fixes the paths of source file so I think it should be enough to add it to `DEBUG_FFLAGS`/`FFLAGS` in `buildenv/debugflags.sh`.

Steps to Reproduce:
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 04 December 2022, 10:43 GMT
Reason for closing:  None
Additional comments about closing:  Moved to gitlab:
https://gitlab.archlinux.org/pacman/pacm an/-/issues/3
Comment by Eli Schwartz (eschwartz) - Thursday, 04 June 2020, 03:39 GMT
That sounds like something useful to do -- currently we don't handle FFLAGS at all though.
Comment by Yichao Yu (yuyichao) - Thursday, 04 June 2020, 03:54 GMT
I assume it can be added without a major change since `RUSTFLAGS` was there (and it seems that you added it last october)... I didn' realize that it has also been added to other places though, since the one actually packaged (https://git.archlinux.org/svntogit/packages.git/tree/trunk/makepkg.conf?h=packages/pacman) doesn't have it = = ....


P.S. is the pacman package intentially shipping a different makepkg.conf than the one in the pacman repo?
Comment by Eli Schwartz (eschwartz) - Thursday, 11 June 2020, 02:55 GMT
Generally the package should ship one that parallels the pacman repo, though the package does define some vendor options that aren't in git. Really, the one in the package should mention RUSTFLAGS even if it is commented out. o_0

Loading...