Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: MKDEBUGLIB set list failure?
>> Hmm. I re-updated src and xsrc, and started with an empty OBJDIR
>> and DESTDIR, but still I get the error(s):
>>
>> ====== 3 missing files in DESTDIR ========
>> Files in flist but missing from DESTDIR.
>> File wasn't installed ?
>> ------------------------------------------
>> ./usr/libdata/debug/usr/bin/lto-dump.debug
>> ./usr/libdata/debug/usr/lib/i386/libi386.so.2.0.debug
>> ./usr/libdata/debug/usr/tests/lib/libstdc++/h_cin_nosync.debug
>> ======== end of 3 missing files ==========
>
> These files should be build and installed with MKDEBUG=yes,
> they are unrelated to MKDEBUGLIB.
Then the bug is probably in the logic which translates from build
flags ("MKDEBUGLIB" / "MKDEBUG") to the attributes to decide
which entries from the set lists to include. I've yet to
(re)find this logic...
> You need to find out why are they not installed in your build.
I thought you implied that setting MKDEBUGLIB should not cause
the above files to be built & installed? But somehow they are
included in the generated set lists anyway?
Regards,
- Håvard
Home |
Main Index |
Thread Index |
Old Index