Re: [gomd-devel] Makefile?

[Matthias Rechenburg]

Hi from Matt,

On Montag 04 August 2003 00:20, Gian Paolo Ghilardi wrote:
> Hi roeles.
> Thanks for your help.
> I'm investigating this problem. :)
>
> There's something strange.
> Matt: can you test the CVS compilation stuff?
> I'd like to know if this is a make vars problem.

i tested it now, checked out the latest stuff and
run into linking probs. It compiles ok but the gomd
does not link on my RH 8.0 system 
(commoncpp-1.0.13 and libgtop-2.0.2 installed in /usr/lib/ + /usr/include/..)
There may be some issues with the include paths e.g.
the libgtop-2.0 is libgtop-2.0.2 on my system but even
after adjusting this manually i was not yet able to fix it yet.
(sorry, heavy busy again)

btw: the Makefile output during "make" is nice ... ;) ... but
less informations about the compiling procedure makes
it harder for people to debug. I would suggest that the
lines which are used for compiling are printed out .... even 
if it looks much nicer as it is now ;)  (just my mind)

>
> CU.
> <rejected>
>
> ----- Original Message -----
> From: <address@hidden>
> To: <address@hidden>
> Sent: Sunday, August 03, 2003 8:46 PM
> Subject: [gomd-devel] Makefile?
>
> > Hi _rejected_ ,
> >
> > As you prolly recall I couldn't compile gomd last time I was testing. The
> > 1st problem I had was an error 127. I think this means the desired target
> > is not found.
> > When I removed all the .o extensions in gomd/daemon/Makefile line 11
> > (OBJECTS), it wasn't make who gave the error but my compiler. Since I use
> > the latest version of commoncpp(1.0.13), I
> > guess it has to do with finding it's headerfiles. My compiler, g++ in
> > this case, couldn't find the file cc++/socket.H. When I looked the file
> > up with locate it was in /usr/local/include/cc++2/(cc++/socket.h)
> > So what I did was add -I/usr/local/include/cc++2/ -
> > I/usr/local/include/cc++2/cc++ to the INCFLAGS (line 9) in the same
> > makefile. Unfortunately, it is not using this when it is trying to
> > compile the target (gomdSearcher in my case).
> > My guess is that the Makefile has to contain a rule to make these objects
> > (make automatically adds .cpp or .c to it afaik).
> > What make runs is "CC LDFLAGS $TARGET.cpp -o $TARGET" (WHERE CC and
>
> LDFLAGS
>
> > are found in the Makefile and $TARGET is gomdSearcher in my case).
> > I cannot find this combination anywhere in this makefile and thus I
> > conclude that make somehow decides on his own to run this. My guess, as
> > said, is that you'll have to specify a rule for making these objects in
> > order to make gcc/c++/g++ include the /usr/local/include/cc++2 path
>
> using -
>
> > I.
> >
> > Now, I don't have lots of experience with makefile's so I would like to
> > invite other people to check CVS out and try aswell and look at it.
> >
> > cheers,
> >
> > Roeles
<snip>

have a nice evening all together,

Matt
-- 
E-mail  :  address@hidden
www     : http://www.openmosixview.com
an openMosix-cluster management GUI

Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the universe trying to produce
bigger and better idiots. So far, the universe is winning.