[ldv-project] Problem with recent LDV version

[Alexander von Rhein]

Hi Evgeny,

thank you, the submodule update works.
Now I have another problem while installing LDV ("install-all").
I think the makefile in
ri/cif/aspectator-build/x86_64-unknown-linux-gnu/libgcc
calls the linker and it does not find the crti.o file in my system.

/usr/bin/ld: cannot find crti.o: No such file or directory
collect2: ld returned 1 exit status
make[6]: *** [libgcc_s.so] Error 1
make[6]: Leaving directory 
`/home/rhein/LDV/ldv-tools/ri/cif/aspectator-build/x86_64-unknown-linux-gnu/libgcc'
make[5]: *** [all-stage1-target-libgcc] Error 2

I had a similar problem with previous versions of LDV.
Those problems could be fixed by exporting the right path in variable 
LIBRARY_PATH
export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
However, that does not work anymore.

BTW, where can I register for this mailing list?

greetings,
Alex

This is the call to LD (from the LDV output):
/bin/bash ../../../aspectator/libgcc/../mkinstalldirs .
/home/rhein/LDV/ldv-tools/ri/cif/aspectator-build/./gcc/xgcc 
-B/home/rhein/LDV/ldv-tools/ri/cif/aspectator-build/./gcc/ 
-B/home/rhein/LDV/ldv-tools/ri/cif/aspectator-bin/x86_64-unknown-linux-gnu/bin/ 
-B/home/rhein/LDV/ldv-tools/ri/cif/aspectator-bin/x86_64-unknown-linux-gnu/lib/ 
-isystem 
/home/rhein/LDV/ldv-tools/ri/cif/aspectator-bin/x86_64-unknown-linux-gnu/include 
-isystem 
/home/rhein/LDV/ldv-tools/ri/cif/aspectator-bin/x86_64-unknown-linux-gnu/sys-include 
-O2  -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wcast-qual 
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem 
./include  -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 
-D__GCC_FLOAT_NOT_NEEDED -fno-stack-protector  -shared -nodefaultlibs 
-Wl,--soname=libgcc_s.so.1 -Wl,--version-script=libgcc.map -o 
./libgcc_s.so.1.tmp -g -O2 -B./ _muldi3_s.o _negdi2_s.o _lshrdi3_s.o 
_ashldi3_s.o _ashrdi3_s.o _cmpdi2_s.o _ucmpdi2_s.o _clear_cache_s.o 
_enable_execute_stack_s.o _trampoline_s.o __main_s.o _absvsi2_s.o 
_absvdi2_s.o _addvsi3_s.o _addvdi3_s.o _subvsi3_s.o _subvdi3_s.o 
_mulvsi3_s.o _mulvdi3_s.o _negvsi2_s.o _negvdi2_s.o _ctors_s.o 
_ffssi2_s.o _ffsdi2_s.o _clz_s.o _clzsi2_s.o _clzdi2_s.o _ctzsi2_s.o 
_ctzdi2_s.o _popcount_tab_s.o _popcountsi2_s.o _popcountdi2_s.o 
_paritysi2_s.o _paritydi2_s.o _powisf2_s.o _powidf2_s.o _powixf2_s.o 
_mulsc3_s.o _muldc3_s.o _mulxc3_s.o _divsc3_s.o _divdc3_s.o _divxc3_s.o 
_bswapsi2_s.o _bswapdi2_s.o _fixunssfsi_s.o _fixunsdfsi_s.o 
_fixunsxfsi_s.o _fixsfdi_s.o _fixdfdi_s.o _fixxfdi_s.o _fixunssfdi_s.o 
_fixunsdfdi_s.o _fixunsxfdi_s.o _floatdisf_s.o _floatdidf_s.o 
_floatdixf_s.o _floatundisf_s.o _floatundidf_s.o _floatundixf_s.o 
_divdi3_s.o _moddi3_s.o _udivdi3_s.o _umoddi3_s.o _udiv_w_sdiv_s.o 
_udivmoddi4_s.o addtf3_s.o divtf3_s.o multf3_s.o negtf2_s.o subtf3_s.o 
unordtf2_s.o fixtfsi_s.o fixunstfsi_s.o floatsitf_s.o floatunsitf_s.o 
fixtfdi_s.o fixunstfdi_s.o floatditf_s.o floatunditf_s.o fixtfti_s.o 
fixunstfti_s.o floattitf_s.o floatuntitf_s.o extendsftf2_s.o 
extenddftf2_s.o extendxftf2_s.o trunctfsf2_s.o trunctfdf2_s.o 
trunctfxf2_s.o getf2_s.o letf2_s.o eqtf2_s.o _divtc3_s.o _multc3_s.o 
_powitf2_s.o unwind-dw2_s.o unwind-dw2-fde-glibc_s.o unwind-sjlj_s.o 
gthr-gnat_s.o unwind-c_s.o emutls_s.o -lc && rm -f ./libgcc_s.so && if [ 
-f ./libgcc_s.so.1 ]; then mv -f ./libgcc_s.so.1 ./libgcc_s.so.1.backup; 
else true; fi && mv ./libgcc_s.so.1.tmp ./libgcc_s.so.1 && ln -s 
libgcc_s.so.1 ./libgcc_s.so

On 10/30/2012 12:02 PM, Evgeny Novikov wrote:
> Hi Alex,
>
> we have changed several GIT submodules included into LDV tools. In 
> case of updating from old LDV sources you have to run:
> git submodule update --init --recursive.
> and then install LDV tools as usual. I hope that this will help you. 
> Note that new commits (but not changes in submodules themselves) 
> appear in submodules rather often and I recommend you to update them 
> after each pull. I saw GIT documentation for pull command. There is 
> option --recurse-submodules that can help you (but I didn't test it 
> myself).
>
> BTW, I guess that we (I mean the LDV team first of all) should make 
> announcements to the LDV public mailing list 
> (ldv-project at linuxtesting.org) when things like that happen. Otherwise 
> all users of LDV tools will encounter such the problems sooner or later.
>
> May be it would be better to continue our discussion about LDV with 
> #ifdef variability in that public list as well, because of it may be 
> interesting for other people.
>
> On 10/30/2012 12:32 PM, Alexander von Rhein wrote:
>> Hi Evgeny,
>>
>> I just pulled the current LDV version and it does not build any more.
>> I think the problem must be introduced in a recent commit.
>>
>> make[1]: Entering directory `/home/rhein/LDV/ldv-tools/ri'
>> Begin to install CIF
>> prefix=/home/rhein/LDV/installation/ri make -C cif install
>> make[2]: Entering directory `/home/rhein/LDV/ldv-tools/ri/cif'
>> make[2]: *** No rule to make target `install'.  Stop.
>> make[2]: Leaving directory `/home/rhein/LDV/ldv-tools/ri/cif'
>> make[1]: *** [install] Error 2
>> make[1]: Leaving directory `/home/rhein/LDV/ldv-tools/ri'
>> make: *** [ri-subdir-install] Error 2
>>
>> The "ri/cif" folder is empty.
>>
>> greetings,
>> Alex
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20121030/2f2f2243/attachment.html>