Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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#46934 - [xorg-xrdb] use cpp instead of mcpp
Attached to Project:
Arch Linux
Opened by Daniel Hahler (blueyed) - Sunday, 01 November 2015, 00:24 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 14 January 2016, 21:02 GMT
Opened by Daniel Hahler (blueyed) - Sunday, 01 November 2015, 00:24 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 14 January 2016, 21:02 GMT
|
DetailsI've noticed that Arch's xrdb will behave different from Ubuntu/Debian's, and
that seems to be caused by using `--with-cpp=/usr/bin/mcpp`. Is there a specific reason for this? Size? (I've found https://github.com/NixOS/nixpkgs/pull/9501, where it was changed to mcpp in NixOS) XRDB(1) mentions that it was designed to use CPP. The differences are (at least): 1. you have to use `xrdb -I$HOME`, for relative `#include`s to work, but usually only `xrdb -merge ~/.Xresources` is used in desktop managers etc. 2. The following keybindings for urxvt do not work with Arch's xrdb. They are meant to change colors (between light/dark Solarized variants), but the constants (defined in an include `#include ".dotfiles/lib/solarized-xresources/Xresources.dark"`) appear to not be available here: URxvt.keysym.M-C-8: command:\033]11;S_base3\007\033]10;S_base00\007\033]12;S_base01\007\033]13;S_base01\007\033]708;S_base3\007 URxvt.keysym.M-C-9: command:\033]11;S_base03\007\033]10;S_base0\007\033]12;S_base1\007\033]13;S_base1\007\033]708;S_base03\007 |
This task depends upon
You have not the choice of your desired preprocessor. This should solve your issue.
Technically I'm not sure why mcpp fails for you. You could get in contact with its upstream maintainer. Maybe some standards aren't properly supported anymore: http://mcpp.sourceforge.net/ .
gcc is in core so mcpp will never be used when both are loaded. Should be --with-cpp=/usr/bin/mcpp,/usr/bin/cpp
Also, having both gcc and mcpp optional means neither will necessarily be loaded. Better solution would be to require cpp and have both gcc and mcpp provide cpp.
And no, xrdb doesn't need any preprocessor at all.
Adding provides for both preprocessors is overkill to me. Allan, any opinion?