Date: Fri, 15 Jul 2016 19:12:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 209528] net/opensips: 2.1.2 fails to build on sparc64 10.3-STABLE Message-ID: <bug-209528-13-4d9FgtiXJN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209528-13@https.bugs.freebsd.org/bugzilla/> References: <bug-209528-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209528 --- Comment #1 from Euan Thoms <euan@potensol.com> --- (In reply to Dima Veselov from comment #0) That is strange. I don't remember making many changes to the port between 2= .1.0 and 2.1.2. Certainly nothing that should effect the building of net_udp. Please try again with the latest port version once it's been committed (2.1= .3). I suspect it only needs a small patch to include a FreeBSD specific header = for a data-type which differs between x86 and SPARC64. It seems to be a casting issue, so perhaps a simple explicit cast to the correct data type will fix = it. I've noticed a lot of bad code in this regard on other projects, normally it just creates a compiler warning. Bad data type casting can lead to bugs and sometimes not, depending on the runtime conditions. But perhaps one platfor= m is more strict about it, or handles the data types slightly differently. The question is, why did it appear in a minor point release? It's difficult for me to work on this, I don't have access to any SPARC64 hardware. Dima, do you have any experience with 'C' programming? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209528-13-4d9FgtiXJN>