Does AC_PATH_XTRA (an autoconf macro used in configure.ac to figure out X library and include paths) cause problems with modular xorg? From the autoconf info page it looks like it uses xmkmf to work its magic. Is this information current? If so, this would leave me with several options: 1) BuildRequire: imake This will bring in xmkmf so that AC_PATH_XTRA will work. Since xmkmf and imake are on the way out and pkgconfig is on the way in, this doesn't seem like the right thing to do. 2) In the package's spec, use: %configure --x-includes/x-libraries=<pkg-config output> This seems to be driving in the right direction but isn't suitable for sending upstream. 3) Modify the configure.ac to use pkg-config. In order to go upstream, this would need some sort of conditional in order to do a traditional AC_PATH_X type check in case of older X releases. Have other people run into this type of problem in their packages yet? Any pointers to a better way of handling it? -Toshio
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
