Hello!

I have the same problem on Fedora Core 4 (gcc 4.0). There was no problem with 
previous release (0.7.18).

Wojciech Kazubski

>
> Trying to compile gSpiceUI Version 0.7.56 on my SuSE 10.0 box.
>
> I cannot fins any fault in the code so I'll drop the question here and hope
> someone ran into it it before.
>
> GCC = gcc version 4.0.2 (SUSE Linux)
>
>
> Any ideas?
>
>
> Cheers
>
>
> Dan Andersson
>
>
>
> The compile output is:
>
>
>
> ***************************************************************************
>*************
>
> [EMAIL PROTECTED]:~/geda-sources/gspiceui/gspiceui-v0.7.56> make
> make config
> make[1]: Entering directory
> `/home/dan/geda-sources/gspiceui/gspiceui-v0.7.56' make[1]: Nothing to be
> done for `config'.
> make[1]: Leaving directory
> `/home/dan/geda-sources/gspiceui/gspiceui-v0.7.56' cd
> /home/dan/geda-sources/gspiceui/gspiceui-v0.7.56/src ; make
> make[1]: Entering directory
> `/home/dan/geda-sources/gspiceui/gspiceui-v0.7.56/src'
> g++ -c -O -Wall -pipe -I/usr/lib/wx/include/gtk2-unicode-release-2.6
> -I/usr/include/wx-2.6 -DGTK_NO_CHECK_CASTS -D__WXGTK__
> -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA
>   -I/usr/include -I/usr/X11R6/include -I. -Ibase -Imain -Inetlist -Ignucap
> -Ingspice -Iprocess -Iutility AppGSpiceUI.cpp -o obj/AppGSpiceUI.o
> CmdLinePcr.hpp:49: error: ISO C++ forbids declaration of ‘AppGSpiceUI’ with
> no type
> CmdLinePcr.hpp:49: error: expected ‘;’ before ‘*’ token
> CmdLinePcr.hpp:73: error: expected `)' before ‘*’ token
> AppGSpiceUI.cpp: In member function ‘virtual bool AppGSpiceUI::OnInit()’:
> AppGSpiceUI.cpp:74: error: no matching function for call to
> ‘CmdLinePcr::CmdLinePcr(AppGSpiceUI* const)’
> CmdLinePcr.hpp:46: note: candidates are: CmdLinePcr::CmdLinePcr()
> CmdLinePcr.hpp:46: note:                 CmdLinePcr::CmdLinePcr(const
> CmdLinePcr&)
> make[1]: *** [obj/AppGSpiceUI.o] Error 1
> make[1]: Leaving directory
> `/home/dan/geda-sources/gspiceui/gspiceui-v0.7.56/src'
> make: *** [all] Error 2
>
>
>
> ***********************************************************************

Reply via email to