On 28 October 2016 at 15:57, Michael Tokarev wrote:
> 17.10.2016 07:43, Stefan Weil wrote:
>> Am 16.10.2016 um 21:04 schrieb Peter Maydell:
>>> On 16 October 2016 at 15:31, Michael Tokarev wrote:
13.10.2016 21:29, Stefan Weil wrote:
> scripts/tracetool generates a C preprocessor macro fr
17.10.2016 07:43, Stefan Weil wrote:
> Am 16.10.2016 um 21:04 schrieb Peter Maydell:
>> On 16 October 2016 at 15:31, Michael Tokarev wrote:
>>> 13.10.2016 21:29, Stefan Weil wrote:
scripts/tracetool generates a C preprocessor macro from the name of the
build directory. Any characters whi
Am 16.10.2016 um 21:04 schrieb Peter Maydell:
On 16 October 2016 at 15:31, Michael Tokarev wrote:
13.10.2016 21:29, Stefan Weil wrote:
scripts/tracetool generates a C preprocessor macro from the name of the
build directory. Any characters which are possible in a directory name
but not allowed
On 16 October 2016 at 15:31, Michael Tokarev wrote:
> 13.10.2016 21:29, Stefan Weil wrote:
>> scripts/tracetool generates a C preprocessor macro from the name of the
>> build directory. Any characters which are possible in a directory name
>> but not allowed in a macro name must be substituted, ot
13.10.2016 21:29, Stefan Weil wrote:
> scripts/tracetool generates a C preprocessor macro from the name of the
> build directory. Any characters which are possible in a directory name
> but not allowed in a macro name must be substituted, otherwise builds
> will fail.
Applied to -trivial, thank yo
On Fri, Oct 14, 2016 at 10:05:18PM +0200, Stefan Weil wrote:
> On 10/14/16 12:01, Stefan Hajnoczi wrote:
> > dirname should only contain QEMU source tree subdirectory paths (e.g.
> > hw/net). How did you get a comma in there?
> >
> > I tried an out-of-tree build in a directory called 'a,b' but it
On 10/14/16 12:01, Stefan Hajnoczi wrote:
dirname should only contain QEMU source tree subdirectory paths (e.g.
hw/net). How did you get a comma in there?
I tried an out-of-tree build in a directory called 'a,b' but it doesn't
trigger the issue.
I'd like to understand how to reproduce the prob
On 14/10/2016 11:53, Stefan Hajnoczi wrote:
> > Why does it need to care about the build directory name at all?
> > Ideally builds should be entirely deterministically reproducible
> > whatever the path to the source or build directory names is...
>
> It's trying to construct the relative path fr
On Thu, Oct 13, 2016 at 08:29:30PM +0200, Stefan Weil wrote:
> scripts/tracetool generates a C preprocessor macro from the name of the
> build directory. Any characters which are possible in a directory name
> but not allowed in a macro name must be substituted, otherwise builds
> will fail.
>
> S
On Thu, Oct 13, 2016 at 07:36:07PM +0100, Peter Maydell wrote:
> On 13 October 2016 at 19:29, Stefan Weil wrote:
> > scripts/tracetool generates a C preprocessor macro from the name of the
> > build directory. Any characters which are possible in a directory name
> > but not allowed in a macro nam
On 13 October 2016 at 19:29, Stefan Weil wrote:
> scripts/tracetool generates a C preprocessor macro from the name of the
> build directory. Any characters which are possible in a directory name
> but not allowed in a macro name must be substituted, otherwise builds
> will fail.
>
> Signed-off-by:
scripts/tracetool generates a C preprocessor macro from the name of the
build directory. Any characters which are possible in a directory name
but not allowed in a macro name must be substituted, otherwise builds
will fail.
Signed-off-by: Stefan Weil
---
I had problems with a build directory of
12 matches
Mail list logo
