Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
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
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
|
DetailsSummary 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
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
P.S. is the pacman package intentially shipping a different makepkg.conf than the one in the pacman repo?