Re: [Opengc-devel] building opengc under redhat 7.3

[Damion S. <dam...@ho...>]

Hi,

I think I've found you're problem There's a function called "round" in
geo_pos.h (under Math) which on my Mandrake box was conflicting with a
stdlib implementation of a function with the same name. I commented it out,
and it worked fine. On my Windows machine, this function is apparently not
defined by default and I'm assuming something similar is happening on your
Redhat system. This error prevents latlongc.o from being generated, which is
what you were seeing.

Try removing the comment in front of the declaration of round geo_pos.h - if
this works on your system and my Windows machine, I'll assume there's a
problem with Mandrake and concoct a fix (maybe renaming the round function
to ogcRound or something).

-Damion-

----- Original Message -----
From: "Rick Marsico" <ri...@cc...>
To: <da...@op...>
Sent: Wednesday, October 23, 2002 12:52 PM
Subject: Re: [Opengc-devel] building opengc under redhat 7.3


> Damion,
>
> I'm in the process of re-downloading now.  When in ccmake, I specify the
> build directory, correct?  Perhaps this is where I'm getting things
> confused?
>
> Rick
>
> Damion Shelton wrote:
>
> > Hi,
> >
> > I've also read your more recent message.... using CMake is the correct
> > thing to do. The make and configure scripts in the CVS repository are
> > no longer functional, as you discovered.
> >
> >> Prior to these statements, I see a number of warning statements
> >> ending with "does not give a valid preprocessing token" (e.g.,
> >> ../../Source/DataSources/ogcDataSource.h:422:3: warning: pasting "->"
> >> and "Wind_Velocity" does not givie a valid preprocessing token).
> >
> >
> > I'm not sure why these warnings are appearing, but they don't indicate
> > a problem. They show up on my Linux system as well, although not under
> > Windows. I'll have to do some reading to figure out what's happening
> > (they are caused by my use of macros in the ogcDataSource.h file, but
> > I'm not sure why - the syntax is legal and the code compiles as
> > expected).
> >
> > As to your current problem with latlongc.o not being available....
> > that's pretty strange. When was your CVS last updated? One thing I
> > might suggest is to completely delete both your current CVS and build
> > directories, download a fresh copy, and try rebuilding from scratch.
> > It's possible something got messed up when you used the configure
> > scripts.
> >
> > Are you using separate build and source directories? I.e., your source
> > directory is named ~/opengc and your build directory is ~/opengcbin
> > (or something similar)? If not, I'd suggest doing this under the
> > assumption that the makefiles present in the repository could be
> > interfering with the makefiles generated by CMake. Incidentally, the
> > executable is named OpenGC (note capitalization), and should appear in
> > the root of the build directory (i.e. ~/opengcbin/OpenGC ).
> >
> > Let me know how it goes - I'd like to make sure I'm not the only
> > person who can build OpenGC!
> >
> > -Damion-
> >
> > _________________________________________________________________
> > Internet access plans that fit your lifestyle -- join MSN.
> > http://resourcecenter.msn.com/access/plans/default.asp
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by: Influence the future of Java(TM)
> > technology. Join the Java Community Process(SM) (JCP(SM)) program now.
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
> >
> > _______________________________________________
> > Opengc-devel mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opengc-devel
>