| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
I did recently add more USE_SSL defines to the reTURN code. Perhaps the linux builds don't set the pre-processor define correctly.ScottOn Mon, May 9, 2016 at 8:43 AM, Mateus Bellomo <mateusbellomo@xxxxxxxxx> wrote:author: Scott Godindate: 2016-04-06 12:58:06SHA1 id: e3958145c62d0d5237414e535ca451d91ebffa76By the way, I don't know what information I should give you to identify that commit so I will put here what I see in the gitk window:I will check again later (I'm going to a class now) if I could find the problem with the USE_SSL.(just the ifdef not what was inside of it) added in that commit and it is compiling now. I think the flag USE_SSL is not being set as it supposed to be.#endifI don't know if there is a fancy way (I have never used gitk) to do this but I find the commit that change /resiprocate/reTurn repo and I commented all the#ifdef USE_SSL2016-05-09 7:10 GMT-03:00 Daniel Pocock <daniel@xxxxxxxxxx>:
On 07/05/16 19:28, Mateus Bellomo wrote:
> I tried to compile again the reSIProcate and I'm getting the same error
> (I'm running on Debian jessie 8.3 and I just clone again the reSIProcate
> repository).
>
> Maybe some of the last commits caused it (the version I got like one
> month ago wasn't with this issue).
>
Could you try looking through the history of that source file or that
part of the tree with gitk and see if you can spot any changes there?
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel