qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org
Subject: Re: [PATCH] ci: build out-of-tree
Date: Wed, 11 Dec 2019 16:07:49 +0100	[thread overview]
Message-ID: <650aa4be-b7be-0150-f6d9-590b9ce1f550@redhat.com> (raw)
In-Reply-To: <be96796e-958f-e51e-6832-b6376e2f9c72@redhat.com>

On 11/12/19 15:50, Thomas Huth wrote:
> On 11/12/2019 15.30, Paolo Bonzini wrote:
>> Most developers are using out-of-tree builds and it was discussed in the past
>> to only allow those.  To prepare for the transition, use out-of-tree builds
>> in all continuous integration jobs.
>>
>> Based on a patch by Marc-André Lureau.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
> [...]
>> diff --git a/.travis.yml b/.travis.yml
>> index 445b064..d259b51 100644
>> --- a/.travis.yml
>> +++ b/.travis.yml
>> @@ -74,8 +74,8 @@ notifications:
>>  
>>  env:
>>    global:
>> -    - SRC_DIR="."
>> -    - BUILD_DIR="."
>> +    - SRC_DIR=".."
>> +    - BUILD_DIR="build"
>>      - BASE_CONFIG="--disable-docs --disable-tools"
>>      - TEST_CMD="make check V=1"
>>      # This is broadly a list of "mainline" softmmu targets which have support across the major distros
>> @@ -192,7 +192,9 @@ matrix:
>>          - CACHE_NAME="${TRAVIS_BRANCH}-linux-clang-sanitize"
>>        compiler: clang
>>        before_script:
>> +        - mkdir -p ${BUILD_DIR} && cd ${BUILD_DIR}
>>          - ./configure ${CONFIG} --extra-cflags="-fsanitize=undefined -Werror" || { cat config.log && exit 1; }
> 
> Don't you want to remove the old line?
> 
>> +        - ${SRC_DIR}/configure ${CONFIG} --extra-cflags="-fsanitize=undefined -Werror" --extra-ldflags="-fsanitize=undefined" || { cat config.log && exit 1; }
>>  
>>  
>>      - env:
>> @@ -323,6 +325,7 @@ matrix:
>>          - CONFIG="--cc=gcc-9 --cxx=g++-9 --disable-pie --disable-linux-user"
>>          - TEST_CMD=""
>>        before_script:
>> +        - mkdir -p ${BUILD_DIR} && cd ${BUILD_DIR}
>>          - ./configure ${CONFIG} --extra-cflags="-g3 -O0 -Wno-error=stringop-truncation -fsanitize=thread -fuse-ld=gold" || { cat config.log && exit 1; }
> 
> That should also use "../configure" (or $SRC_DIR/configure), shouldn't it?
> 
>  Thomas
> 

Yes, I've sent v2.  This was supposed to be --dry-run, sorry for the noise.

Paolo



  reply	other threads:[~2019-12-11 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 14:30 [PATCH] ci: build out-of-tree Paolo Bonzini
2019-12-11 14:50 ` Thomas Huth
2019-12-11 15:07   ` Paolo Bonzini [this message]
2019-12-11 14:52 ` no-reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=650aa4be-b7be-0150-f6d9-590b9ce1f550@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).