gEDA-dev: g_hash_table_remove_all

Timmerman, Bert bert.timmerman at corusgroup.com
Thu Jul 5 04:12:40 EDT 2007


Hi Peter and all,

FWIW, maybe a table of dependancies with allowed versions could be made
and stated on one of the geda wiki developer pages.

If this table is to exist, it may or may not reduce this kind of
oversights in the future, it would at least give a clear picture on what
to use.

It has it's drawbacks: if, for instance, gtk is allowed to be <=1.6 in
the future the table needs to be maintained (by whoever pushes the
dependency version upwards).

Just my EUR 0.02

Kind regrads,

Bert Timmerman.

-----Original Message-----
From: geda-dev-bounces at moria.seul.org
[mailto:geda-dev-bounces at moria.seul.org] On Behalf Of Peter TB Brett
Sent: Thursday, July 05, 2007 7:42 AM
To: gEDA developer mailing list
Subject: Re: gEDA-dev: g_hash_table_remove_all

On Wednesday 04 July 2007 23:54:30 Stuart Brorson wrote:

> /usr/local/geda/lib/libgeda.so: undefined reference to
> `g_hash_table_remove_all'collect2: ld returned 1 exit status
>
> [snip]
>
> I'm sure it's an oversight by whoever used it, so no hard feelings.  I
> suppose most developers use much more up-to-date boxen than I do.
> Catching stuff like this is one reason I use old boxen.  So, whoever
> used it, I'd be very happy if you would find an equivalent  gtk-2.4
> compliant way to accomplish your goal.  :-)

That would be me.  Sorry -- and yes, it was an oversight.  We definitely
need 
a way to audit which library functions are in use!

I'm afraid I can't fix it right now, but I'll try and get a fix out this

evening (UK time).

                                 Peter


-- 
Peter Brett

Electronic Systems Engineer
Integral Informatics Ltd


More information about the geda-dev mailing list