[asterisk-users] Zaptel / Asterisk on Solaris

[RR]

Hi Tilghman,

Thanks for your response. Please see my response below.
On Sat, Dec 4, 2010 at 2:17 PM, Tilghman Lesher <tlesher at digium.com> wrote:

> Changes that you need to make to get Asterisk to compile reliably on
> Solaris would be welcome reports on the issue tracker.  What we have now
> are paths that worked for someone at sometime.  Adding extra include
> and library paths should not cause problems, but what really should happen
> is that the configure script should be detecting the right paths and
> automatically adding them to the Makefile variables.
>
> Our standard build script for Solaris (1.8 and trunk only) does not alter
> the source at all, but does set PATH and LD_LIBRARY_PATH to ensure that
> certain values are included, and it does compile and run (and pass) our
> unit tests.
>
>

So as mentioned in my response to Bruce, I did try to prepend these library
paths to the configure script via the LDFLAGS variable. You're right about
all the includes and library paths. The problem is, as I've mentioned
earlier, for non-developer people like me, this isn't second nature and
eveytime I have to do something like this, it's usually months or many times
years since I'd last had to build anything from source and modify something
anything in the code. So it would help if after these unit and sanity tests
that are done for whichever build/release/version, if these can be added to
the README or INSTALL notes for Solaris, for *that* build in a file like
INSTALL.solaris or something. This won't happen everytime or for every
release/, and I understand and appreciate that but it's a bit hard to get
this going whent eh only resource we have are the pages from SolarisVoIP
people which is almost 3-5 yrs old and I have not heard from Joe at
thrallingpenguin after I sent him 2 emails about 3-4 weeks ago. We'll we
more than happy to help in whatever way, if we can get a bit of hand holding
and relatively fast turnaround/attention from the developers who can just
point us in the right direction ... don't have to use up your machines, dev
cycles or testing time, we'll do all of that if we can get help in
troubleshooting the build environment.

Anyway, coming back to the point, so are you saying that I should try trunk
or 1.8 instead of mucking around with 1.6x versions? Sorry I have got back
to Asterisk after almost 3 years, so haven't kept up with where I should be
going and is it better to stick with 1.6x or just go to 1.8 as there's no
upgrades or backward compatability requirements for me.

Once I get this going, I promise to have an updated document uploaded
somewhere or will mail to the list so someone can put it on the wiki.

Thanks,

RR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20101204/dbd68efc/attachment.htm