gnupic: Thread: Re: gpsim compiler preference? - Mac OS/X help

Easy B (and OS/X friends), 

After struggling for months to keep up with all the releases of my
favorite EDA tools, assemblers, simulators and programmers for my Mac
I finally updated some existing fink package. Even created some new ones.

The utilities I (re-)packaged are the following.

o gEDA/PCB - 20040111 (based on Charles Lepple fink configs)
o gtk+extra - 0.99.17-1 (based on Jeffrey Whitaker fink configs)
o gputils - 0.12.0
o gpsim - 0.21.1
o (still working on picp)

Hopefully some other folks here would be willing to test these packages
before myself (or someone else) submits them to the fink folks for
unstable testing. I know they need some cleanup in the .info files, but
they do "work for me".

Here is my own test environment.

o gcc 3.3
o fink 0.6.2
o G4 MAC 10.3.2 system.

Its pretty easy to install these on a panther system.

o Install the latest fink (obtainable here)

  http://fink.sf.net

o Obtain the fink .info and .patch files from me (temporarily)

  http://screwdecaf.cx/tmp/fink-20040125/

o Copy all these files to /sw/fink/dists/local/main/finkinfo

o fink install <pkgname>

Cool. I managed to install it.
Thanx a lot man.
This is gota go into fink.
Ezra.

Am 27.01.2004 um 01:53 schrieb Mikey Sklar:

>
> Easy B (and OS/X friends),
>
> After struggling for months to keep up with all the releases of my
> favorite EDA tools, assemblers, simulators and programmers for my Mac
> I finally updated some existing fink package. Even created some new 
> ones.
>
> The utilities I (re-)packaged are the following.
>
> o gEDA/PCB - 20040111 (based on Charles Lepple fink configs)
> o gtk+extra - 0.99.17-1 (based on Jeffrey Whitaker fink configs)
> o gputils - 0.12.0
> o gpsim - 0.21.1
> o (still working on picp)
>
> Hopefully some other folks here would be willing to test these packages
> before myself (or someone else) submits them to the fink folks for
> unstable testing. I know they need some cleanup in the .info files, but
> they do "work for me".
>
> Here is my own test environment.
>
> o gcc 3.3
> o fink 0.6.2
> o G4 MAC 10.3.2 system.
>
> Its pretty easy to install these on a panther system.
>
> o Install the latest fink (obtainable here)
>
>   http://fink.sf.net
>
> o Obtain the fink .info and .patch files from me (temporarily)
>
>   http://screwdecaf.cx/tmp/fink-20040125/
>
> o Copy all these files to /sw/fink/dists/local/main/finkinfo
>
> o fink install <pkgname>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>

Thanks Mikey, this is great.  I have been trying to build gpsim for 
months - until now that is.

I have it running, but there are still a few issues though:

1. moving one of the gpsim windows generates a long list of "eXdbm : 
Wrong database ID" lines in the terminal
2. opening the stopwatch window generates a veeeery long lis of these 
lines ending with a segmentation fault and gpsim quitting.


Perhaps one of the gpsim developers could give a hint as to what we 
should be looking for to tackle this issue?


Michiel

I had some issiues simulating with the fink package based on gpsim
0.21.1 although I didn't have these troubles with the gpsim 0.20
build. Admittedly I had not tried rebuilding these projects with the
latest gpsim.

Are you able to still animate in breadboard mode?

I understand the moving of windows and stopwatch are causing issues for
you, I'll try that this evening and see if its a issue for me as well.

btw. I've updated my pages to include some more information about other
utilities I use on OS/X and fink packages for those.

http://screwdecaf.cx/tools

On Mon, 2 Feb 2004, Michiel Boerman wrote:

> Thanks Mikey, this is great.  I have been trying to build gpsim for 
> months - until now that is.
> 
> I have it running, but there are still a few issues though:
> 
> 1. moving one of the gpsim windows generates a long list of "eXdbm : 
> Wrong database ID" lines in the terminal
> 2. opening the stopwatch window generates a veeeery long lis of these 
> lines ending with a segmentation fault and gpsim quitting.
> 
> 
> Perhaps one of the gpsim developers could give a hint as to what we 
> should be looking for to tackle this issue?
> 
> 
> Michiel
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 

-- 

On Mon, 2 Feb 2004 16:55:22 +0100
Michiel Boerman ####@####.#### wrote:

> long list of "eXdbm : Wrong database ID" lines

Three weeks ago someone found a uninitialized pointer in the eXdbm package.
You could try downloading the new parse.c to see if that could be it.

http://cvs.sourceforge.net/viewcvs.py/*checkout*/gpsim/eXdbm/parse.c?content-type=text%2Fplain&rev=1.5

Other than that, no ideas.

 / Ralf

On Mon, 2 Feb 2004, Ralf Forsberg wrote:

> On Mon, 2 Feb 2004 16:55:22 +0100
> Michiel Boerman ####@####.#### wrote:
> 
> > long list of "eXdbm : Wrong database ID" lines
> 
> Three weeks ago someone found a uninitialized pointer in the eXdbm package.
> You could try downloading the new parse.c to see if that could be it.
> 
> http://cvs.sourceforge.net/viewcvs.py/*checkout*/gpsim/eXdbm/parse.c?content-type=text%2Fplain&rev=1.5
> 
> Other than that, no ideas.

Yes, Borut found that bug in eXdbm. I've never have seen those messages 
either so I'm at a loss what could be happening. One other thing you may 
wish to try is deleting the file ~/.gpsim . This is a hidden configuration 
file in your home directory that gpsim creates to record the state of the 
windows (i.e. size and location). If this file got corrupted for some 
reason, then there's a chance that it may affect eXdbm too.

Scott

That's it!
After removing the configuration file I get no more eXdbm messages. AND  
gpsim now restores previous window positioning.

Still crashes when i open the stopwatch though, with no other info than  
"segmentation fault"
I did find this quote on  
http://cvs.sourceforge.net/viewcvs.py/*checkout*/gpsim/eXdbm/parse.c? 
>> content-type=text%2Fplain&rev=1.5
>>
>> Other than that, no ideas.
>
> Yes, Borut found that bug in eXdbm. I've never have seen those messages
> either so I'm at a loss what could be happening. One other thing you  
> may
> wish to try is deleting the file ~/.gpsim . This is a hidden  
> configuration
> file in your home directory that gpsim creates to record the state of  
> the
> windows (i.e. size and location). If this file got corrupted for some
> reason, then there's a chance that it may affect eXdbm too.
>
> Scott
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>

On Mon, 2 Feb 2004, Michiel Boerman wrote:
> That's it!
> After removing the configuration file I get no more eXdbm messages. AND  
> gpsim now restores previous window positioning.
> 
> Still crashes when i open the stopwatch though, with no other info than  
> "segmentation fault"
> I did find this quote on  
> 

On Mon, 2 Feb 2004, Mikey Sklar wrote:

> On Mon, 2 Feb 2004, Michiel Boerman wrote:
> > That's it!
> > After removing the configuration file I get no more eXdbm messages. AND  
> > gpsim now restores previous window positioning.
> > 
> > Still crashes when i open the stopwatch though, with no other info than  
> > "segmentation fault"
> > I did find this quote on  
> > 

On Mon, 2 Feb 2004, Scott Dattalo wrote:
> Which version of gpsim are you using?

0.21.0 and 0.21.1 both produce this stopwatch crash fo rme.