Compile after git pull but without make Clean/distclean a (when source file structure changed)

Source: Internet
Author: User
 http://lists.nongnu.org/archive/html/qemu-devel/2013-03/msg01559.html on 10.03.2013 18:04, Peter Maydell wrote: 

Oh, right. Tracing functions moved from trace.h to the "the" files in the trace/subdirectory. This means so if you didn ' t does a make clean ordistclean before doing the git update then the new makefile About the old trace.h file and so won ' t delete it, but Thecompiler could still pull it in anyhow. However This happened a long back which be why I didn ' t mention it as a possibility (it was discussed on the list at The time as a number of people including Meran into it). If you remove all the files:trace.c trace.h Trace.c-timestamp Trace.h-timestamp This should resolve the problem. This is a example of a longstanding problem we have where the makefile ' s dependency rules aren ' t able to cope with Chang Es to TheProject source file structure, and I clean, distclean and incremental build sometimes breaks a git update . I am pretty intractable as a problem to solve; You can mitigate it through doing allyour builds in a builds directory rather than in the source tree ITself, since then you can always just delete the whole builds tree toget a definite.

Rm-f trace.c trace.h libcacard/trace.c find
.-name \*-timestamp-exec rm-f {} \;
Make Distclean make clean
./configure--target-list=x86_64-softmmu

# No files found find
.-name \*- Timestamp

# No files found find
.-name trace.c

# Under git version control:
#./include/trace.h
Fin D. -name trace.h

=> worked

But shouldn ' t "make Distclean" does the job correctly (even with a changed directory structure, in least for some time)?
Ciao,
Gerhard


There ' s also
$ git reset--hard
$ git clean-fdx
$./configure

Laszlo

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.