Re: [wxhaskell-devel] Build failure
Hi Melanie, this problem is fixed in the forked repo https://github.com/atzedijkstra/wxHaskell. See the README there. The intent is that this fork will merge back into the official repo and an update of the version available via cabal and Hackage. regards, On 2 Aug, 2013, at 01:19 , M. Schulte m-hask...@fuglos.org wrote: Hi, I'm on Fedora 18, having installed wxWidgets (GTK) 2.9 in ~/local, ~/local/bin is in $PATH. When I do 'cabal install wx', the following error gets triggered: [...] /usr/bin/gcc -Wl,--hash-size=31 -Wl,--reduce-memory-overheads -Isrc/include -I/home/mel/local/include/wx-2.9 -I/home/mel/local/lib/wx/include/gtk2-unicode-2.9 -D__WXGTK__ -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -DwxcREFUSE_MEDIACTRL -fPIC -c src/cpp/eljgrid.cpp -o dist/build/src/cpp/eljgrid.o src/cpp/eljgrid.cpp: In function ‘void wxGridCellEditor_PaintBackground(wxGridCellEditor*, int, int, int, int, void*)’: src/cpp/eljgrid.cpp:61:65: error: no matching function for call to ‘wxGridCellEditor::PaintBackground(wxRect, wxGridCellAttr*)’ src/cpp/eljgrid.cpp:61:65: note: candidate is: In file included from /home/mel/local/include/wx-2.9/wx/grid.h:15:0, from src/include/wrapper.h:32, from src/cpp/eljgrid.cpp:1: /home/mel/local/include/wx-2.9/wx/generic/grid.h:216:18: note: virtual void wxGridCellEditor::PaintBackground(wxDC, const wxRect, const wxGridCellAttr) /home/mel/local/include/wx-2.9/wx/generic/grid.h:216:18: note: candidate expects 3 arguments, 2 provided src/cpp/eljgrid.cpp: In function ‘bool wxGrid_CanDragRowSize(wxGrid*)’: src/cpp/eljgrid.cpp:741:30: warning: ‘bool wxGrid::CanDragRowSize() const’ is deprecated (declared at /home/mel/local/include/wx-2.9/wx/generic/grid.h:1836) [-Wdeprecated-declarations] src/cpp/eljgrid.cpp: In function ‘bool wxGrid_CanDragColSize(wxGrid*)’: src/cpp/eljgrid.cpp:756:30: warning: ‘bool wxGrid::CanDragColSize() const’ is deprecated (declared at /home/mel/local/include/wx-2.9/wx/generic/grid.h:1837) [-Wdeprecated-declarations] cabal: Error: some packages failed to install: wx-0.90.0.1 depends on wxc-0.90.0.4 which failed to install. wxc-0.90.0.4 failed during the building phase. The exception was: ExitFailure 1 wxcore-0.90.0.3 depends on wxc-0.90.0.4 which failed to install. [mel@lily ~]$ Any idea, what's going on here? Thanks, melanie-- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel - Atze - Atze Dijkstra, Department of Information and Computing Sciences. /|\ Utrecht University, PO Box 80089, 3508 TB Utrecht, Netherlands. / | \ Tel.: +31-30-2534118/1454 | WWW : http://www.cs.uu.nl/~atze . /--| \ Fax : +31-30-2513971 | Email: a...@uu.nl ... / |___\ -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Build
On 31 May 2013 06:34, harry volderm...@hotmail.com wrote: The first problem is that wxdirect installs both executables and a library - why is that necessary, and is there another way to do it? Could you elaborate on this? I'm not 100% sure I follow. Is the issue something related to the wxdirect executable not being available in the sandbox environment? One issue is that wxdirect is used in the build process of the wxcore Setup.hs One thing which I think might help matters is if we had a way for the custom Setup.hs in wxcore to depend on wxdirect. Now one option would be for us to just swallow wxdirect directly into wxcore, making it part of the setup script. There's no particular reason it has to be run as an executable. If not feasible, then we may need something like https://github.com/haskell/cabal/issues/948 -- Eric Kow http://erickow.com -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Build
btw, we are already at the solution stage, what is the problem in fact ? what are the typical difficulties that a raise when installing wx ? is it on the C side or on the haskell side ? is it because they have to be fetched separately ? do we have a shared view on where lies the problems ? -- Luc Taesch Envoyé avec Sparrow (http://www.sparrowmailapp.com/?sig) Le vendredi 31 mai 2013 à 15:24, Eric Kow a écrit : On 31 May 2013 06:34, harry volderm...@hotmail.com (mailto:volderm...@hotmail.com) wrote: The first problem is that wxdirect installs both executables and a library - why is that necessary, and is there another way to do it? Could you elaborate on this? I'm not 100% sure I follow. Is the issue something related to the wxdirect executable not being available in the sandbox environment? One issue is that wxdirect is used in the build process of the wxcore Setup.hs One thing which I think might help matters is if we had a way for the custom Setup.hs in wxcore to depend on wxdirect. Now one option would be for us to just swallow wxdirect directly into wxcore, making it part of the setup script. There's no particular reason it has to be run as an executable. If not feasible, then we may need something like https://github.com/haskell/cabal/issues/948 -- Eric Kow http://erickow.com -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net (mailto:wxhaskell-devel@lists.sourceforge.net) https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Build
Eric Kow eric.kow@... writes: Is the issue something related to the wxdirect executable not being available in the sandbox environment? Yes - executables built in cabal-dev aren't on the path (which is different for each sandbox). If wxdirect only built an executable, I could install it outside of the sandboxes, and it would be available in the path for later use. A similar issue arises with wxc - what exactly is it building, and why is an environment variable needed to find it later? Is it creating a Haskell library, or just creating come C files for use by wxcore? -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] Build error
Hi,
On Thu, 05 Mar 2009 15:04:23 +0900, Don Stewart d...@galois.com wrote:
wxc/src/eljdc.cpp: In function ‘void wxDC_EndDrawing(wxDC*)’:
wxc/src/eljdc.cpp:26: warning: ‘void wxDCBase::EndDrawing()’ is deprecated
(declared at /usr/include/wx-2.8/wx/dc.h:393)
wxc/src/eljdc.cpp: At global scope:
wxc/src/eljdc.cpp:629: error: ‘wxMetafile’ was not declared in this scope
wxc/src/eljdc.cpp:629: error: ‘self’ was not declared in this scope
wxc/src/eljdc.cpp:629: error: expected primary-expression before ‘int’
wxc/src/eljdc.cpp:629: error: expected primary-expression before ‘int’
wxc/src/eljdc.cpp:629: error: initializer expression list treated as compound
expression
wxc/src/eljdc.cpp:630: error: expected ‘,’ or ‘;’ before ‘{’ token
wxc/src/eljdc.cpp:638: error: ‘wxMetafile’ was not declared in this scope
wxc/src/eljdc.cpp:638: error: ‘self’ was not declared in this scope
wxc/src/eljdc.cpp:638: error: expected primary-expression before ‘*’ token
wxc/src/eljdc.cpp:638: error: ‘_dc’ was not declared in this scope
wxc/src/eljdc.cpp:638: error: initializer expression list treated as compound
expression
wxc/src/eljdc.cpp:639: error: expected ‘,’ or ‘;’ before ‘{’ token
wxc/src/eljdc.cpp:647: error: ‘wxMetafile’ was not declared in this scope
wxc/src/eljdc.cpp:647: error: ‘self’ was not declared in this scope
wxc/src/eljdc.cpp:648: error: expected ‘,’ or ‘;’ before ‘{’ token
wxc/src/eljdc.cpp:656: error: variable or field ‘wxMetafile_Delete’ declared
void
wxc/src/eljdc.cpp:656: error: ‘wxMetafile’ was not declared in this scope
wxc/src/eljdc.cpp:656: error: ‘self’ was not declared in this scope
I fixed this bug in the new HackageDB releace 0.11.1.2.
Please test again with 0.11.1.2.
And I'll send darcs patch for this problem later.
Best Regards,
--
shelarcy shelarcyhotmail.co.jp
http://page.freett.com/shelarcy/
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
Re: [wxhaskell-devel] build failure in new release
shelarcy: Hi, On Sat, 11 Oct 2008 11:26:43 +0900, Don Stewart [EMAIL PROTECTED] wrote: configuration: library: wxhaskell-0.10.4 (release 0) (snip) *** config/config.mk:22: *** missing separator. Stop. cabal: Error: some packages failed to install: wxcore-0.10.4 failed during the building phase. The exception was: exit: ExitFailure 2 Typo in config.mk # Packages PKG-CONTAINERS=-package containers-0.2.0.0 PKG-PARSEC=-package parsec-2.1.0.1 2.1.0.2 PKG-TIME=-package time-1.1.2.1 PKG-STM=-package stm-2.1.1.1 I fixed this bug in the new HackageDB releace 0.10.5. Please test again with 0.10.5. And I sent darcs patch for this bug (and 2 more). I will push tomorrow unless somebody complains that. http://sourceforge.net/mailarchive/forum.php?thread_name=FF3769EA396C4DA4B1FC7BF317CFF6A8%40ShelarcyWinforum_name=wxhaskell-devel Best Regards, And I got wx and wxcore to build *out of the box* with cabal install 0.6, cabal 1.6 and ghc 6.10!!! Yay! -- Don - 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=100url=/ ___ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
