Building on ubuntu 10.04 LTS fails

Hi, 

I'm trying to build gob-2.0.18 from source tar ball on Ubuntu 10.04 LTS and it fails with the following
messages: 

dev02:~/src/gob2-2.0.18> ./configure 
checking for a BSD-compatible install... /usr/bin/install -c 
checking whether build environment is sane... yes 
checking for a thread-safe mkdir -p... /bin/mkdir -p 
checking for gawk... gawk 
checking whether make sets $(MAKE)... yes 
checking whether to enable maintainer-specific portions of Makefiles... no 
checking for style of include used by make... GNU 
checking for gcc... gcc 
checking whether the C compiler works... yes 
checking for C compiler default output file name... a.out 
checking for suffix of executables... 
checking whether we are cross compiling... no 
checking for suffix of object files... o 
checking whether we are using the GNU C compiler... yes 
checking whether gcc accepts -g... yes 
checking for gcc option to accept ISO C89... none needed 
checking dependency style of gcc... gcc3 
checking for library containing strerror... none required 
checking for gcc... (cached) gcc 
checking whether we are using the GNU C compiler... (cached) yes 
checking whether gcc accepts -g... (cached) yes 
checking for gcc option to accept ISO C89... (cached) none needed 
checking dependency style of gcc... (cached) gcc3 
checking how to run the C preprocessor... gcc -E 

Call order of parrent methods in __dispose() and __finalize()

Hi,

I noticed that implementation of __dispose() and __finalize() methods generated by GOB includes calls
corresponding dispose() and finalize() methods of the parent BEFORE deallocating local objects.
GObject specification states to call them AFTER local resources have been freed. In most cases that
should not be an issue, but the fact that it is inconsistent with the specification makes me cautious. Is
there any reason for this behavior?

Regards,
Dmitri

--
to unsubscribe:
send mail to minimalist <at> 5z.com with "unsubscribe gob-list" in the subject

Re: Building on ubuntu 10.04 LTS fails

Install flex.  It should fail configure ... I'll take a look at that.

Jiri

On Sat, Mar 5, 2011 at 9:47 PM, Dmitri Toubelis
<dmitri.toubelis <at> alkeron.com> wrote:
> Hi,
>
> I'm trying to build gob-2.0.18 from source tar ball on Ubuntu 10.04 LTS and it fails with the following messages:
>
> dev02:~/src/gob2-2.0.18> ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... gcc3
> checking for library containing strerror... none required
> checking for gcc... (cached) gcc

Re: Call order of parrent methods in __dispose() and __finalize()

Not that I remember, I'll take a look at it.

Jiri

On Sat, Mar 5, 2011 at 10:08 PM, Dmitri Toubelis
<dmitri.toubelis <at> alkeron.com> wrote:
> Hi,
>
> I noticed that implementation of __dispose() and __finalize() methods generated by GOB includes calls
corresponding dispose() and finalize() methods of the parent BEFORE deallocating local objects.
GObject specification states to call them AFTER local resources have been freed. In most cases that
should not be an issue, but the fact that it is inconsistent with the specification makes me cautious. Is
there any reason for this behavior?
>
> Regards,
> Dmitri
>
>
>
> --
> to unsubscribe:
> send mail to minimalist <at> 5z.com with "unsubscribe gob-list" in the subject
>

--

-- 
Jiri (George) Lebl, http://www.math.ucsd.edu/~jlebl/ or http://www.jirka.org/

--

[PATCH] Don't output #line 0 directives for prototypes.

It is not valid for the integer argument of a #line directive to be 0.
However, the generated C source will contain such a directive around the
prototypes of private functions that do not appear in the .gob file.
For example, the trivial

  class My:Test from G:Object {
  }

generates the invalid C code:

  #line 0 "my-test.gob"
  static void my_test_init (MyTest * o) G_GNUC_UNUSED;
  /* ... */
  #line 0 "my-test.gob"
  static void my_test_class_init (MyTestClass * c) G_GNUC_UNUSED;

Fix this up and add an assertion to out_addline_infile to catch future
problems of this nature.
---

Hopefully this is the right place to send patches!  The gob2 website
doesn't make any mention of where they should be sent.

 src/main.c |    6 ++++--
 src/out.c  |    2 ++
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/src/main.c b/src/main.c
index 5d2d4c9..cd8edef 100644
--- a/src/main.c