Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#36125 - Record build environment when building a package

Attached to Project: Arch Linux
Opened by Peter Wu (Lekensteyn) - Friday, 12 July 2013, 21:29 GMT
Last edited by Allan McRae (Allan) - Friday, 12 July 2019, 11:40 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.1.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Arch Linux does not ship with debugging symbols in packages, a discussion on inclusion for that went silent[1].

KDE programs do not often crash, but when they do, I do not have any useful debugging symbols. Today I had KMail crashing out of nothing. The backtrace contained a lot ??? as there are no debugging symbols.

As I do not forsee special debugging repositories, please consider:

* Storing the build environment in a .pkg.tar.xz, consisting of:
- `env`, especially something like CFLAGS)
- version of packages and compiler (or a reference to a set of package versions of base and base-devel)
* Saving the results of builds, Debian has a very nice place, "Developer Information (PTS)"[2] that also links to build logs[3].
* (creating a repo with debugging symbols anyway)
* (creating a debugging package for qt4 and the like)

Discussion is welcome.

This task depends upon

Closed by  Allan McRae (Allan)
Friday, 12 July 2019, 11:40 GMT
Reason for closing:  Implemented
Additional comments about closing:  .BUILDINFO in packages
Comment by Allan McRae (Allan) - Friday, 12 July 2013, 21:49 GMT
CFLAGS are standardised in Arch and the version of packages matter little given you will need to test if the build fails under current conditions to replicate/fix.

Not a pacman issue.
Comment by Peter Wu (Lekensteyn) - Saturday, 13 July 2013, 13:31 GMT
Allan, CFLAGS change over time as do the package versions. I am assuming that if the base environments are equal, then the produced assembly/binaries should also be the same. Things like machine names, kernel version and time may also have an effect on the resulting binaries, but it shouldn't change too much.

A core dump is useless (or hard to debug) if there are no debugging symbols giving a starting point.
Comment by Jelle van der Waa (jelly) - Sunday, 06 January 2019, 10:59 GMT
Necrobump here, we now have a BUILDINFO which solves part of this problem. A separate debug repo is still an todo item.