Date: Tue, 10 Dec 2013 11:42:17 +0300 From: David Naylor <dbn@freebsd.org> To: Joe Nosay <superbisquit@gmail.com> Cc: ports <ports@freebsd.org>, kde-freebsd <kde-freebsd@kde.org> Subject: Re: [kde-freebsd] Error using CMake similar to error from earlier list post Message-ID: <4799985.u5Ux28jmlm@dragon.dg> In-Reply-To: <CA%2BWntOskh95EE_wMw6N_Msi5H=2TBJ1n7mW_qRD88gG=F0XkvA@mail.gmail.com> References: <CA%2BWntOtukTye4fut8LrDmNE5gbyXZQHXfBU5D=Aq2%2Bao%2BP-K-Q@mail.gmail.com> <CA%2BWntOtxSpiV=MEXrsg06_9ixRVvR1MgDhovL9PQ4BGxV_AstQ@mail.gmail.com> <CA%2BWntOskh95EE_wMw6N_Msi5H=2TBJ1n7mW_qRD88gG=F0XkvA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1527311.DXGiulpyVg Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="ISO-8859-1" Hi Joe, I'm listening! I've read through your thread on KDE-FreeBSD and Ports-FreeBSD however I am a bit fuzzy as to the issues. Are these specific to clang, FreeBSD >= 10 or some other trigger? How would I go about reproducing these errors? I'm happy to work with you to resolve these issues. Regards On Tuesday, 10 December 2013 04:25:58 Joe Nosay wrote: > On Mon, Dec 9, 2013 at 11:18 PM, Joe Nosay <superbisquit@gmail.com> wrote: > > ---------- Forwarded message ---------- > > From: Joe Nosay <superbisquit@gmail.com> > > Date: Sun, Dec 8, 2013 at 6:38 PM > > Subject: Re: Error using CMake similar to error from earlier list post > > To: kde-freebsd <kde-freebsd@kde.org> > > > > On Sat, Dec 7, 2013 at 3:45 PM, Joe Nosay <superbisquit@gmail.com> wrote: > >> On Fri, Dec 6, 2013 at 7:50 PM, Joe Nosay <superbisquit@gmail.com> wrote: > >>> https://www.mail-archive.com/kde-freebsd@kde.org/msg15778.html > >>> > >>> Is there a similar fix for this? > >>> > >>> Thanks. > >> > >> Now would > >> " > >> > >> +Build fix for clang. > >> > >> + > >> + error: use of undeclared identifier 'pthread_mutex_lock' > >> + error: use of undeclared identifier 'pthread_mutex_unlock' > >> + error: use of undeclared identifier 'pthread_self' > >> + error: use of undeclared identifier 'pthread_mutex_init' > >> + error: use of undeclared identifier 'pthread_mutex_destroy' > >> + > >> +--- > >> kopete/protocols/jabber/googletalk/libjingle/talk/base/ssladapter.cc.or > >> ig>> > >> 2013-11-04 01:20:09.000000000 +0200 > >> > >> ++++ > >> kopete/protocols/jabber/googletalk/libjingle/talk/base/ssladapter.cc > >> > >> 2013-11-04 01:20:20.000000000 +0200 > >> > >> +@@ -29,6 +29,7 @@ > >> + > >> + #ifdef POSIX > >> + extern "C" { > >> ++#include <pthread.h> > >> + #include <unistd.h> > >> + } > >> + #endif" > >> > >> Be the appropriate fix for > >> > >> > >> /usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDeviceTh > >> read.cpp:58:30: error: use of undeclared identifier 'pthread_self'>> > >> if (pthread_setschedparam (pthread_self(), SCHED_FIFO, > >> ¶m) != 0) {} > >> > >> ^ > >> > >> /usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDeviceTh > >> read.cpp:131:30: error: use of undeclared identifier 'pthread_self'>> > >> if (pthread_setschedparam (pthread_self(), SCHED_FIFO, > >> ¶m) != 0) { > > > > I need to write a patch and then apply it to the script in question. > > 1. Will I need to add the patch to each part that is listed? > > > > > > > > > > > > > > > > > > Since it is suggested to build an application natively - or at least try > > to - on FreeBSD before making a port, I am trying to do such. > > > > The errors seems to be the same CLang type as the others. > > Included is the file which was modified according to the patch from the > > hyperlink stated earlier in this thread. > > Since this a CLang problem which has occurred and will occur in software > with the same or similar type of instructions, it may be of use to make a > patch for all qtX software and others with the same problem. > > > Me "Did I do the patch right?" > KDE FreeBSD "Did you hear something?" > Ports FreeBSD "Nope, not at all." > > GCC patchiness popping up here and there. I can see it and so can others. > > KDE FreeBSD "What was that?" > Ports FreeBSD "Nothing, nothing at all." > > These problems also show up on Debian and other systems transitioning to > CLang for the compiler. Errors of the same type happen on software not in > ports or natively part of kde3/4. > > KDE FreeBSD " There goes that noise again." > Ports FreeBSD "Just ignore it." --nextPart1527311.DXGiulpyVg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEABECAAYFAlKm4fwACgkQUaaFgP9pFrKZcwCcDXMb6nvyHWS3XUJDC/8kQXza 5iYAoImNHB+/xD7oyJAMM7Y6jfW6DiZI =xwKL -----END PGP SIGNATURE----- --nextPart1527311.DXGiulpyVg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4799985.u5Ux28jmlm>