control -1 close On Tue, Apr 07, 2015 at 04:47:59AM +0200, Guillem Jover wrote: > Hi! > > On Mon, 2015-04-06 at 12:54:33 -0700, Shawn Landden wrote: > > Package: dpkg > > Version: 1.17.24 > > Severity: wishlist > > > clang is a native compiler, and so the gcc way of naming cross-compilers is > > cumbersome as it would require the clang > > package to ship many symlinks. instead the architecture is listed with > > -target > > CC="clang -target $(DEB_HOST_GNU_TYPE)" > > > > Not all software uses autoconf, and also the autoconf auto-detection > > doesn't work with musl-linux-(amd64|armhf|...), > > which doesn't require a differn't gcc, but simply a spec file. > > I think I'm quite confused by this report. How would having > dpkg-buildflags support a CC variable (set to gcc) help when the user > wants to use clang? > > If you want to use clang, then just do: > > $ CC="clang <whatever>" dpkg-buildpackage > > what am I missing? > We talked about this, and what i'm proposing is still not a panacea. Closing. > Thanks, > Guillem
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
