All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Scanandoah <k2zn@rochester.rr.com>
To: Alex Flinsch <avflinsch@att.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: Any glfer users?
Date: Sun, 16 Apr 2006 18:32:57 -0400	[thread overview]
Message-ID: <4442C619.5030801@rochester.rr.com> (raw)
In-Reply-To: <190E15D0-BFED-42F9-9216-7E53F5E25366@att.net>

It looks like it may be getting closer, but still no cigar.  The error 
messages have changed.

I didn't have any problems with glfer back when I ran Mandrake, but I 
could never get all my HW to play well together.


al@linux:~/glfer-0.3.4> make
make  all-am
make[1]: Entering directory `/home/al/glfer-0.3.4'
if gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/include/cairo 
-I/usr/include/freetype2 -I/usr/X11R6/include -I/usr/include/libpng12 
-I/opt/gnome/include/gtk-2.0 -I/opt/gnome/lib/gtk-2.0/include 
-I/opt/gnome/include/atk-1.0 -I/opt/gnome/include/pango-1.0 
-I/opt/gnome/include/glib-2.0 -I/opt/gnome/lib/glib-2.0/include 
-ggdb -O2 -Wall -MT g_main.o -MD -MP -MF ".deps/g_main.Tpo" -c -o 
g_main.o g_main.c; \
then mv -f ".deps/g_main.Tpo" ".deps/g_main.Po"; else rm -f 
".deps/g_main.Tpo"; exit 1; fi
In file included from g_main.c:34:
g_save_image.h:25: error: conflicting types for 
‘gdk_pixbuf_get_from_drawable’
/opt/gnome/include/gtk-2.0/gdk/gdkpixbuf.h:97: error: previous 
declaration of ‘gdk_pixbuf_get_from_drawable’ was here
g_main.c: In function ‘get_main_menu’:
g_main.c:151: warning: implicit declaration of function 
‘gtk_accel_group_attach’
g_main.c: In function ‘spect_save_ok’:
g_main.c:182: warning: assignment discards qualifiers from pointer 
target type
g_main.c: In function ‘open_file_ok’:
g_main.c:206: warning: assignment discards qualifiers from pointer 
target type
make[1]: *** [g_main.o] Error 1
make[1]: Leaving directory `/home/al/glfer-0.3.4'
make: *** [all] Error 2
al@linux:~/glfer-0.3.4>

Alex Flinsch wrote:
> 
> On Apr 16, 2006, at 1:13 PM, Al Scanandoah wrote:
> 
>>
>> g_main.c: In function ‘save_full_pixmap’:
>> g_main.c:1037: warning: pointer targets in passing argument 3 of 
>> ‘write_jpeg_file’ differ in signedness
>> make[1]: *** [g_main.o] Error 1
>> make[1]: Leaving directory `/home/al/glfer-0.3.4'
>> make: *** [all] Error 2
>> al@linux:~/glfer-0.3.4>
>>
>>
>> Has anyone encountered this before?
> 
> This compiles just fine on my mandrake system... but I have seen this 
> error before
> change the define of  write_jpeg_file in g_save_image.h and g_save_image.c
> from (char *filename, int quality, char *image_buffer, int image_width, 
> int image_height)
> to     (char *filename, int quality, guchar *image_buffer, int 
> image_width, int image_height)
> 
> and it should work
> 
> 
> -- 
> Alex / AB2RC
> avflinsch@att.net
> 
> 
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-04-16 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-16 17:13 Any glfer users? Al Scanandoah
2006-04-16 18:24 ` Alex Flinsch
2006-04-16 22:32   ` Al Scanandoah [this message]
2006-04-17  5:29     ` Joop Stakenborg
2006-04-17 22:40       ` Al Scanandoah

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=4442C619.5030801@rochester.rr.com \
    --to=k2zn@rochester.rr.com \
    --cc=avflinsch@att.net \
    --cc=linux-hams@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.