Re: [Ekiga-devel-list] Ekiga call does not reach established state

[Matthias Apitz <guru Sisis de>]

El día Friday, May 16, 2008 a las 10:25:52PM +0200, Matthias Schneider escribió:

> Quoting Matthias Apitz <matthias apitz oclc org>:
> 
> > El día Thursday, May 15, 2008 a las 08:09:36AM +0200, Matthias Schneider
> > escribió:
> >
> > > Hi Emilio,
> > >
> > > have you tried any recent ekiga/opal/ptlib to see if your problem still
> > exists?
> > >
> > > Matthias
> >
> > Hi,
> >
> > I have just SVN updated all (ekiga/opal/ptlib), but building of PTLib
> > fails (see nohup.out attached);
> >
> > what can/should I do?
> >
> > 	matthias
> >
> > --
> > Matthias Apitz
> 
> Hi,
> this is something what only happens on freebsd, but not on linux. I have scanned
> possible plaes for suspicious #ifdefs, but I could not find anything. But it
> should be easy to find out why the definition of PIPAddress and friends is not
> recognized. They are defined in the PTLIB headers...

Hi Matthias,

No, this would happen on any system; I figured out what was wrong; the
'gmake' (and as well the 'configure' step) of PTLIB assumes that the
include files are already placed in system's space /usr/local/include
(to where they get later with 'gmake install') and not in your current
workspace; in my case there have been older header files below
/usr/local/include/ptlib and /usr/local/include/ptclib; I copied over by
hand the actual ones with:

# cp ptlib/include/ptlib.h /usr/local/include
# cp ptlib/include/ptbuildopts.h /usr/local/include
# mkdir /usr/local/include/ptlib
# cp ptlib/include/ptlib/*.h /usr/local/include/ptlib
# mkdir /usr/local/include/ptclib
# cp ptlib/include/ptclib/*.h /usr/local/include/ptclib
# mkdir -p /usr/local/include/ptlib/unix/ptlib
# cp ptlib/include/ptlib/unix/ptlib/*.h /usr/local/include/ptlib/unix/ptlib

and then PTLIB builds fine;

sill building Opal and Ekiga and let you know...

	Emilio

-- 
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <matthias apitz oclc org> - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on Usenet and in e-mail?