[mapguide-internals] Anyone was able to compile mg 2.0.0 with
linux x86_64 ?
traian.stanev at autodesk.com
Thu Apr 3 10:36:45 EDT 2008
Everything you say sounds about right. I remember having to do all these when I compiled on x64.
It is ok to hack around the atomic stuff in DWF, because MapGuide does not use it.
Ironically dwf_max is something I added because a while back I was getting gcc errors about redefinition of max. Your solution of using STL max is better.
Last time I tried this, I got the mg server to briefly run, before going down in flames when it hit places which cast pointers in the wrong way. I fixed some of these in the UTF16 string conversion code, but there were more, at which point I gave up.
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-
> internals-bounces at lists.osgeo.org] On Behalf Of Helio Chissini de
> Sent: Thursday, April 03, 2008 9:57 AM
> To: MapGuide Internals Mail List
> Subject: [mapguide-internals] Anyone was able to compile mg 2.0.0 with
> linux x86_64 ?
> I just gor a new machine 4 procs full 64 bits, and tried to compile
> pristine mg 2 package. I have a 64 bits linux installed using just 64
> bits libraries.
> First, i need add a CPPFLAGS=" -fPIC" global due to whole static libs
> To build Oem, i needed remove the explicit -march=i686 on some
> Makefiles ( ex. SWIGEx )
> dwftoolkit have some own issues, one with atomic, and i was not able to
> solve and just add a dummy function for now ( i'm not the best kernel
> expert ), Tick32 and Tick64, and dwf_max, which not play nice with new
> gcc , i substituted for STL <algorithm> max, min
> So, Oem built i was able to start mapguide, but then got stuck on
> mgRenderer, that got undefineds in gdFontCacheSetup Fdo*::Create
> I stopped here last night.
> Anyone can have some input ?
> Helio Chissini de Castro
> KDE Project South America Primary Contact
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
More information about the mapguide-internals