On 2011-04-09 23:13, Michael Walle wrote:
> There is a bug in nvidia's binary GPU driver, which causes a segmentation
> fault if linked to libGL.
>
> Signed-off-by: Michael Walle
> ---
> configure |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/configure b/configur
On Thu, Apr 07, 2011 at 09:31:24AM +0200, Paolo Bonzini wrote:
> On 04/07/2011 07:12 AM, Mike Frysinger wrote:
> > Standard autoconf scripts include a --version flag so people can easily
> > query things. Add this to qemu's configure so it too can integrate with
> > build systems that have standar
On 04/07/2011 07:12 AM, Mike Frysinger wrote:
Standard autoconf scripts include a --version flag so people can easily
query things. Add this to qemu's configure so it too can integrate with
build systems that have standard autotool helpers.
Signed-off-by: Mike Frysinger
ACK
Paolo
Am 15.11.2010 21:22, schrieb Stefan Weil:
With the previous patches, hopefully all functions with
printf like arguments use gcc's format checking.
This was tested with default build configuration on linux
and windows hosts (including some cross compilations),
so chances are good that there remai
Thanks, applied.
On Thu, Oct 14, 2010 at 9:19 AM, Markus Armbruster wrote:
> -Wall enables a bunch of warnings at once. configure puts it after
> $gcc_flags. This makes it impossible to disable warnings enabled by
> -Wall there. Fix by putting configured flags last.
>
> Signed-off-by: Markus A
On 10/07/10 17:58, Stefan Weil wrote:
pkg-config is not always available (e.g. on win32 hosts),
but we don't want to see the 'command not found' error message.
compile_object() {
+ echo>>config.log
+ cat $TMPC>>config.log
+ echo>>config.log
This looks unrelated.
@@ -28,6 +31,9 @@ comp
Am 07.10.2010 21:05, schrieb Gerd Hoffmann:
On 10/07/10 17:58, Stefan Weil wrote:
pkg-config is not always available (e.g. on win32 hosts),
but we don't want to see the 'command not found' error message.
compile_object() {
+ echo>>config.log
+ cat $TMPC>>config.log
+ echo>>config.log
T
On Sat, Jun 12, 2010 at 07:57:52PM +0200, Paolo Bonzini wrote:
> On 06/12/2010 06:44 PM, Jan Kiszka wrote:
> >>Yes, but only for this line. What I mean is something more generic
> >>like:
> >>
> >>"#"*) # comment
> >> continue
> >> ;;
> >>
> >
> >IMO, that would only paper over suboptimally
On 06/12/2010 06:44 PM, Jan Kiszka wrote:
Yes, but only for this line. What I mean is something more generic
like:
"#"*) # comment
continue
;;
IMO, that would only paper over suboptimally expressed patterns for the
other line evaluations.
Agreed. I like Jan's patch more.
Paolo
Stefan Weil wrote:
> Signed-off-by: Stefan Weil
Ouch. good catch.
Acked-by: Juan Quintela
> ---
> configure |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/configure b/configure
> index dfe3e42..a14aba7 100755
> --- a/configure
> +++ b/configure
> @@ -1091,8
On Wed, Nov 11, 2009 at 01:49:06PM +0100, Juan Quintela wrote:
> "Michael S. Tsirkin" wrote:
>
> Hi
>
> > @@ -1585,7 +1605,7 @@ int main(void)
> > return 0;
> > }
> > EOF
> > -if $cc $ARCH_CFLAGS -o $TMPE $TMPC 2> /dev/null ; then
> > +if compile_prog "$ARCH_CFLAGS" "" ; then
>
> s/$ARCH
Thiemo Seufer <[EMAIL PROTECTED]> writes:
> Joachim Henke wrote:
>> On Wed, 2007-05-09 at 10:51 +0200, Juergen Keil wrote:
>> > Isn't the use of "which" wrong, anyway?
>> >
>> > "which" belongs to csh/tcsh, and tells you about csh's/tcsh's idea
>> > about a command or a csh command alias.
>> >
12 matches
Mail list logo
