ngspice-devel

[Ngspice-devel] bug fixes

[Lionel S. C. <lio...@gm...>]

Hi,

I finally committed my (quite) big set of bug fixes, in order:
  to prevent errors where there are warnings
  to avoid using regular malloc.

I tested as much as I can.

I've not reformatted COPYING yet, I wait for your comments first.

-- 
Lionel SAINTE CLUQUE

Re: [Ngspice-devel] bug fixes

[Paolo N. <pne...@gm...>]

Lionel,

For copying: I have read it and it is fine. Just a note, you write:
"We encourage restrictive licenses to be choosen for new
functinonalities, writtent in distinct files, leading to
distinct libraries that links depending on a specific configure flag."

is restrictive = non copyleft ?

Ops, something I forgot:
Have you seen the pacth sent by Jos ?

Let me know if you plan to add it to rework-18, otherwise we release and
keep the patch for rework 19.


Ciao,
Paolo

Lionel Sainte Cluque wrote:
> Hi,
> 
> I finally committed my (quite) big set of bug fixes, in order:
>   to prevent errors where there are warnings
>   to avoid using regular malloc.
> 
> I tested as much as I can.
> 
> I've not reformatted COPYING yet, I wait for your comments first.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ngspice-devel mailing list
> Ngs...@li...
> https://lists.sourceforge.net/lists/listinfo/ngspice-devel

Re: [Ngspice-devel] bug fixes

[steven.borley <ste...@vi...>]

On 22 Nov 2008, at 10:52, Paolo Nenzi wrote:

> "We encourage restrictive licenses to be choosen for new
> functinonalities, writtent in distinct files, leading to
> distinct libraries that links depending on a specific configure flag."

Ah, I missed that. Just thinking about the grammar rather than Paolo's  
question, I belive is should be...

	"...that link depending on a specific configure flags."

(links not links, and flags not flag).

As for Paolo's question. I don't think restrictive = non-copyleft.   
All licenses are restrictive in one way or another. Maybe the word  
'restrictive' could be omitted here without loss of meaning?

Steven

Re: [Ngspice-devel] bug fixes

[Paolo N. <pne...@gm...>]

Hi,

I was in chat with Lionel, restrictive licenses are the copyleft ones.

I understood exactly the opposite.

Ciao,
Paolo


> As for Paolo's question. I don't think restrictive = non-copyleft.   
> All licenses are restrictive in one way or another. Maybe the word  
> 'restrictive' could be omitted here without loss of meaning?
> 
> Steven
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Ngspice-devel mailing list
> Ngs...@li...
> https://lists.sourceforge.net/lists/listinfo/ngspice-devel

[Ngspice-devel] version.texi missing

[Holger V. <hol...@un...>]

Hi all,

I just tried to make ngspice in an entirely new directory with MINGW and 
source files freshly downloaded from CVS.

The build fails immediately due to a missing /doc/version.texi.

Is there any reason to not have that one or is it just forgotten?

Regards

Holger

Re: [Ngspice-devel] version.texi missing

[Lionel S. C. <lio...@gm...>]

It is strange,

I used to have this bug by the past (I corrected it in my local copies by
removing doc directory from the make tree).

I do not have it now, but it's strange it appears for you too, now.


2008/11/22 Holger Vogt <hol...@un...>

> Hi all,
>
> I just tried to make ngspice in an entirely new directory with MINGW and
> source files freshly downloaded from CVS.
>
> The build fails immediately due to a missing /doc/version.texi.
>
> Is there any reason to not have that one or is it just forgotten?
>
> Regards
>
> Holger
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Ngspice-devel mailing list
> Ngs...@li...
> https://lists.sourceforge.net/lists/listinfo/ngspice-devel
>



-- 
Lionel SAINTE CLUQUE

Re: [Ngspice-devel] bug fixes

[Holger V. <hol...@un...>]

Dear all,

before releasing ngspice 18, we should put a little bit more work into 
some issues:

My personal feeling is that the tclspice integration using libtool is 
not yet ready.
I cannot make tclspice fronm CVS sources under MINGW.
I cannot make tclspice from CVS sources under LINUX (SUSE 10.2).
The error messages are the same in both cases and are totally cryptic 
(thanks to libtool):

libtool: link: can not build a shared library
libtool: link: See the libtool documentation for more information.
libtool: link: Fatal configuration error.

CVS code has to be the norm, not a personal setup of ngspice/tclspice! 
So if there is anybody out there who can make tclspice on either OS from 
fresh code (really fresh, that is starting with an empty directory, 
copying the top level CVS file only and then calling CVS to download 
everything), please let me know. I would be happy to understand what is 
going on.

Compilation of ngspice with libtool is a nuisance, because every *.o 
file is created twice.
I have reported on these matters some time ago, and we should resolve 
these problems. However, if we want (need?) to stick to libtool, 
somebody should take care and make himself a specialist. We cannot 
introduce this tool and have only a coarse understanding of what it is 
doing!

Some additional remarks:

What will be the new welcome message (current one below)?
******
** ngspice-17.1 : Circuit level simulation program
** The U. C. Berkeley CAD Group
** Copyright 1985-1994, Regents of the University of California.
** Please submit bug-reports to: ngs...@li...
** Creation Date: Sun Nov 23 08:53:15 GMT 2008
******

During cimpiling there are some warnings (similar under MINGW and LINUX).
A summary is below, skipping minor ones:

MINGW:
cmath2.c: In function `cx_rnd':
cmath2.c:217: warning: implicit declaration of function `random'
mifsetup.c: In function `MIFunsetup':
mifsetup.c:524: warning: case value `-1' not in enumerated type 
`Mif_Cntl_Src_Type_t'
mod_yacc.c: In function `mod_yyparse':
mod_yacc.c:1455: warning: implicit declaration of function `mod_yylex'
mod_yacc.y:493: warning: too many arguments for format
main.c: In function `xmain':
main.c:740: warning: implicit declaration of function `srandom'

in LINUX
equality.c: In function ‘AlmostEqualUlps’:
equality.c:56: warning: implicit declaration of function ‘llabs’
equality.c:56: warning: incompatible implicit declaration of built-in 
function ‘llabs’

We should remove the sources of the warning by improving the code. I 
will take care of llabs and (s)random.

Regards

Holger

Re: [Ngspice-devel] bug fixes

[Lionel S. C. <lio...@gm...>]

Hi holger

I think it is good to release now. I know that there are some issues that
are not yet addressed, but it is not big enough IMO to delay it.

Yes, we can not build under mingw yet. I believe that windows users are
mostly interested in binaries or can carry on using plain ngspice rather
tclspice for some times. Perhaps the full integration of libtool can be put
in the release 19 task list?

I appology for my lack of time. I wanted to actively support tclspice
integration but my work does not let me the time, and I don't have windows.
If we want to do it good, better to take the time for it and wait newt
release.

Something I was thinking about in the past was to use libtool only in the
case of tclspice compiling. Perhaps it is better for ngspice. I had problems
under debian 64bits without libtool. I think we should keep it. We have to
make it compile under windows. That's true.



I fixed many warning this week, but I failed to fix the llabs implicit
declaration. llabs seems to be in stdlib, but depends on a #ifdef. Don't
have a solution yet.
It occurs for both ngspice and tclspice.

I checked warnings that appear under tclspice, but there are some others
under ngspice. Need to check it too...

Lionel

2008/11/23 Holger Vogt <hol...@un...>

> Dear all,
>
> before releasing ngspice 18, we should put a little bit more work into
> some issues:
>
> My personal feeling is that the tclspice integration using libtool is
> not yet ready.
> I cannot make tclspice fronm CVS sources under MINGW.
> I cannot make tclspice from CVS sources under LINUX (SUSE 10.2).
> The error messages are the same in both cases and are totally cryptic
> (thanks to libtool):
>
> libtool: link: can not build a shared library
> libtool: link: See the libtool documentation for more information.
> libtool: link: Fatal configuration error.
>
> CVS code has to be the norm, not a personal setup of ngspice/tclspice!
> So if there is anybody out there who can make tclspice on either OS from
> fresh code (really fresh, that is starting with an empty directory,
> copying the top level CVS file only and then calling CVS to download
> everything), please let me know. I would be happy to understand what is
> going on.
>
> Compilation of ngspice with libtool is a nuisance, because every *.o
> file is created twice.
> I have reported on these matters some time ago, and we should resolve
> these problems. However, if we want (need?) to stick to libtool,
> somebody should take care and make himself a specialist. We cannot
> introduce this tool and have only a coarse understanding of what it is
> doing!
>
> Some additional remarks:
>
> What will be the new welcome message (current one below)?
> ******
> ** ngspice-17.1 : Circuit level simulation program
> ** The U. C. Berkeley CAD Group
> ** Copyright 1985-1994, Regents of the University of California.
> ** Please submit bug-reports to: ngs...@li...
> ** Creation Date: Sun Nov 23 08:53:15 GMT 2008
> ******
>
> During cimpiling there are some warnings (similar under MINGW and LINUX).
> A summary is below, skipping minor ones:
>
> MINGW:
> cmath2.c: In function `cx_rnd':
> cmath2.c:217: warning: implicit declaration of function `random'
> mifsetup.c: In function `MIFunsetup':
> mifsetup.c:524: warning: case value `-1' not in enumerated type
> `Mif_Cntl_Src_Type_t'
> mod_yacc.c: In function `mod_yyparse':
> mod_yacc.c:1455: warning: implicit declaration of function `mod_yylex'
> mod_yacc.y:493: warning: too many arguments for format
> main.c: In function `xmain':
> main.c:740: warning: implicit declaration of function `srandom'
>
> in LINUX
> equality.c: In function 'AlmostEqualUlps':
> equality.c:56: warning: implicit declaration of function 'llabs'
> equality.c:56: warning: incompatible implicit declaration of built-in
> function 'llabs'
>
> We should remove the sources of the warning by improving the code. I
> will take care of llabs and (s)random.
>
> Regards
>
> Holger
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Ngspice-devel mailing list
> Ngs...@li...
> https://lists.sourceforge.net/lists/listinfo/ngspice-devel
>



-- 
Lionel SAINTE CLUQUE