During the compile phase for bdetla (version 0.1.0), cc is invoked instead of a CHOST-specific command (like i686-pc-linux-gnu-gcc). This could cause troubles if trying to do, say, a cross-compile and the system cc gets called (since normally it would use the CHOST for the cross compiler). >>> Starting src_compile make -j2 -j1 cc bpatch.cpp -o bpatch -O2 -lstdc++ cc -shared -fPIC -O2 libbdelta.cpp -o libbdelta.so cc bdelta.cpp -o bdelta -O2 -L. -lbdelta -lstdc++ Reproducible: Always Steps to Reproduce: 1. Install bdelta 2. Look at output during compile phase 3. Actual Results: cc is invoked Expected Results: A CHOST-specific compiler name to be invoked
Also, if you look at the Makefile, the package is using its own settings for stuff like CXXFLAGS.
Created attachment 126095 [details] diff bdelta-0.1.0.ebuild bdelta-0.1.0.ebuild.orig Made it so it uses tc-getCC and respects your CXXFLAGS settings. Though, I'm not sure if it should instead modify the Makefile through some sed action (which wouldn't be too difficult either way).
jep you might want to do the makefile modification and send that upstream too, thanks. I have committed your patch for now.
