On lun, giu 16, 2014 at 10:35:51 +0200, Kamil Dudka wrote: > > A while ago I made the Debian libcurl dev packages (those shipping the > > header files) support multi-arch (i.e. the possibility of installing the > > same package from multiple architecture at the same time). This didn't > > quite work as expected partly because of the above reason. > > > > I'm planning to move the libcurl headers from /usr/include to > > /usr/include/<gnu_triplet> but if this could be solved on the libcurl side > > it'd be better I guess. > > > > Another problem I've encountered is that curl-config changes based on the > > architecture it was built on because it embeds the libdir paths (which on > > Debian change from arch to arch because of multi-arch). The --configure > > option is also different. Not sure how this could be fixed though. > > You can redirect 'curl-config --configure' to pkg-config as we do on Fedora: > > http://pkgs.fedoraproject.org/cgit/curl.git/tree/0101-curl-7.32.0-multilib.patch
The problem is that, at least on Debian, pkg-config isn't multi-arch itself, which means that since the -dev packages would depend on it, it would change nothing. The alternative would be to use a Debian-specific way to get the "current" architecture gnu triplet from the curl-config script instead of hard-condig it, but I haven't tried that yet. Cheers
signature.asc
Description: Digital signature
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
