Am 15.12.2012 14:16, schrieb Roland Stigge: > Hi Matthias, > > On 14/12/12 15:37, Roland Stigge wrote: >> That's what current upstream does in src/gcc/config.gcc: e500-double.h >> is added to the tm_file (list) to make the distinction between v1 and >> default/v2. >> >> If you don't have another suggestion, I would adjust upstream to do >> actually the same, but do via tm_file_list instead of tm_file (as you >> suggested). > > Consider the attached patch: It does the same as the first patch but via > tm_file_list instead of tm_file as described above. (Applying to the > version in unstable, and with the experimental version there is > generally the same issue.)
the chunk for config.gcc is wrong. You have to use tm_file here. > Unfortunately, upon build, this also didn't work: Both tm_file and > tm_file_list don't get passed to t-linux (and the other makefile snippets). > > My conclusion is that the tm_file (_list) passing doesn't work as > intended (including upstream), and considering that all > powerpc-linux-gnuspe(-v1) specific stuff in src/gcc/config/rs6000 is > Debian specific (only in a debian/patch/*) and not working anyway as > described previously, I guess -v1 support is negligible. (Also, can't > test it.) strange, seems to work on other architectures. > For which reason does Debian need to explicitely port to gnuspev1 (when > upstream's port is only bsd specific and obviously not working anyway)? Sure, but then don't define a wrong multiarch name for that case. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50cf1709.5040...@debian.org