RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Probably it is still using the old version of libraries, I had the same problem, I solved after I did a fresh installation and recompilation. Stefano -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Balogh Ádám Sent: Friday, 16 April, 2010 09:16 To: mapguide-users@lists.osgeo.org Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Thank you Stefano, but after downloading and building dwftoolkit-7.6 I still get this message: /usr/bin/ld: warning: libxerces-c.so.27, needed by /usr/local/src/MgDev-2.2.4731/Server/src/Services/Drawing/.libs/libMgServerDrawingService.so, may conflict with libxerces-c.so.25 /usr/local/src/MgDev-2.2.4731/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev-2.2.4731/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore: undefined reference to `DWFCore::DWFTimer::Tick32()' - Original Message - From: To: Sent: Thursday, April 15, 2010 6:00 PM Subject: mapguide-users Digest, Vol 40, Issue 14 > Send mapguide-users mailing list submissions to > mapguide-users@lists.osgeo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.osgeo.org/mailman/listinfo/mapguide-users > or, via email, send a message with subject or body 'help' to > mapguide-users-requ...@lists.osgeo.org > > You can reach the person managing the list at > mapguide-users-ow...@lists.osgeo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mapguide-users digest..." > > > Today's Topics: > > 1. Re: Edit WebLayout Problem (SriRam007) > 2. RE: Re: Edit WebLayout Problem (Ivan Mili?evi?) > 3. Re: MapGuide integration with Google Earth (padmini godavarthi) > 4. Re: Re: MapGuide integration with Google Earth (Jason Birch) > 5. Sorry (padmini godavarthi) > 6. Re: Edit WebLayout Problem (SriRam007) > 7. RE: Re: Edit WebLayout Problem (Ivan Mili?evi?) > 8. Does Mapguide 2.1 support Windows Server 2008 64 bits? > (Jose Cerrejon) > 9. Change the Icon image of the tool bar command buttons (SriRam007) > 10. RE: Change the Icon image of the tool bar command buttons > (Ivan Mili?evi?) > 11. RE: Change the Icon image of the tool bar command buttons > (SriRam007) > 12. building 64bit openmapguide on rhel 5.4 (Balogh ?d?m) > 13. RE: building 64bit openmapguide on rhel 5.4 (Bracco Stefano) > > > -- > > Message: 1 > Date: Wed, 14 Apr 2010 21:56:56 -0800 (PST) > From: SriRam007 > Subject: [mapguide-users] Re: Edit WebLayout Problem > To: mapguide-users@lists.osgeo.org > Message-ID: <1271311016243-4905776.p...@n2.nabble.com> > Content-Type: text/plain; charset=UTF-8 > > > > thank u Ivan MiliÄeviÄ?-3 > it is done. > > But I was trying to edit in the web layout because i want to make visible > false context menu also while editing. > > Can it also be done by client side javascript. > > > thanks > > -- > View this message in context: > http://n2.nabble.com/Edit-WebLayout-Problem-tp4869470p4905776.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > > > -- > > Message: 2 > Date: Thu, 15 Apr 2010 08:23:46 +0200 > From: Ivan Mili?evi? > Subject: RE: [mapguide-users] Re: Edit WebLayout Problem > To: MapGuide Users Mail List > Message-ID: <0d128d12f796fd49a6c2bb061db100a7012d773...@mail.storm.hr> > Content-Type: text/plain; charset="utf-8" > > Of course that you can. You can do it on several ways. > > Please, look at in ajaxmappane.templ and mainframe.tepml and if you can't > find anything that's related to your problem then you can ask for help. > > It's look like that you don't even try to solve a problem by yourself. > > -Original Message- > From: mapguide-users-boun...@lists.osgeo.org > [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of SriRam007 > Sent: Thursday, April 15, 2010 7:57 AM > To: mapguide-users@lists.osgeo.org > Subject: [mapguide-users] Re: Edit WebLayout Problem > > > > thank u Ivan MiliÄeviÄ?-3 > it is done. > > But I was trying to edit in the web layout because i want to make visible > false context menu also while editing. > > Can it also be done by client side javascript. > > > thanks > > -- > View this message in context: > http://n2.nabble.com/Edit-WebLayout-Problem-tp4869470p4905776.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > _
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
the 32 bits compatibility layer to true, but
doesn't
work.
--
View this message in context:
http://n2.nabble.com/Does-Mapguide-2-1-support-Windows-Server-2008-64-bits-tp4906789p4906789.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
--
Message: 9
Date: Thu, 15 Apr 2010 03:47:12 -0800 (PST)
From: SriRam007
Subject: [mapguide-users] Change the Icon image of the tool bar
command buttons
To: mapguide-users@lists.osgeo.org
Message-ID: <1271332032996-4906988.p...@n2.nabble.com>
Content-Type: text/plain; charset=us-ascii
Hi everyone,
Is there any way to change the Icon image of the tool bar command buttons
Using GetCommands methods i got all the command list
and i m doing enable and disable using javascript like below
var cmd = commands[0];//This is for getting Pan Command
if(condition)
{
cmd.enabled=false; //working
cmd.iconDisabled = "../stdicons/icon_pan_disabled.gif"; //not working
cmd.icon = "../stdicons/icon_pan.gif";//not working
}
else
{
cmd.enabled=true;//working
cmd.iconDisabled = "../stdicons/icon_pan_disabled.gif";//not working
cmd.icon = "../stdicons/icon_pan.gif";//not working
}
But there are two property iconDisabled and icon which i set but still
that
image is not changing
Actually here i m setting one image when the command buttons is disable
state and another when i m making it enable.
any help please
thanks
--
View this message in context:
http://n2.nabble.com/Change-the-Icon-image-of-the-tool-bar-command-buttons-tp4906988p4906988.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
--
Message: 10
Date: Thu, 15 Apr 2010 14:05:45 +0200
From: Ivan Mili?evi?
Subject: RE: [mapguide-users] Change the Icon image of the tool bar
command buttons
To: MapGuide Users Mail List
Message-ID: <0d128d12f796fd49a6c2bb061db100a7012d773...@mail.storm.hr>
Content-Type: text/plain; charset="iso-8859-2"
Hello again. Of course that you can change image of icon :/
Look at toolbar.templ and call InitToolbar() function after you change
image source.
-Original Message-
From: mapguide-users-boun...@lists.osgeo.org
[mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of SriRam007
Sent: Thursday, April 15, 2010 1:47 PM
To: mapguide-users@lists.osgeo.org
Subject: [mapguide-users] Change the Icon image of the tool bar command
buttons
Hi everyone,
Is there any way to change the Icon image of the tool bar command buttons
Using GetCommands methods i got all the command list
and i m doing enable and disable using javascript like below
var cmd = commands[0];//This is for getting Pan Command
if(condition)
{
cmd.enabled=false; //working
cmd.iconDisabled = "../stdicons/icon_pan_disabled.gif"; //not working
cmd.icon = "../stdicons/icon_pan.gif";//not working
}
else
{
cmd.enabled=true;//working
cmd.iconDisabled = "../stdicons/icon_pan_disabled.gif";//not working
cmd.icon = "../stdicons/icon_pan.gif";//not working
}
But there are two property iconDisabled and icon which i set but still
that
image is not changing
Actually here i m setting one image when the command buttons is disable
state and another when i m making it enable.
any help please
thanks
--
View this message in context:
http://n2.nabble.com/Change-the-Icon-image-of-the-tool-bar-command-buttons-tp4906988p4906988.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users
--
Message: 11
Date: Thu, 15 Apr 2010 04:48:08 -0800 (PST)
From: SriRam007
Subject: [mapguide-users] RE: Change the Icon image of the tool bar
command buttons
To: mapguide-users@lists.osgeo.org
Message-ID: <1271335688361-4907268.p...@n2.nabble.com>
Content-Type: text/plain; charset=us-ascii
Heloo Sir,
thanks again
It is now working.
--
View this message in context:
http://n2.nabble.com/Change-the-Icon-image-of-the-tool-bar-command-buttons-tp4906988p4907268.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
--
Message: 12
Date: Thu, 15 Apr 2010 16:14:51 +0200
From: Balogh ?d?m
Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4
To:
Message-ID: <3a79534b2183457cb231879b5085f...@gds2000.hu>
Content-Type: text/plain; charset="iso-8859-2"
Skipped content of type multipart/alternative-- next
part --
g++ -O2 -g -pipe -march=x86-64 -mcpu=i686 -fno-use-cxa-atexit -fexceptions
-DACE_HAS_SVC_DLL=1 -O2 -g -pipe -march=x86-64 -mcpu=i686 -fno-use-cxa-atexit
-fexceptions -o .libs/mgserver Serv
erCoreBuild.o -L/usr/local/fdo-3.5.0/lib -L/usr/local/src/MgDev-2.2.4731/Oem/ACE/ACE_wrappers/ace
-L/usr/local/src/MgDev-2.2.47
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Sorry for late response, KFW is right, you can remove the IFDEF and you will be able to compile on RH 5.3, 5.4 and 5.5, but the IFDEF was added to implement that functionalities, so my advice is to consider to do something "alternative". I don't know why, but the functionalities were implemented in the IFDEF in more recent releases of the DWF ToolKit (I suppose that Adobe decided to support 64 bit only in recent versions, so the ifdef in the preliminary releases was left intentionally blank, to prepare the code for new developments). Here there is a license issue, because I'm not sure that can be used in production, anyway an alternative (and valuable) solution is to upgrade the version of the DWF ToolKit in the MapGuide (if I'm not wrong, the first version supporting 64x should be 7.3.x). You just need to untar the package in the right directory, the makefile/build file has minor changes and will work perfectly. In this case you will see that the compilation will work successfully. As it is recalled in many other parts, I suggest to do a make clean and recompile everything. There is no issue about compatibility with recent kernels and/or glibc libs, I also crosschecked this. The advantage is that the code defined on that variables, is implemented in the newest version, and if you have any problem, at least you know that the toolkit is consistent. Just my suggestion, let us know if you succeeded! Stefano -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of kfw...@bombasticlocution.com Sent: Friday, 16 April, 2010 02:22 To: MapGuide Users Mail List Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 Hi Adam, Stefano is correct about removing the #ifdef statements in both Timer.cpp and Core.cpp. Remove all of the following #ifdef, #else, and #endif (making sure you remove all of the WIN32 code that is inside the _DWFCORE_WIN32_SYTEM code blocks: #ifdef _DWFCORE_X86_SYSTEM #ifdef_DWFCORE_WIN32_SYSTEM #else #ifdef_DWFCORE_LINUX_SYSTEM #else #errorCannot continue - implementation not provided for this hardware configuration #endif #endif The only code that should be left is the code that was inside the _DWFCORE_LINUX_SYSTEM code blocks, some of which you updated for 64-bit architecture. KFW On Thu, 2010-04-15 at 16:14 +0200, Balogh Ádám wrote: > Dear Kevin Webb, > > Thank you for your valuable help, > > I did everything exactly as you said, but I'm still having the same > error when building MgDev (see the attachment). > > The dwf libs are compiled smoothly. I checked the > Server/src/Core/Makefile if -ldwfcore was given for the linker, but I > found both dwftk and dwfcore was added. > Now I am hopeless again. If you could share how you could overcome > with this, I would be realy grateful. > > Thank you, > Adam > > > > Hello Adam, Rajeev, and others interested in 64bit MapGuide, > > I thought I had the problem solved last week. I got FDO and MapGuide > to > compile on a x86_64 installation of Fedora Core 8 (a torturous > experience). When I tested using the Sheboygan.mgp sample data, > mgserver > threw an FDO exception related to the ConvertUTF16toUTF32() routine in > Fdo. It was then that I realized I had contract work to do and I > didn't > have the time it would take to do a thorough job on Fdo and any other > packages needing work, so I stopped my 64-bit installation and > installed > on an ancient 32-bit box so that I could get some work done. (I am > still > debugging the 32-bit install - nothing is ever easy in this business). > > To answer your direct question, here is how I got around the DWFTimer > issues. My thinking is that DWF is an Internet Explorer only viewer, > not > much use for today's browser market. I also didn't know what other > dependencies there were for the DWF library so I just wanted to make > it > compile and not ever use the viewer. I copied the > dwfcore/x86/Core.cpp, > and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then > edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, > register name changes only. I added Timer.cpp and Core.cpp to the > dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. > > In general I had to sprinkle around alot of -fPIC directives in > numerous > spots, and I changed all of the build_oem.sh entries that were > --enable-static --disable-shared > > to > > --enable-shared --disable-static > > The change to dynamic linking required adding some -l___ and -L > directives as called for. > > I hope to go back to the 64-bit build when I have time, but maybe the > 2.2 version will be out by then. > >
Re: [mapguide-users] building 64bit openmapguide on rhel 5.4
Hi Adam, Stefano is correct about removing the #ifdef statements in both Timer.cpp and Core.cpp. Remove all of the following #ifdef, #else, and #endif (making sure you remove all of the WIN32 code that is inside the _DWFCORE_WIN32_SYTEM code blocks: #ifdef _DWFCORE_X86_SYSTEM #ifdef_DWFCORE_WIN32_SYSTEM #else #ifdef_DWFCORE_LINUX_SYSTEM #else #errorCannot continue - implementation not provided for this hardware configuration #endif #endif The only code that should be left is the code that was inside the _DWFCORE_LINUX_SYSTEM code blocks, some of which you updated for 64-bit architecture. KFW On Thu, 2010-04-15 at 16:14 +0200, Balogh Ádám wrote: > Dear Kevin Webb, > > Thank you for your valuable help, > > I did everything exactly as you said, but I'm still having the same > error when building MgDev (see the attachment). > > The dwf libs are compiled smoothly. I checked the > Server/src/Core/Makefile if -ldwfcore was given for the linker, but I > found both dwftk and dwfcore was added. > Now I am hopeless again. If you could share how you could overcome > with this, I would be realy grateful. > > Thank you, > Adam > > > > Hello Adam, Rajeev, and others interested in 64bit MapGuide, > > I thought I had the problem solved last week. I got FDO and MapGuide > to > compile on a x86_64 installation of Fedora Core 8 (a torturous > experience). When I tested using the Sheboygan.mgp sample data, > mgserver > threw an FDO exception related to the ConvertUTF16toUTF32() routine in > Fdo. It was then that I realized I had contract work to do and I > didn't > have the time it would take to do a thorough job on Fdo and any other > packages needing work, so I stopped my 64-bit installation and > installed > on an ancient 32-bit box so that I could get some work done. (I am > still > debugging the 32-bit install - nothing is ever easy in this business). > > To answer your direct question, here is how I got around the DWFTimer > issues. My thinking is that DWF is an Internet Explorer only viewer, > not > much use for today's browser market. I also didn't know what other > dependencies there were for the DWF library so I just wanted to make > it > compile and not ever use the viewer. I copied the > dwfcore/x86/Core.cpp, > and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then > edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, > register name changes only. I added Timer.cpp and Core.cpp to the > dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. > > In general I had to sprinkle around alot of -fPIC directives in > numerous > spots, and I changed all of the build_oem.sh entries that were > --enable-static --disable-shared > > to > > --enable-shared --disable-static > > The change to dynamic linking required adding some -l___ and -L > directives as called for. > > I hope to go back to the 64-bit build when I have time, but maybe the > 2.2 version will be out by then. > > Good luck! > > Kevin Webb > > > > Balogh Ádám > adatbázisgazda > GDS 2000 Kft. > 1074 Budapest, VII. ker. Dohány u. 20. III/15. > Telefon: +36-1-344-5495 > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
It was added, but some parts are not compiled because there is an IFDEF in the code which excludes the 64 bit. You can get the last dwftk (as I did). Stefano From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Balogh Ádám Sent: Thursday, 15 April, 2010 16:15 To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4 Dear Kevin Webb, Thank you for your valuable help, I did everything exactly as you said, but I'm still having the same error when building MgDev (see the attachment). The dwf libs are compiled smoothly. I checked the Server/src/Core/Makefile if -ldwfcore was given for the linker, but I found both dwftk and dwfcore was added. Now I am hopeless again. If you could share how you could overcome with this, I would be realy grateful. Thank you, Adam Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit installation and installed on an ancient 32-bit box so that I could get some work done. (I am still debugging the 32-bit install - nothing is ever easy in this business). To answer your direct question, here is how I got around the DWFTimer issues. My thinking is that DWF is an Internet Explorer only viewer, not much use for today's browser market. I also didn't know what other dependencies there were for the DWF library so I just wanted to make it compile and not ever use the viewer. I copied the dwfcore/x86/Core.cpp, and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, register name changes only. I added Timer.cpp and Core.cpp to the dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. In general I had to sprinkle around alot of -fPIC directives in numerous spots, and I changed all of the build_oem.sh entries that were --enable-static --disable-shared to --enable-shared --disable-static The change to dynamic linking required adding some -l___ and -L directives as called for. I hope to go back to the 64-bit build when I have time, but maybe the 2.2 version will be out by then. Good luck! Kevin Webb Balogh Ádám adatbázisgazda GDS 2000 Kft. 1074 Budapest, VII. ker. Dohány u. 20. III/15. Telefon: +36-1-344-5495 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] building 64bit openmapguide on rhel 5.4
Dear Kevin Webb, Thank you for your valuable help, I did everything exactly as you said, but I'm still having the same error when building MgDev (see the attachment). The dwf libs are compiled smoothly. I checked the Server/src/Core/Makefile if -ldwfcore was given for the linker, but I found both dwftk and dwfcore was added. Now I am hopeless again. If you could share how you could overcome with this, I would be realy grateful. Thank you, Adam Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit installation and installed on an ancient 32-bit box so that I could get some work done. (I am still debugging the 32-bit install - nothing is ever easy in this business). To answer your direct question, here is how I got around the DWFTimer issues. My thinking is that DWF is an Internet Explorer only viewer, not much use for today's browser market. I also didn't know what other dependencies there were for the DWF library so I just wanted to make it compile and not ever use the viewer. I copied the dwfcore/x86/Core.cpp, and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, register name changes only. I added Timer.cpp and Core.cpp to the dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. In general I had to sprinkle around alot of -fPIC directives in numerous spots, and I changed all of the build_oem.sh entries that were --enable-static --disable-shared to --enable-shared --disable-static The change to dynamic linking required adding some -l___ and -L directives as called for. I hope to go back to the 64-bit build when I have time, but maybe the 2.2 version will be out by then. Good luck! Kevin Webb Balogh Ádám adatbázisgazda GDS 2000 Kft. 1074 Budapest, VII. ker. Dohány u. 20. III/15. Telefon: +36-1-344-5495 g++ -O2 -g -pipe -march=x86-64 -mcpu=i686 -fno-use-cxa-atexit -fexceptions -DACE_HAS_SVC_DLL=1 -O2 -g -pipe -march=x86-64 -mcpu=i686 -fno-use-cxa-atexit -fexceptions -o .libs/mgserver Serv erCoreBuild.o -L/usr/local/fdo-3.5.0/lib -L/usr/local/src/MgDev-2.2.4731/Oem/ACE/ACE_wrappers/ace -L/usr/local/src/MgDev-2.2.4731/Oem/DWFTK7.1/develop/global/src/dwfcore -L/usr/local/src/ MgDev-2.2.4731/Oem/DWFTK7.1/develop/global/src/dwf -L/usr/local/src/MgDev-2.2.4731/Oem/DWFTK7.1/develop/global/src/dwfemap -L/usr/local/src/MgDev-2.2.4731/Oem/dbxml-2.3.10/install/lib -L/u sr/local/src/MgDev-2.2.4731/Common/CoordinateSystem -L/usr/local/src/MgDev-2.2.4731/Common/MdfModel -L/usr/local/src/MgDev-2.2.4731/Common/MdfParser -L/usr/local/src/MgDev-2.2.4731/Common/ Stylization -L/usr/local/src/MgDev-2.2.4731/Common/Renderers -L/usr/local/src/MgDev-2.2.4731/Common/Foundation -L/usr/local/src/MgDev-2.2.4731/Common/Geometry -L/usr/local/src/MgDev-2.2.47 31/Common/PlatformBase -L/usr/local/src/MgDev-2.2.4731/Common/MapGuideCommon -L/usr/local/src/MgDev-2.2.4731/Server/src/Common/Base -L/usr/local/src/MgDev-2.2.4731/Server/src/Common/Cache -L/usr/local/src/MgDev-2.2.4731/Server/src/Common/Manager -L/usr/local/src/MgDev-2.2.4731/Server/src/Common/Thread -L/usr/local/src/MgDev-2.2.4731/Server/src/Services/Drawing -L/usr/local/ src/MgDev-2.2.4731/Server/src/Services/Feature -L/usr/local/src/MgDev-2.2.4731/Server/src/Services/Kml -L/usr/local/src/MgDev-2.2.4731/Server/src/Services/Mapping -L/usr/local/src/MgDev-2. 2.4731/Server/src/Services/Rendering -L/usr/local/src/MgDev-2.2.4731/Server/src/Services/Resource -L/usr/local/src/MgDev-2.2.4731/Server/src/Services/ServerAdmin -L/usr/local/src/MgDev-2.2 .4731/Server/src/Services/Site -L/usr/local/src/MgDev-2.2.4731/Server/src/Services/Tile /usr/local/src/MgDev-2.2.4731/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore -luuid /usr/l ocal/src/MgDev-2.2.4731/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk -lz /usr/local/src/MgDev-2.2.4731/Oem/DWFTK7.1/develop/global/src/dwfemap/.libs/libdwfemap /usr/lib64/libexpat.so -lFDO-3.5.0 /usr/local/fdo-3.5.0/lib/libExpressionEngine.so /usr/local/fdo-3.5.0/lib/libFDO.so -L/usr/local/src/OpenSource_FDO-3.5/Thirdparty/apache/xml-xalan/c/lib -L/usr/local/src/OpenS ource_FDO-3.5/Thirdparty/apache/xml-xerces/c/lib -ldl -lxalanMsg -lxalan-c -L/usr/local/src/MgDev-2.2.4731/Oem/dbxml-2.3.10/xerces-c-src/lib -L/usr/local/src/MgDev-2.2.4731/Oem/CsMap -L/us r/local/src/MgDev-2.2.4731/Common/Security /usr/local/src/MgDev-2.2.4731/Server/src/Services/ServerAdmin/.libs/libMgServerAdminService.so /usr/local/src/MgDev-2.2.4731/Server/
Re: [mapguide-users] building 64bit openmapguide on rhel 5.4
For me, it's less about easier than about co-existing on a non-dedicated server. We're never going to get people to try MapGuide if it breaks their other applications to run it :) If we find particular problems I'm guessing that we can set specific version stuff in the apt requirements? It would be cool if, as we gradually upgrade the OEM libraries, we could switch to specifying a build rather than maintaining in our tree. This would allow us to bite off small chunks at a time. This would also force us to work directly with those communities, contributing back up the chain. While this would be more overhead, it would also be a lot less painful when upgrading the libraries. Possibly more of a discussion for internals :) Jason On 31 March 2010 22:43, Trevor Wekel wrote: > Easier to compile? Yes. The libraries will be up to date. > > Easier to ensure MapGuide stability? That's a very good question. Mixing > and matching oem libs could potentially lead to unexpected side effects but > more up to date libraries *should* have fewer bugs. > > ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Easier to compile? Yes. The libraries will be up to date. Easier to ensure MapGuide stability? That's a very good question. Mixing and matching oem libs could potentially lead to unexpected side effects but more up to date libraries *should* have fewer bugs. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Zac Spitzer Sent: March 31, 2010 5:50 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 migrating away from using all these third party libs in the oem tree on linux and use the system ones when possible is a better approach On 1 April 2010 10:34, Trevor Wekel wrote: > Hi Rajeev, > > Third party components can be very tricky business in MapGuide. For example, > Berkeley DB XML uses specific versions of xerces and xalan. These three > third party libraries should remain in sync to ensure repository stability. > In order to compile with GCC 4.4, we will need to update a significant > portion of the Oem tree. Since we are about to hit beta, I would say any > additional changes to third party / Oem libraries would have to be considered > on a case by case basis. > > Hopefully our existing set of third party libs will compile successfully on > 64 bit Linux. If not, RFC's will have to be written to get the libraries > upgraded. For example, RFC 89 > http://trac.osgeo.org/mapguide/wiki/MapGuideRfc89 was a required upgrade for > 2.2. > > As for source code modifications, yes there have been a few > (geos,swig,agg,others?). I do not know if the modifications have made it > back into their respective projects. > > Regards, > Trevor > > -Original Message- > From: mapguide-users-boun...@lists.osgeo.org > [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh > Sent: March 31, 2010 7:02 AM > To: MapGuide Users Mail List > Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 > > Hi Trevor, > > I will certainly look into this - though adam probably will get to it > sooner. Right now finally gotten around to looking at 32 bit crash of 2.0.2 > branch (had filed a bug earlier, essentially every 1/2 hr or so the process > crashes). > > As an aside, when going thru the attempt on 2.0.2, I did complie FDO 3.3.2 > on 64 bit (compiled all except a few dealing with ODBC/PostGis/Oracle, but > including MySQL) > > On a different note, lots of third party components are used with mapguide. > At some point I think I had seen in some mailing list that the source code > have been modified. Is that really so or can we instead create a packaging > that uses the latest / required binaries of those components (I can help > with that) > > thanks > rajeev > > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia http://www.ennoble.com.au http://zacster.blogspot.com +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
I concur with Zac, but I guess the timing is not right. If at some point we get around to removing the Oem src code and compare with their respective releases, I will get back to see how to move that for wider distrib. thx Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of Zac Spitzer Sent: 31 March 2010 19:50 To: MapGuide Users Mail List Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 migrating away from using all these third party libs in the oem tree on linux and use the system ones when possible is a better approach On 1 April 2010 10:34, Trevor Wekel wrote: > Hi Rajeev, > > Third party components can be very tricky business in MapGuide. For example, Berkeley DB XML uses specific versions of xerces and xalan. These three third party libraries should remain in sync to ensure repository stability. In order to compile with GCC 4.4, we will need to update a significant portion of the Oem tree. Since we are about to hit beta, I would say any additional changes to third party / Oem libraries would have to be considered on a case by case basis. > > Hopefully our existing set of third party libs will compile successfully on 64 bit Linux. If not, RFC's will have to be written to get the libraries upgraded. For example, RFC 89 http://trac.osgeo.org/mapguide/wiki/MapGuideRfc89 was a required upgrade for 2.2. > > As for source code modifications, yes there have been a few (geos,swig,agg,others?). I do not know if the modifications have made it back into their respective projects. > > Regards, > Trevor > > -Original Message- > From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh > Sent: March 31, 2010 7:02 AM > To: MapGuide Users Mail List > Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 > > Hi Trevor, > > I will certainly look into this - though adam probably will get to it > sooner. Right now finally gotten around to looking at 32 bit crash of 2.0.2 > branch (had filed a bug earlier, essentially every 1/2 hr or so the process > crashes). > > As an aside, when going thru the attempt on 2.0.2, I did complie FDO 3.3.2 > on 64 bit (compiled all except a few dealing with ODBC/PostGis/Oracle, but > including MySQL) > > On a different note, lots of third party components are used with mapguide. > At some point I think I had seen in some mailing list that the source code > have been modified. Is that really so or can we instead create a packaging > that uses the latest / required binaries of those components (I can help > with that) > > thanks > rajeev > > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia http://www.ennoble.com.au http://zacster.blogspot.com +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] building 64bit openmapguide on rhel 5.4
migrating away from using all these third party libs in the oem tree on linux and use the system ones when possible is a better approach On 1 April 2010 10:34, Trevor Wekel wrote: > Hi Rajeev, > > Third party components can be very tricky business in MapGuide. For example, > Berkeley DB XML uses specific versions of xerces and xalan. These three > third party libraries should remain in sync to ensure repository stability. > In order to compile with GCC 4.4, we will need to update a significant > portion of the Oem tree. Since we are about to hit beta, I would say any > additional changes to third party / Oem libraries would have to be considered > on a case by case basis. > > Hopefully our existing set of third party libs will compile successfully on > 64 bit Linux. If not, RFC's will have to be written to get the libraries > upgraded. For example, RFC 89 > http://trac.osgeo.org/mapguide/wiki/MapGuideRfc89 was a required upgrade for > 2.2. > > As for source code modifications, yes there have been a few > (geos,swig,agg,others?). I do not know if the modifications have made it > back into their respective projects. > > Regards, > Trevor > > -Original Message- > From: mapguide-users-boun...@lists.osgeo.org > [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh > Sent: March 31, 2010 7:02 AM > To: MapGuide Users Mail List > Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 > > Hi Trevor, > > I will certainly look into this - though adam probably will get to it > sooner. Right now finally gotten around to looking at 32 bit crash of 2.0.2 > branch (had filed a bug earlier, essentially every 1/2 hr or so the process > crashes). > > As an aside, when going thru the attempt on 2.0.2, I did complie FDO 3.3.2 > on 64 bit (compiled all except a few dealing with ODBC/PostGis/Oracle, but > including MySQL) > > On a different note, lots of third party components are used with mapguide. > At some point I think I had seen in some mailing list that the source code > have been modified. Is that really so or can we instead create a packaging > that uses the latest / required binaries of those components (I can help > with that) > > thanks > rajeev > > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia http://www.ennoble.com.au http://zacster.blogspot.com +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Hi Rajeev, Third party components can be very tricky business in MapGuide. For example, Berkeley DB XML uses specific versions of xerces and xalan. These three third party libraries should remain in sync to ensure repository stability. In order to compile with GCC 4.4, we will need to update a significant portion of the Oem tree. Since we are about to hit beta, I would say any additional changes to third party / Oem libraries would have to be considered on a case by case basis. Hopefully our existing set of third party libs will compile successfully on 64 bit Linux. If not, RFC's will have to be written to get the libraries upgraded. For example, RFC 89 http://trac.osgeo.org/mapguide/wiki/MapGuideRfc89 was a required upgrade for 2.2. As for source code modifications, yes there have been a few (geos,swig,agg,others?). I do not know if the modifications have made it back into their respective projects. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh Sent: March 31, 2010 7:02 AM To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Hi Trevor, I will certainly look into this - though adam probably will get to it sooner. Right now finally gotten around to looking at 32 bit crash of 2.0.2 branch (had filed a bug earlier, essentially every 1/2 hr or so the process crashes). As an aside, when going thru the attempt on 2.0.2, I did complie FDO 3.3.2 on 64 bit (compiled all except a few dealing with ODBC/PostGis/Oracle, but including MySQL) On a different note, lots of third party components are used with mapguide. At some point I think I had seen in some mailing list that the source code have been modified. Is that really so or can we instead create a packaging that uses the latest / required binaries of those components (I can help with that) thanks rajeev ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Hi Trevor, I will certainly look into this - though adam probably will get to it sooner. Right now finally gotten around to looking at 32 bit crash of 2.0.2 branch (had filed a bug earlier, essentially every 1/2 hr or so the process crashes). As an aside, when going thru the attempt on 2.0.2, I did complie FDO 3.3.2 on 64 bit (compiled all except a few dealing with ODBC/PostGis/Oracle, but including MySQL) On a different note, lots of third party components are used with mapguide. At some point I think I had seen in some mailing list that the source code have been modified. Is that really so or can we instead create a packaging that uses the latest / required binaries of those components (I can help with that) thanks rajeev Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of Trevor Wekel Sent: 31 March 2010 01:19 To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Hi Rajeev, You will need to create 64 bit FDO libraries before compiling MapGuide. MapGuide 2.2 should be built against FDO 3.5.0. I have started working on Linux build and packaging scripts for both FDO and MapGuide. The scripts are a work in progress but they might get you somewhere on a 64 bit machine. I haven't tried them yet. http://svn.osgeo.org/fdo/branches/3.5/install/ - buildall.sh, buildfdocore.sh, buildfdoprovider.sh http://svn.osgeo.org/mapguide/trunk/Installer/scripts/ - build.sh, revnum.pl If you make some headway with the 64bit Linux builds and would like to make changes to these scripts, please let me know. A couple of cautionary words before you begin: - MapGuide 2.2 will only build on GCC 4.1. Trying to use GCC 4.4 is problematic to say the least. - Check out http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. It could save you a few hours. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh Sent: March 30, 2010 10:56 PM To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Thanks for sharing that - though Trevor has explicitly said that 2.2 is the one that might be 64 bit, let me share my experience on Centos 5.5 (btw you can use the 32 bit build on 64 bit machine) **Trevor - my interest in 64 bit was actually to use it against 64 bit java (and the current plan for not doing 64 bit web components, in my opinion, restricts utility to a large extent. I also did -fPIC - infact lots of the makefiles did not pass on the parameters (i.e. the makefiles being generated do not follow good practices of taking things from environment). So created a script wrapper around gcc/cc/g++/c++ (yup all the 4 compiler commands are used by the make files) The DwfCore needed to be tweaked (for the Tick32) and some compile directives needed to be checked. I got a sense looking at these files and one of the core component files (I forget which one) had assumptions builit in about size of int and there were issues fixed for 16 to 32 bit conversion, though I think we did a cursory fix the end result was that though successful compilation happened, the thing did not run. Anyway I will look at 2.2 branch and retry 64 bit compilation. thx Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of kfw...@bombasticlocution.com Sent: 30 March 2010 21:43 To: MapGuide Users Mail List Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit in
Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 - Found word(s) list error in the Text body [Keyword]
Dear Rajeev, I work on this compilation for the second week now, I still haven't given up. Once I manage doing it I will send a step-by-step storyboard of building mapguide opensource on 64 bit Linux. Thank you for sharing your experience. I will probably start from the beginning again, as Trevor suggested, checking out source from svn... Regards, Adam - Original Message - From: "Rajeev Singh" To: "MapGuide Users Mail List" Cc: Sent: Tuesday, March 30, 2010 8:07 PM Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 - Found word(s) list error in the Text body [Keyword] Adam, I will be grateful if you could share your learnings on 64 bit build. I tried with 2.0.2 (the one downloadable) and though after herculean efforts I managed to compile stuff (mix-match etc etc), the final thing did not run (it went into some weird loop - 100% cpu, mem consumption - so much so that I could barely kill the process) thanks rajeev Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of Trevor Wekel Sent: 30 March 2010 11:17 To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 [Keyword] Are you compiling against trunk? The 2.1 branch will probably not compile on 64 bit. Some of the third party projects still require atomic.h. Please reference http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. This may correct AtomicDecrement and AtomicIncrement. Try using the default png and png-devel libraries from RHEL5.4. This may correct png_check_sig. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of ad...@geoform.hu Sent: March 30, 2010 7:16 AM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4 [Keyword] Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcor e: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Hi Rajeev, You will need to create 64 bit FDO libraries before compiling MapGuide. MapGuide 2.2 should be built against FDO 3.5.0. I have started working on Linux build and packaging scripts for both FDO and MapGuide. The scripts are a work in progress but they might get you somewhere on a 64 bit machine. I haven't tried them yet. http://svn.osgeo.org/fdo/branches/3.5/install/ - buildall.sh, buildfdocore.sh, buildfdoprovider.sh http://svn.osgeo.org/mapguide/trunk/Installer/scripts/ - build.sh, revnum.pl If you make some headway with the 64bit Linux builds and would like to make changes to these scripts, please let me know. A couple of cautionary words before you begin: - MapGuide 2.2 will only build on GCC 4.1. Trying to use GCC 4.4 is problematic to say the least. - Check out http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. It could save you a few hours. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh Sent: March 30, 2010 10:56 PM To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Thanks for sharing that - though Trevor has explicitly said that 2.2 is the one that might be 64 bit, let me share my experience on Centos 5.5 (btw you can use the 32 bit build on 64 bit machine) **Trevor - my interest in 64 bit was actually to use it against 64 bit java (and the current plan for not doing 64 bit web components, in my opinion, restricts utility to a large extent. I also did -fPIC - infact lots of the makefiles did not pass on the parameters (i.e. the makefiles being generated do not follow good practices of taking things from environment). So created a script wrapper around gcc/cc/g++/c++ (yup all the 4 compiler commands are used by the make files) The DwfCore needed to be tweaked (for the Tick32) and some compile directives needed to be checked. I got a sense looking at these files and one of the core component files (I forget which one) had assumptions builit in about size of int and there were issues fixed for 16 to 32 bit conversion, though I think we did a cursory fix the end result was that though successful compilation happened, the thing did not run. Anyway I will look at 2.2 branch and retry 64 bit compilation. thx Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of kfw...@bombasticlocution.com Sent: 30 March 2010 21:43 To: MapGuide Users Mail List Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit installation and installed on an ancient 32-bit box so that I could get some work done. (I am still debugging the 32-bit install - nothing is ever easy in this business). To answer your direct question, here is how I got around the DWFTimer issues. My thinking is that DWF is an Internet Explorer only viewer, not much use for today's browser market. I also didn't know what other dependencies there were for the DWF library so I just wanted to make it compile and not ever use the viewer. I copied the dwfcore/x86/Core.cpp, and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, register name changes only. I added Timer.cpp and Core.cpp to the dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. In general I had to sprinkle around alot of -fPIC directives in numerous spots, and I changed all of the build_oem.sh entries that were --enable-static --disable-shared to --enable-shared --disable-static The change to dynamic linking required adding some -l___ and -L directives as called for. I hope to go back to the 64-bit build when I have time, but maybe the 2.2 version will be out by then. Good luck! Kevin Webb On Tue, 2010-03-30 at 15:15 +0200, ad...@geoform.hu wrote: > Dear fellows, > Our office have a 64bit rhel 5.4 linux machine, that I want to use (among >
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Thanks for sharing that - though Trevor has explicitly said that 2.2 is the one that might be 64 bit, let me share my experience on Centos 5.5 (btw you can use the 32 bit build on 64 bit machine) **Trevor - my interest in 64 bit was actually to use it against 64 bit java (and the current plan for not doing 64 bit web components, in my opinion, restricts utility to a large extent. I also did -fPIC - infact lots of the makefiles did not pass on the parameters (i.e. the makefiles being generated do not follow good practices of taking things from environment). So created a script wrapper around gcc/cc/g++/c++ (yup all the 4 compiler commands are used by the make files) The DwfCore needed to be tweaked (for the Tick32) and some compile directives needed to be checked. I got a sense looking at these files and one of the core component files (I forget which one) had assumptions builit in about size of int and there were issues fixed for 16 to 32 bit conversion, though I think we did a cursory fix the end result was that though successful compilation happened, the thing did not run. Anyway I will look at 2.2 branch and retry 64 bit compilation. thx Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of kfw...@bombasticlocution.com Sent: 30 March 2010 21:43 To: MapGuide Users Mail List Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4 Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit installation and installed on an ancient 32-bit box so that I could get some work done. (I am still debugging the 32-bit install - nothing is ever easy in this business). To answer your direct question, here is how I got around the DWFTimer issues. My thinking is that DWF is an Internet Explorer only viewer, not much use for today's browser market. I also didn't know what other dependencies there were for the DWF library so I just wanted to make it compile and not ever use the viewer. I copied the dwfcore/x86/Core.cpp, and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, register name changes only. I added Timer.cpp and Core.cpp to the dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. In general I had to sprinkle around alot of -fPIC directives in numerous spots, and I changed all of the build_oem.sh entries that were --enable-static --disable-shared to --enable-shared --disable-static The change to dynamic linking required adding some -l___ and -L directives as called for. I hope to go back to the 64-bit build when I have time, but maybe the 2.2 version will be out by then. Good luck! Kevin Webb On Tue, 2010-03-30 at 15:15 +0200, ad...@geoform.hu wrote: > Dear fellows, > Our office have a 64bit rhel 5.4 linux machine, that I want to use (among > others) for openmapguide. I passed through fdo install, and build_oem.sh. > I downloaded some third party libraries newer then what was provided in > the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's > clean and tidy. Now I faced errors during build, that I cannot resolve > alone. Can anyone help, please? Adam > > /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: > undefined reference to `DWFCore::AtomicDecrement(int volatile*)' > /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: > undefined reference to `DWFCore::AtomicIncrement(int volatile*)' > /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined > reference to `png_check_sig' > /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: > undefined reference to `DWFCore::DWFTimer::Tick64()' > /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined > reference to `png_set_gray_1_2_4_to_8' > /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcor e: > undefined reference to `DWFCore::DWFTimer::Tick32()' > c
Re: [mapguide-users] building 64bit openmapguide on rhel 5.4
Hello Adam, Rajeev, and others interested in 64bit MapGuide, I thought I had the problem solved last week. I got FDO and MapGuide to compile on a x86_64 installation of Fedora Core 8 (a torturous experience). When I tested using the Sheboygan.mgp sample data, mgserver threw an FDO exception related to the ConvertUTF16toUTF32() routine in Fdo. It was then that I realized I had contract work to do and I didn't have the time it would take to do a thorough job on Fdo and any other packages needing work, so I stopped my 64-bit installation and installed on an ancient 32-bit box so that I could get some work done. (I am still debugging the 32-bit install - nothing is ever easy in this business). To answer your direct question, here is how I got around the DWFTimer issues. My thinking is that DWF is an Internet Explorer only viewer, not much use for today's browser market. I also didn't know what other dependencies there were for the DWF library so I just wanted to make it compile and not ever use the viewer. I copied the dwfcore/x86/Core.cpp, and dwfcore/x86/Timer.cpp files into the dwfcore directory. I then edited Timer.cpp to change the 32-bit assembler into 64-bit assembler, register name changes only. I added Timer.cpp and Core.cpp to the dwfcore Makefile and Makefile.am for the libdwfcore_la_SOURCES tag. In general I had to sprinkle around alot of -fPIC directives in numerous spots, and I changed all of the build_oem.sh entries that were --enable-static --disable-shared to --enable-shared --disable-static The change to dynamic linking required adding some -l___ and -L directives as called for. I hope to go back to the 64-bit build when I have time, but maybe the 2.2 version will be out by then. Good luck! Kevin Webb On Tue, 2010-03-30 at 15:15 +0200, ad...@geoform.hu wrote: > Dear fellows, > Our office have a 64bit rhel 5.4 linux machine, that I want to use (among > others) for openmapguide. I passed through fdo install, and build_oem.sh. > I downloaded some third party libraries newer then what was provided in > the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's > clean and tidy. Now I faced errors during build, that I cannot resolve > alone. Can anyone help, please? Adam > > /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: > undefined reference to `DWFCore::AtomicDecrement(int volatile*)' > /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: > undefined reference to `DWFCore::AtomicIncrement(int volatile*)' > /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined > reference to `png_check_sig' > /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: > undefined reference to `DWFCore::DWFTimer::Tick64()' > /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined > reference to `png_set_gray_1_2_4_to_8' > /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore: > undefined reference to `DWFCore::DWFTimer::Tick32()' > collect2: ld returned 1 exit status > make[3]: *** [mgserver] Error 1 > make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/local/src/MgDev/Server' > make: *** [all-recursive] Error 1 > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Hello list, MapGuide 2.0 and 2.1 have never been validated as a 64 bit build. MapGuide 2.2 will be the first 64 bit capable release. For the beta (coming soon), we may not have 64 bit versions built and packaged. We are planning to address this before the final 2.2 release. From the last PSC meeting http://trac.osgeo.org/mapguide/wiki/PscMeeting02-04-2010, here is what was discussed: "Expected release is 32 and 64 bit for windows (with 32bit webtier/apache/php), and 32 bit linux. Trevor will look into problems with 64bit linux support." Once I have completed the 32 bit build and packaging for Linux, I will investigate build and packaging of the 64 bit Server for Linux. If all goes well, MapGuide 2.2 will have both 32 and 64 bit Server binaries available for Windows, RedHat/CentOS 5.4, and Ubuntu 9.10. The Web Extensions binaries will likely be 32 bit. There have already been requests for 64 bit Web Extensions on the -internals list. If time permits, the PSC may re-evaluate the feasibility of a 64 bit Web Extensions. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Rajeev Singh Sent: March 30, 2010 12:07 PM To: MapGuide Users Mail List Cc: ad...@geoform.hu Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Adam, I will be grateful if you could share your learnings on 64 bit build. I tried with 2.0.2 (the one downloadable) and though after herculean efforts I managed to compile stuff (mix-match etc etc), the final thing did not run (it went into some weird loop - 100% cpu, mem consumption - so much so that I could barely kill the process) thanks rajeev Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of Trevor Wekel Sent: 30 March 2010 11:17 To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Are you compiling against trunk? The 2.1 branch will probably not compile on 64 bit. Some of the third party projects still require atomic.h. Please reference http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. This may correct AtomicDecrement and AtomicIncrement. Try using the default png and png-devel libraries from RHEL5.4. This may correct png_check_sig. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of ad...@geoform.hu Sent: March 30, 2010 7:16 AM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4 Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcor e: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users __
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Adam, I will be grateful if you could share your learnings on 64 bit build. I tried with 2.0.2 (the one downloadable) and though after herculean efforts I managed to compile stuff (mix-match etc etc), the final thing did not run (it went into some weird loop - 100% cpu, mem consumption - so much so that I could barely kill the process) thanks rajeev Rajeev K. Singh IntelliPlanner Software Systems, Inc. West Windsor, NJ (USA) / New Delhi (India) +1.609.945.4927 (o) / +1.203.558.3224 (c) +91.11.4672 6635(o) / +91.995 841 1064(c) This mail contains proprietary and confidential information. Please destroy it if you received it by mistake and notify the sender. -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org]on Behalf Of Trevor Wekel Sent: 30 March 2010 11:17 To: MapGuide Users Mail List Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4 Are you compiling against trunk? The 2.1 branch will probably not compile on 64 bit. Some of the third party projects still require atomic.h. Please reference http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. This may correct AtomicDecrement and AtomicIncrement. Try using the default png and png-devel libraries from RHEL5.4. This may correct png_check_sig. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of ad...@geoform.hu Sent: March 30, 2010 7:16 AM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4 Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcor e: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
Are you compiling against trunk? The 2.1 branch will probably not compile on 64 bit. Some of the third party projects still require atomic.h. Please reference http://trac.osgeo.org/mapguide/wiki/CompilingMapGuide22. This may correct AtomicDecrement and AtomicIncrement. Try using the default png and png-devel libraries from RHEL5.4. This may correct png_check_sig. Regards, Trevor -Original Message- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of ad...@geoform.hu Sent: March 30, 2010 7:16 AM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] building 64bit openmapguide on rhel 5.4 Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] building 64bit openmapguide on rhel 5.4
Dear fellows, Our office have a 64bit rhel 5.4 linux machine, that I want to use (among others) for openmapguide. I passed through fdo install, and build_oem.sh. I downloaded some third party libraries newer then what was provided in the tarball (namely: libpng, libjped, freetype and agg) Otherwise it's clean and tidy. Now I faced errors during build, that I cannot resolve alone. Can anyone help, please? Adam /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicDecrement(int volatile*)' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::AtomicIncrement(int volatile*)' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_check_sig' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwf/.libs/libdwftk: undefined reference to `DWFCore::DWFTimer::Tick64()' /usr/local/src/MgDev/Common/Renderers/.libs/libMgRenderers.so: undefined reference to `png_set_gray_1_2_4_to_8' /usr/local/src/MgDev/Oem/DWFTK7.1/develop/global/src/dwfcore/.libs/libdwfcore: undefined reference to `DWFCore::DWFTimer::Tick32()' collect2: ld returned 1 exit status make[3]: *** [mgserver] Error 1 make[3]: Leaving directory `/usr/local/src/MgDev/Server/src/Core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/MgDev/Server/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/MgDev/Server' make: *** [all-recursive] Error 1 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
