Bug#645021: gcc-4.6: build error on REVERSE_CROSS (files in "4.6.1" dir instead of "4.6")
On Oct 11, 2011, at 17:47, Matthias Klose wrote:
> On 10/11/2011 10:49 PM, Kyle Moffett wrote:
>> Source: gcc-4.6
>> Version: 4.6.1-15
>> Severity: wishlist
>>
>> When building in REVERSE_CROSS mode (IE: when trying to build a native
>> compiler for another architecture with an existing cross-compiler, the
>> build fails with the following error:
>>
>> $ apt-get gcc-4.6=4.6.1-15
>> $ ( cd gcc-4.6-4.6.1 && dpkg-buildpackage -apowerpcspe -b -us -uc )
>> [...]
>> dh_movefiles: debian/tmp/usr/lib/gcc/powerpc-linux-gnuspe/4.6/libgcov.a not found (supposed to put it in gcc-4.6)
>>
>> It looks like it is being put in the wrong directory:
>>
>> $ find . -name '*libgcov*'
>> ./gcc-4.6-4.6.1/debian/tmp/usr/lib/gcc/powerpc-linux-gnuspe/4.6.1/libgcov.a
>> ./gcc-4.6-4.6.1/build/powerpc-linux-gnuspe/libgcc/libgcov.a
>> ./gcc-4.6-4.6.1/build/gcc/libgcov.a
>>
>> There seem to have been some similar bugs regarding recent changes to
>> the "gcc -print-file-name" command, EG: #643891, #644849
>>
>> Unfortunately I'm not having any luck figuring out what I need to fix to
>> make this build. Any help would be much appreciated.
>
> is gcc-base-version.diff applied? I think we should build every cross build with
> this patch.
>
> gcc/BASE-VER now does omit the subminor version number. gcc/FULL-VER does have
> it (used to print the version number for gcc --version).
Yeah, gcc-base-version.diff is applied. I should mention, I do get *most*
files in the "4.6" directory. It's just that I get some files in "4.6.1".
Specifically, in debian/tmp/usr/lib/gcc/powerpc-linux-gnuspe/4.6.1:
crtbegin.o
crtbeginS.o
crtbeginT.o
crtend.o
crtendS.o
ecrti.o
ecrtn.o
libgcc.a
libgcc_eh.a
libgcov.a
ncrti.o
ncrtn.o
While everything else is in the "4.6" directory:
collect2
finclude
include/*.h
include-fixed/*.h
install-tools/include
lto-wrapper
lto1
plugin/include/*.h
Cheers,
Kyle Moffett
--
Curious about my work on the Debian powerpcspe port?
I'm keeping a blog here: http://pureperl.blogspot.com/
Reply to: