Menu
▾
▴
wxhaskell-devel
|
From: Dave T. <dav...@gm...> - 2011-07-21 20:54:39
|
Hi all, I am having trouble compiling wxcore on Ubuntu 10.04. The source I am using I pulled with a "darcs get" from hackage, I then descended into the wxcore directory and did a "cabal configure". It gives me a "* Missing C libraries: wx_baseu-2.8, wx_baseu_net-2.8, wx_baseu_xml-2.8..." error, I have the .so files for "libwx_baseu-2.8.so" in my /usr/lib, but I don't have any headers in /usr/include, could this be a problem? If so then does anyone know where I can obtain these headers? I have already installed the libwxbase2.8-dev and libwxgtk2.8-dev packages. Running "cabal configure -v3" I can see the first problem is this: "/usr/bin/ld: cannot find -lwxmsw28ud_media" Is it safe to assume that "msw" refers to MS Windows? If so should I be trying to link against this when building in Linux? I have pasted the full output from "cabal configure -v3" here: http://hpaste.org/49326 Thanks, Dave |
|
From: Dave T. <duk...@gm...> - 2011-07-21 20:55:21
|
Hi all, I am having trouble compiling wxcore on Ubuntu 10.04. The source I am using I pulled with a "darcs get" from hackage, I then descended into the wxcore directory and did a "cabal configure". It gives me a "* Missing C libraries: wx_baseu-2.8, wx_baseu_net-2.8, wx_baseu_xml-2.8..." error, I have the .so files for "libwx_baseu-2.8.so" in my /usr/lib, but I don't have any headers in /usr/include, could this be a problem? If so then does anyone know where I can obtain these headers? I have already installed the libwxbase2.8-dev and libwxgtk2.8-dev packages. Running "cabal configure -v3" I can see the first problem is this: "/usr/bin/ld: cannot find -lwxmsw28ud_media" Is it safe to assume that "msw" refers to MS Windows? If so should I be trying to link against this when building in Linux? I have pasted the full output from "cabal configure -v3" here: http://hpaste.org/49326 Thanks, Dave |
|
From: Eric Y. K. <eri...@gm...> - 2011-07-21 21:44:28
|
Hi Dave, On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote: > I am having trouble compiling wxcore on Ubuntu 10.04. > The source I am using I pulled with a "darcs get" from hackage, I then > descended into the wxcore directory and did a "cabal configure". I suspect that recent minor changes to our Setup.hs file have broken compatibility with wxWidgets 2.8. Could you try darcs obliterate -p "Additional libraries required by wxWidgets 2.9" and see if it has any result? Alternatively, if you just want a working wxHaskell and aren't particularly interested in debugging this sort of thing, I'd suggest just doing cabal install wx and fetching the one on hackage for now. Thanks! -- Eric Kow <http://erickow.com> |
|
From: Dave T. <dav...@gm...> - 2011-07-21 22:01:22
|
That was exactly the problem! Thank you very much Eric :) Dave, On 21 July 2011 22:44, Eric Y. Kow <eri...@gm...> wrote: > Hi Dave, > > On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote: > > I am having trouble compiling wxcore on Ubuntu 10.04. > > The source I am using I pulled with a "darcs get" from hackage, I then > > descended into the wxcore directory and did a "cabal configure". > > I suspect that recent minor changes to our Setup.hs file have > broken compatibility with wxWidgets 2.8. > > Could you try > > darcs obliterate -p "Additional libraries required by wxWidgets 2.9" > > and see if it has any result? > > Alternatively, if you just want a working wxHaskell and aren't > particularly interested in debugging this sort of thing, I'd > suggest just doing cabal install wx and fetching the one on > hackage for now. > > Thanks! > > -- > Eric Kow <http://erickow.com> > |
|
From: Dave T. <dav...@gm...> - 2011-07-22 19:06:36
|
Hmm, unfortunately whilst cabal configure now completes successfully, I am having a problem when doing cabal build, see output below. Could it be related to this: http://comments.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/298 ? src/cpp/eljcursor.cpp:23:0: error: no matching function for call to ‘wxCursor::wxCursor(wxString&, long int&, int&, int&)’ /usr/include/wx-2.8/wx/gtk/cursor.h:31:0: note: candidates are: wxCursor::wxCursor(const char*, int, int, int, int, const char*, const wxColour*, const wxColour*) /usr/include/wx-2.8/wx/gtk/cursor.h:29:0: note: wxCursor::wxCursor(const wxImage&) /usr/include/wx-2.8/wx/gtk/cursor.h:27:0: note: wxCursor::wxCursor(int) /usr/include/wx-2.8/wx/gtk/cursor.h:26:0: note: wxCursor::wxCursor() /usr/include/wx-2.8/wx/gtk/cursor.h:23:0: note: wxCursor::wxCursor(const wxCursor&) On 21 July 2011 23:00, Dave Tapley <dav...@gm...> wrote: > That was exactly the problem! > > Thank you very much Eric :) > > Dave, > > > > > On 21 July 2011 22:44, Eric Y. Kow <eri...@gm...> wrote: > >> Hi Dave, >> >> On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote: >> > I am having trouble compiling wxcore on Ubuntu 10.04. >> > The source I am using I pulled with a "darcs get" from hackage, I then >> > descended into the wxcore directory and did a "cabal configure". >> >> I suspect that recent minor changes to our Setup.hs file have >> broken compatibility with wxWidgets 2.8. >> >> Could you try >> >> darcs obliterate -p "Additional libraries required by wxWidgets 2.9" >> >> and see if it has any result? >> >> Alternatively, if you just want a working wxHaskell and aren't >> particularly interested in debugging this sort of thing, I'd >> suggest just doing cabal install wx and fetching the one on >> hackage for now. >> >> Thanks! >> >> -- >> Eric Kow <http://erickow.com> >> > > |
|
From: Dave T. <dav...@gm...> - 2011-07-23 01:26:28
|
I have done some further investigation on this and discovered the source of the problem, and it is very strange. It seems that even in the latest 2.8.12 release of wxWidgets¹ the cursor.h file in include/wx/gtk/ does not contain the four argument constructor (which is causing the build failure below), however the cursor.h in include/wx/msw does. I looked at the history for eljcursor.cpp in darcs and it hasn't been changed in anyway in a long time, so this can't be a new problem. I am going to post to the wx-dev² group and see if anyone knows why this constructor declaration is missing. But the question remains: How have we been able to build wxcore for GTK when its .cabal claims³ it works for GTK with wxWidgets 2.8? Thanks, Dave ¹ http://sourceforge.net/projects/wxwindows/files/2.8.12/ ² http://groups.google.com/group/wx-dev ³ http://code.haskell.org/wxhaskell/wxcore/wxcore.cabal On 22 July 2011 20:06, Dave Tapley <dav...@gm...> wrote: > Hmm, unfortunately whilst cabal configure now completes successfully, I am > having a problem when doing cabal build, see output below. Could it be > related to this: > http://comments.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/298 ? > > src/cpp/eljcursor.cpp:23:0: > error: no matching function for call to ‘wxCursor::wxCursor(wxString&, > long int&, int&, int&)’ > > /usr/include/wx-2.8/wx/gtk/cursor.h:31:0: > note: candidates are: wxCursor::wxCursor(const char*, int, int, int, > int, const char*, const wxColour*, const wxColour*) > > /usr/include/wx-2.8/wx/gtk/cursor.h:29:0: > note: wxCursor::wxCursor(const wxImage&) > > /usr/include/wx-2.8/wx/gtk/cursor.h:27:0: > note: wxCursor::wxCursor(int) > > /usr/include/wx-2.8/wx/gtk/cursor.h:26:0: > note: wxCursor::wxCursor() > > /usr/include/wx-2.8/wx/gtk/cursor.h:23:0: > note: wxCursor::wxCursor(const wxCursor&) > > > > > > > On 21 July 2011 23:00, Dave Tapley <dav...@gm...> wrote: > >> That was exactly the problem! >> >> Thank you very much Eric :) >> >> Dave, >> >> >> >> >> On 21 July 2011 22:44, Eric Y. Kow <eri...@gm...> wrote: >> >>> Hi Dave, >>> >>> On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote: >>> > I am having trouble compiling wxcore on Ubuntu 10.04. >>> > The source I am using I pulled with a "darcs get" from hackage, I then >>> > descended into the wxcore directory and did a "cabal configure". >>> >>> I suspect that recent minor changes to our Setup.hs file have >>> broken compatibility with wxWidgets 2.8. >>> >>> Could you try >>> >>> darcs obliterate -p "Additional libraries required by wxWidgets 2.9" >>> >>> and see if it has any result? >>> >>> Alternatively, if you just want a working wxHaskell and aren't >>> particularly interested in debugging this sort of thing, I'd >>> suggest just doing cabal install wx and fetching the one on >>> hackage for now. >>> >>> Thanks! >>> >>> -- >>> Eric Kow <http://erickow.com> >>> >> >> > |
|
From: Dave T. <duk...@gm...> - 2011-07-23 20:26:42
|
Well I have a response¹ from someone in the wx-dev group saying that the missing GTK constructor "is available in 2.9.2 but chances of this being backported to 2.8 are slim". I don't know how people would feel about modifying wxcore to use a constructor which is implemented for 2.8 with GTK? Dave, ¹ ---------- Forwarded message ---------- From: Vadim Zeitlin <va...@wx...> Date: 23 July 2011 12:52 Subject: Re: [wx-dev] [2.8.12] Missing constructor definition in gtk cursor.h To: wx...@go... On Sat, 23 Jul 2011 02:32:12 +0100 Dave Tapley <duk...@gm...> wrote: DT> It seems that in (at least) the latest 2.8.12 release of wxWidgets¹ the DT> cursor.h file in include/wx/gtk/ does not contain a four argument DT> constructor², however the cursor.h in include/wx/msw does. DT> DT> Does anyone know why this is so? It simply wasn't implemented initially. It was added since then and is available in 2.9.2 but chances of this being backported to 2.8 are slim. Regards, VZ On 23 July 2011 02:26, Dave Tapley <dav...@gm...> wrote: > I have done some further investigation on this and discovered the source of > the problem, and it is very strange. > > It seems that even in the latest 2.8.12 release of wxWidgets¹ the cursor.h > file in include/wx/gtk/ does not contain the four argument constructor > (which is causing the build failure below), however the cursor.h in > include/wx/msw does. > > I looked at the history for eljcursor.cpp in darcs and it hasn't been > changed in anyway in a long time, so this can't be a new problem. > > I am going to post to the wx-dev² group and see if anyone knows why this > constructor declaration is missing. > > But the question remains: > How have we been able to build wxcore for GTK when its .cabal claims³ it > works for GTK with wxWidgets 2.8? > > Thanks, > Dave > > > ¹ http://sourceforge.net/projects/wxwindows/files/2.8.12/ > ² http://groups.google.com/group/wx-dev > ³ http://code.haskell.org/wxhaskell/wxcore/wxcore.cabal > > > > On 22 July 2011 20:06, Dave Tapley <dav...@gm...> wrote: > >> Hmm, unfortunately whilst cabal configure now completes successfully, I am >> having a problem when doing cabal build, see output below. Could it be >> related to this: >> http://comments.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/298 >> ? >> >> src/cpp/eljcursor.cpp:23:0: >> error: no matching function for call to >> ‘wxCursor::wxCursor(wxString&, long int&, int&, int&)’ >> >> /usr/include/wx-2.8/wx/gtk/cursor.h:31:0: >> note: candidates are: wxCursor::wxCursor(const char*, int, int, int, >> int, const char*, const wxColour*, const wxColour*) >> >> /usr/include/wx-2.8/wx/gtk/cursor.h:29:0: >> note: wxCursor::wxCursor(const wxImage&) >> >> /usr/include/wx-2.8/wx/gtk/cursor.h:27:0: >> note: wxCursor::wxCursor(int) >> >> /usr/include/wx-2.8/wx/gtk/cursor.h:26:0: >> note: wxCursor::wxCursor() >> >> /usr/include/wx-2.8/wx/gtk/cursor.h:23:0: >> note: wxCursor::wxCursor(const wxCursor&) >> >> >> >> >> >> >> On 21 July 2011 23:00, Dave Tapley <dav...@gm...> wrote: >> >>> That was exactly the problem! >>> >>> Thank you very much Eric :) >>> >>> Dave, >>> >>> >>> >>> >>> On 21 July 2011 22:44, Eric Y. Kow <eri...@gm...> wrote: >>> >>>> Hi Dave, >>>> >>>> On Thu, Jul 21, 2011 at 21:54:11 +0100, Dave Tapley wrote: >>>> > I am having trouble compiling wxcore on Ubuntu 10.04. >>>> > The source I am using I pulled with a "darcs get" from hackage, I then >>>> > descended into the wxcore directory and did a "cabal configure". >>>> >>>> I suspect that recent minor changes to our Setup.hs file have >>>> broken compatibility with wxWidgets 2.8. >>>> >>>> Could you try >>>> >>>> darcs obliterate -p "Additional libraries required by wxWidgets 2.9" >>>> >>>> and see if it has any result? >>>> >>>> Alternatively, if you just want a working wxHaskell and aren't >>>> particularly interested in debugging this sort of thing, I'd >>>> suggest just doing cabal install wx and fetching the one on >>>> hackage for now. >>>> >>>> Thanks! >>>> >>>> -- >>>> Eric Kow <http://erickow.com> >>>> >>> >>> >> > |
|
From: Eric Y. K. <eri...@gm...> - 2011-07-24 21:57:34
|
On Sat, Jul 23, 2011 at 21:26:12 +0100, Dave Tapley wrote: > Well I have a response¹ from someone in the wx-dev group saying that the > missing GTK constructor "is > available in 2.9.2 but chances of this being backported to 2.8 are slim". > > I don't know how people would feel about modifying wxcore to use a > constructor which is implemented for 2.8 with GTK? I think it's worth checking that the stable wxcore doesn't already do this. -- Eric Kow <http://erickow.com> |
|
From: Dave T. <duk...@gm...> - 2011-07-25 00:10:42
|
On 24 July 2011 22:57, Eric Y. Kow <eri...@gm...> wrote: > On Sat, Jul 23, 2011 at 21:26:12 +0100, Dave Tapley wrote: > > Well I have a response¹ from someone in the wx-dev group saying that the > > missing GTK constructor "is > > available in 2.9.2 but chances of this being backported to 2.8 are slim". > > > > I don't know how people would feel about modifying wxcore to use a > > constructor which is implemented for 2.8 with GTK? > > I think it's worth checking that the stable wxcore doesn't already do > this. > > -- > Eric Kow <http://erickow.com> > A very good suggestion. I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹. Do we know why this fix is in the release, but not in darcs? ¹ #ifdef __WXGTK__ // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999 return NULL; #else |
|
From: Eric Y. K. <eri...@gm...> - 2011-07-25 06:45:30
|
On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote: > A very good suggestion. > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹. > > Do we know why this fix is in the release, but not in darcs? I suspect the answer lies somewhere in here: darcs changes --repo http://code.haskell.org/wxhaskell --from-tag . --match 'hunk 45999' (the 45999 is from the URL mentioned in the source code you pasted) It could be a good thing if you would catalogue all the wxWidgets 2.8 regressions you have encountered so far -- Eric Kow <http://erickow.com> |
|
From: Dave T. <duk...@gm...> - 2011-07-25 16:49:15
|
On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote: > On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote: > > A very good suggestion. > > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹. > > > > Do we know why this fix is in the release, but not in darcs? > > I suspect the answer lies somewhere in here: > > darcs changes --repo http://code.haskell.org/wxhaskell --from-tag . > --match 'hunk 45999' > > (the 45999 is from the URL mentioned in the source code you pasted) > > It could be a good thing if you would catalogue all the wxWidgets > 2.8 regressions you have encountered so far > > -- > Eric Kow <http://erickow.com> > The only other step I had to take after pulling the latest was: darcs obliterate -p "Additional libraries required by wxWidgets 2.9" Failure to do this causes: Configuring wxcore-0.13.1... setup: Missing dependencies on foreign libraries: * Missing C libraries: wx_baseu-2.8, wx_baseu_net-2.8, wx_baseu_xml-2.8, wx_gtk2u_core-2.8, wx_gtk2u_adv-2.8, wx_gtk2u_html-2.8, wx_gtk2u_qa-2.8, wx_gtk2u_xrc-2.8, wx_gtk2u_aui-2.8, wx_gtk2u_richtext-2.8 This problem can usually be solved by installing the system packages that provide these libraries (you may need the "-dev" versions). If the libraries are already installed but in a non-standard location then you can use the flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are. |
|
From: Jeremy O'D. <jer...@gm...> - 2011-07-25 14:49:45
|
Hi all, On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote: > On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote: > > A very good suggestion. > > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹. > > > > Do we know why this fix is in the release, but not in darcs? > > I suspect the answer lies somewhere in here: > > darcs changes --repo http://code.haskell.org/wxhaskell --from-tag . > --match 'hunk 45999' > The answer is that it comes from my clean-up for wxWidgets 2.9, and is probably a case of being over-zealous. The problem wasn't caught because (most likely) no-one built tip for Gtk. It's not an environment I have readily available to me. I'm not sure that there is a straightforward way to get similar behaviour on Gtk, so I think the only clean solution is to revert the old 'NULL' implementation. What do you think? EWXWEXPORT(wxCursor*,Cursor_CreateLoad)(wxString* name,long type,int width,int height) { #if (wxVERSION_NUMBER >= 2900) wxBitmapType bm_type = (wxBitmapType) type; #else long bm_type = type; #endif #ifdef __WXGTK__ // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999 return NULL; #else return new wxCursor(*name, bm_type, width, height); #endif } Regards Jeremy |
|
From: Dave T. <duk...@gm...> - 2011-07-25 17:06:44
|
On 25 July 2011 15:49, Jeremy O'Donoghue <jer...@gm...> wrote: > Hi all, > > On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote: > >> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote: >> > A very good suggestion. >> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹. >> > >> > Do we know why this fix is in the release, but not in darcs? >> >> I suspect the answer lies somewhere in here: >> >> darcs changes --repo http://code.haskell.org/wxhaskell --from-tag . >> --match 'hunk 45999' >> > > The answer is that it comes from my clean-up for wxWidgets 2.9, and is > probably a case of being over-zealous. The problem wasn't caught because > (most likely) no-one built tip for Gtk. It's not an environment I have > readily available to me. > > I'm not sure that there is a straightforward way to get similar behaviour > on Gtk, so I think the only clean solution is to revert the old 'NULL' > implementation. What do you think? > > EWXWEXPORT(wxCursor*,Cursor_CreateLoad)(wxString* name,long type,int > width,int height) > { > #if (wxVERSION_NUMBER >= 2900) > wxBitmapType bm_type = (wxBitmapType) type; > #else > long bm_type = type; > #endif > > #ifdef __WXGTK__ > // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999 > return NULL; > #else > return new wxCursor(*name, bm_type, width, height); > #endif > } > > Regards > Jeremy > Well, the 2.9.2 dev release¹ appears to include that constructor (in include/wx/gtk/cursor.h) if wxUSE_IMAGE is set. So perhaps we should check that? ¹ http://www.wxwidgets.org/downloads/#latest_dev |
|
From: Dave T. <duk...@gm...> - 2011-07-25 23:42:14
|
On 25 July 2011 15:49, Jeremy O'Donoghue <jer...@gm...> wrote: > Hi all, > > On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote: > >> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote: >> > A very good suggestion. >> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹. >> > >> > Do we know why this fix is in the release, but not in darcs? >> >> I suspect the answer lies somewhere in here: >> >> darcs changes --repo http://code.haskell.org/wxhaskell --from-tag . >> --match 'hunk 45999' >> > > The answer is that it comes from my clean-up for wxWidgets 2.9, and is > probably a case of being over-zealous. The problem wasn't caught because > (most likely) no-one built tip for Gtk. It's not an environment I have > readily available to me. > > I'm not sure that there is a straightforward way to get similar behaviour > on Gtk, so I think the only clean solution is to revert the old 'NULL' > implementation. What do you think? > > EWXWEXPORT(wxCursor*,Cursor_CreateLoad)(wxString* name,long type,int > width,int height) > { > #if (wxVERSION_NUMBER >= 2900) > wxBitmapType bm_type = (wxBitmapType) type; > #else > long bm_type = type; > #endif > > #ifdef __WXGTK__ > // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999 > return NULL; > #else > return new wxCursor(*name, bm_type, width, height); > #endif > } > > Regards > Jeremy > Having made these modifications I now get passed that error, but stumble on this: http://hpaste.org/49525 Does anyone have any intuition why these files could be missing? |
|
From: Dave T. <duk...@gm...> - 2011-07-27 00:30:54
|
On 26 July 2011 00:41, Dave Tapley <duk...@gm...> wrote: > On 25 July 2011 15:49, Jeremy O'Donoghue <jer...@gm...>wrote: > >> Hi all, >> >> On 25 July 2011 07:45, Eric Y. Kow <eri...@gm...> wrote: >> >>> On Mon, Jul 25, 2011 at 01:10:15 +0100, Dave Tapley wrote: >>> > A very good suggestion. >>> > I cabal unpacked wxcore-0.12.1.7 and it appears to have a fix in it¹. >>> > >>> > Do we know why this fix is in the release, but not in darcs? >>> >>> I suspect the answer lies somewhere in here: >>> >>> darcs changes --repo http://code.haskell.org/wxhaskell --from-tag . >>> --match 'hunk 45999' >>> >> >> The answer is that it comes from my clean-up for wxWidgets 2.9, and is >> probably a case of being over-zealous. The problem wasn't caught because >> (most likely) no-one built tip for Gtk. It's not an environment I have >> readily available to me. >> >> I'm not sure that there is a straightforward way to get similar behaviour >> on Gtk, so I think the only clean solution is to revert the old 'NULL' >> implementation. What do you think? >> >> EWXWEXPORT(wxCursor*,Cursor_CreateLoad)(wxString* name,long type,int >> width,int height) >> { >> #if (wxVERSION_NUMBER >= 2900) >> wxBitmapType bm_type = (wxBitmapType) type; >> #else >> long bm_type = type; >> #endif >> >> #ifdef __WXGTK__ >> // See http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/45999 >> return NULL; >> #else >> return new wxCursor(*name, bm_type, width, height); >> #endif >> } >> >> Regards >> Jeremy >> > > Having made these modifications I now get passed that error, but stumble on > this: http://hpaste.org/49525 > Does anyone have any intuition why these files could be missing? > Hmm, I've switched to the 2.9.2 dev release of wxWidgets and I'm getting a similar failures with: Both with the latest wxHaskell in hackage: http://hpaste.org/49563 And with the latest from darcs: http://hpaste.org/49564 Does anyone have any suggestions as to a fix, or a more reliable build set up? Thanks, Dave |
Thanks for helping keep SourceForge clean.
X