[FreeBSD-Ports-Announce] Requirements for ports with 'LEGAL' concerns
If your port falls into any of the following categories - defines RESTRICTED - defines NO_CDROM - defines NO_PACKAGE - has a very restrictive license (not OSI approved) - has special licensing just for FreeBSD - has issues with patents - any other concern which is not currently covered by our LICENSE framework please make sure of the following things (a) the origin listed in LEGAL matches the port origin *exactly* - there should be no wildcards. Please duplicate listings if required. (b) the output of 'make -VLEGAL' matches the third column of LEGAL *exactly* If you have any questions please feel to email ports@. -- Eitan Adler ___ freebsd-ports-announce@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports-announce To unsubscribe, send any mail to freebsd-ports-announce-unsubscr...@freebsd.org
Re: Error using CMake similar to error from earlier list post
On Mon, Dec 9, 2013 at 11:18 PM, Joe Nosay superbisq...@gmail.com wrote:
-- Forwarded message --
From: Joe Nosay superbisq...@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-free...@kde.org
On Sat, Dec 7, 2013 at 3:45 PM, Joe Nosay superbisq...@gmail.com wrote:
On Fri, Dec 6, 2013 at 7:50 PM, Joe Nosay superbisq...@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.orig
2013-11-04 01:20:09.0 +0200
kopete/protocols/jabber/googletalk/libjingle/talk/base/ssladapter.cc
2013-11-04 01:20:20.0 +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/AudioDeviceThread.cpp:58:30:
error: use of undeclared identifier 'pthread_self'
if (pthread_setschedparam (pthread_self(), SCHED_FIFO,
param) != 0) {}
^
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDeviceThread.cpp:131:30:
error: use of undeclared identifier 'pthread_self'
if (pthread_setschedparam (pthread_self(), SCHED_FIFO,
param) != 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.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [kde-freebsd] Error using CMake similar to error from earlier list post
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 superbisq...@gmail.com wrote:
-- Forwarded message --
From: Joe Nosay superbisq...@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-free...@kde.org
On Sat, Dec 7, 2013 at 3:45 PM, Joe Nosay superbisq...@gmail.com wrote:
On Fri, Dec 6, 2013 at 7:50 PM, Joe Nosay superbisq...@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.0 +0200
kopete/protocols/jabber/googletalk/libjingle/talk/base/ssladapter.cc
2013-11-04 01:20:20.0 +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,
param) != 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,
param) != 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.
signature.asc
Description: This is a digitally signed message part.
Wedding Invitation Of Matthew 22, Scripture Now Being Fulfilled!
This extraordinary prophecy/wedding invitation can be read in any language at [1]www.revelation12.ca The kingdom of heaven is like unto a certain king, which made a marriage for his son, And sent forth his servants to call them that were bidden to the wedding: and they would not come. (they would not come because they would not believe it was true) Amazing [2]'biblical signs' are now being seen and photographed in the skies over many nations. The 'Wedding in Heaven' is surely very close. The Lord has been indicating in recent visions to prophet Linda Newkirk that His 'tarrying' will end soon, so ask right away to be a guest, things are going to get very bad in the earth soon and you will be glad that you did! Be sure to read the update that follows the invitation. An Open Invitation To A Spectacular And Timely, Heavenly Event! Our Father in Heaven Speaks! Receive, Believe And Ask! My Blessed Child, I am your Father Yahweh, yea Jehovah, Most High God; and I come to you today to impart to you a message of My great love, of My great mercy and of My great grace! My Little One, few know, or believe, that you, Linda Newkirk, the same Linda Newkirk of Mayflower, Arkansas, are the Woman of Revelation Chapter Twelve! And, few know how you have labored, how you have travailed, how you have suffered, and how you have often wept beneath the weight of unspeakable persecution! And, all for the love of Me, for the love of My Son and for the love of humanity! Yes, few know, and of those who know, few believe! For your trials have been so great as you have travailed beneath the feet of Satan and all of his demonic hordes! Oh yes, you have travailed to bring forth My holy seed! A tiny seed indeed when it was given to you; but at this time, it has been maturing in your body for more than seventeen months! And, during this time, it has been growing in strength, power, and stature until it is, for a certainty, now a manchild! And, soon, oh so soon, it will be birthed back to My throne! But, not without you; for he is a part of you! My Child, I have told you that, as the Woman of Revelation Twelve, you are the spiritual mother of My Kingdom! What grows in you is My Kingdom Seed! It is also the seed of My Son, Jesus, who is Saviour of Humanity! All, who marry Him, will receive this seed! All, who come into My Kingdom, to work in My service, and to be a part of My Kingdom, the queens, the kings and all others, must receive this seed! None will be a part of My Kingdom, who do not have this seed! My Little One, as I have told you, soon and oh so soon, I will take you and My manchild, my now-matured holy seed, back to My throne! And, what awaits you in heaven is most surely the second greatest celebration ever to take place in heaven, the first being when My Son returned after He was crucified! Now comes another grand celebration in Heaven and in some ways, perhaps in many ways, it is even more grand than when My Son returned, but not in all ways! For this celebration, this marriage to My Son, will go on for some time; with you, My Little One, being the first to marry Him, your marriage to Him coming through the now-matured holy seed of My Son! For, you are the spiritual mother of My Kingdom, the very one, who has birthed the holy seed into the earth, which is now a manchild! My Little One, you have so often wanted these works to be finished! So often you have sought this; for you have wanted an end to the constant persecution, which is directed at you! But, you have not wanted to leave this Earth and to come into Heaven without your faithful friends! In fact, My Little One, your cries have continually come before My throne, wherein you have repeatedly asked that all clean souls be allowed to come with you and the manchild when you come to My throne! And, yes, My Child, I shall grant this request, but in an even greater way than what you ask! Surely, I will now give the grace, great grace to you, that when I come for you and the manchild, I will also take those, have been your faithful friends. But, My Little One, I extend more, and I extend it to those, who are on the streets, who are in the highways and the bi-ways! Even if they do not know if Revelation Chapter Twelve is true; and even if they do not know a thing about what you have been through, if they ask of Me with a sincere heart and a humble heart to come, I will allow many of them to come with you, even total strangers! I will answer the calls of many, even those, who are lost and who sleep under the bridges!
Ports with a broken PKGORIGIN: mail/squirrelmail-abook_import_e...
** The following ports have an incorrect PKGORIGIN ** PKGORIGIN connects packaged or installed ports to the directory they originated from. This is essential for tools like pkg_version or portupgrade to work correctly. Wrong PKGORIGINs are often caused by a wrong order of CATEGORIES after a repocopy. Please fix any errors as soon as possible. The ports tree was updated at Tue Dec 10 2013 12:37:31 UTC. - *mail/squirrelmail-abook_import_export-plugin* lamb...@lambertfam.org: /squirrelmail-abook_import_export-plugin - *mail/squirrelmail-askuserinfo-plugin* po...@freebsd.org: /squirrelmail-askuserinfo-plugin - *mail/squirrelmail-avelsieve-plugin* n...@darlow.co.uk: /squirrelmail-avelsieve-plugin - *mail/squirrelmail-calendar_file_backend-plugin* po...@freebsd.org: /squirrelmail-calendar_file_backend-plugin - *mail/squirrelmail-change_sqlpass-plugin* ite...@freebsd.org: /squirrelmail-change_sqlpass-plugin - *mail/squirrelmail-check_quota-plugin* ite...@freebsd.org: /squirrelmail-check_quota-plugin - *mail/squirrelmail-email_footer-plugin* po...@freebsd.org: /squirrelmail-email_footer-plugin - *mail/squirrelmail-login_auth-plugin* s...@lassitu.de: /squirrelmail-login_auth-plugin - *mail/squirrelmail-login_notes-plugin* po...@freebsd.org: /squirrelmail-login_notes-plugin - *mail/squirrelmail-mark_read-plugin* ite...@freebsd.org: /squirrelmail-mark_read-plugin - *mail/squirrelmail-multilogin-plugin* po...@freebsd.org: /squirrelmail-multilogin-plugin - *mail/squirrelmail-notes-plugin* po...@freebsd.org: /squirrelmail-notes-plugin - *mail/squirrelmail-notify-plugin* po...@freebsd.org: /squirrelmail-notify-plugin - *mail/squirrelmail-password_forget-plugin* n...@darlow.co.uk: /squirrelmail-password_forget-plugin - *mail/squirrelmail-pupdate-plugin* po...@freebsd.org: /squirrelmail-pupdate-plugin - *mail/squirrelmail-qmailadmin_login-plugin* po...@freebsd.org: /squirrelmail-qmailadmin_login-plugin - *mail/squirrelmail-quota_usage-plugin* po...@freebsd.org: /squirrelmail-quota_usage-plugin - *mail/squirrelmail-sasql-plugin* po...@freebsd.org: /squirrelmail-sasql-plugin - *mail/squirrelmail-secure_login-plugin* po...@freebsd.org: /squirrelmail-secure_login-plugin - *mail/squirrelmail-spam-buttons-plugin* ite...@freebsd.org: /squirrelmail-spam-buttons-plugin - *mail/squirrelmail-squirrel_logger-plugin* morin...@riken.jp: /squirrelmail-squirrel_logger-plugin - *mail/squirrelmail-timeout_user-plugin* po...@freebsd.org: /squirrelmail-timeout_user-plugin - *mail/squirrelmail-unsafe_image_rules-plugin* ite...@freebsd.org: /squirrelmail-unsafe_image_rules-plugin - *mail/squirrelmail-user_special_mailboxes-plugin* ite...@freebsd.org: /squirrelmail-user_special_mailboxes-plugin - *mail/squirrelmail-websearch-plugin* po...@freebsd.org: /squirrelmail-websearch-plugin - *mail/squirrelmail-wetteronline-plugin* po...@freebsd.org: /squirrelmail-wetteronline-plugin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: www/rt42: Fail Install
On 12/10/13 04:05, Larry Rosenman wrote: Many errors along the lines of: pkg-static: lstat(/usr/ports/www/rt42/work/stage/usr/local/lib/perl5/site_perl/5.14/RT.pm): No such file or directory What is the output of: % perl -v % make -C /usr/ports/www/rt42 -V SITE_PERL ... any mention of perl related stuff in /etc/make.conf ? Note that nowadays the approved method of choosing a different perl version than the default used by the ports is to define DEFAULT_VERSIONS= perl5=5.16 in /etc/make.conf. The ports wide current default is 5.16 but your output indicates something on your system is expecting 5.14. --- that's the cause of the problem. I've tested rt42 by building packages against several different perl versions, and the error you saw does not occur if the perl version is specified correctly and all of the dependencies are installed using the selected perl version. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Integrating Custom Ports
Hi all, I have a need to create a custom Ports tree for my organization containing custom Ports that currently do not exist as well as existing Ports modified with our organization's customizations. I intend to create a new physical category according to the instructions in the Committer's Handbook ( http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#idp65956656) where our organization's Ports will be included. This is my first foray into Ports beyond just installing what is available. So, just looking for some feedback from others doing similar. Is there someone that can provide a few pointers in putting together and managing such a system? -- Take care Rick Miller ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: www/rt42: Fail Install
On 2013-12-10 07:24, Matthew Seaman wrote: On 12/10/13 04:05, Larry Rosenman wrote: Many errors along the lines of: pkg-static: lstat(/usr/ports/www/rt42/work/stage/usr/local/lib/perl5/site_perl/5.14/RT.pm): No such file or directory What is the output of: % perl -v % make -C /usr/ports/www/rt42 -V SITE_PERL ... any mention of perl related stuff in /etc/make.conf ? Note that nowadays the approved method of choosing a different perl version than the default used by the ports is to define DEFAULT_VERSIONS= perl5=5.16 in /etc/make.conf. The ports wide current default is 5.16 but your output indicates something on your system is expecting 5.14. --- that's the cause of the problem. I've tested rt42 by building packages against several different perl versions, and the error you saw does not occur if the perl version is specified correctly and all of the dependencies are installed using the selected perl version. Cheers, Matthew # perl -v This is perl 5, version 14, subversion 4 (v5.14.4) built for amd64-freebsd Copyright 1987-2013, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using man perl or perldoc perl. If you have access to the Internet, point your browser at http://www.perl.org/, the Perl Home Page. # make -C /usr/ports/www/rt42 -V SITE_PERL /usr/local/lib/perl5/site_perl/5.14 # grep -i PERL /etc/make.conf #WITHOUT_PERL= yes #WITH_MODPERL2=yes # so I'm not sure what the issue is. I'll set DEFAULT_VERSIONS. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: www/rt42: Fail Install
On 2013-12-10 07:24, Matthew Seaman wrote: On 12/10/13 04:05, Larry Rosenman wrote: Many errors along the lines of: pkg-static: lstat(/usr/ports/www/rt42/work/stage/usr/local/lib/perl5/site_perl/5.14/RT.pm): No such file or directory What is the output of: % perl -v % make -C /usr/ports/www/rt42 -V SITE_PERL ... any mention of perl related stuff in /etc/make.conf ? Note that nowadays the approved method of choosing a different perl version than the default used by the ports is to define DEFAULT_VERSIONS= perl5=5.16 in /etc/make.conf. The ports wide current default is 5.16 but your output indicates something on your system is expecting 5.14. --- that's the cause of the problem. I've tested rt42 by building packages against several different perl versions, and the error you saw does not occur if the perl version is specified correctly and all of the dependencies are installed using the selected perl version. Cheers, Matthew Even with DEFAULT_VERSIONS set, it still fails in the same way. I can give you access. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Integrating Custom Ports
On 12/10/2013 09:37, Rick Miller wrote: Hi all, I have a need to create a custom Ports tree for my organization containing custom Ports that currently do not exist as well as existing Ports modified with our organization's customizations. I intend to create a new physical category according to the instructions in the Committer's Handbook ( http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#idp65956656) where our organization's Ports will be included. This is my first foray into Ports beyond just installing what is available. So, just looking for some feedback from others doing similar. Is there someone that can provide a few pointers in putting together and managing such a system? Rick, So the way we've been doing it is with git. I started by forking the ports tree from here: https://github.com/freebsd/freebsd-ports/ After cloning the fork to disk, I added a new remote for the original ports tree: % git remote add freebsd https://github.com/freebsd/freebsd-ports.git I then added any custom ports / patches to our fork. When I want to import changes from upstream I just go to my fork and do a new pull: % git pull freebsd master Merge any conflicts and commit. -- Kris Moore PC-BSD Software iXsystems ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Integrating Custom Ports
On Tue, Dec 10, 2013 at 11:44 AM, Kris Moore k...@pcbsd.org wrote: On 12/10/2013 09:37, Rick Miller wrote: This is my first foray into Ports beyond just installing what is available. So, just looking for some feedback from others doing similar. Is there someone that can provide a few pointers in putting together and managing such a system? Rick, So the way we've been doing it is with git. I started by forking the ports tree from here: https://github.com/freebsd/freebsd-ports/ After cloning the fork to disk, I added a new remote for the original ports tree: % git remote add freebsd https://github.com/freebsd/freebsd-ports.git I then added any custom ports / patches to our fork. When I want to import changes from upstream I just go to my fork and do a new pull: % git pull freebsd master Merge any conflicts and commit. Haha. Thanks, Kris! I was making this harder than it needed to be :) I appreciate the simple solution! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[QAT] r336079: 4x leftovers
- Remove NO_LATEST_LINK - Build ID: 20131210185601-54377 Job owner: sunp...@freebsd.org Buildtime: 3 hours Enddate: Tue, 10 Dec 2013 22:21:35 GMT Revision: r336079 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=336079 - Port:www/tinymce3 3.5.8 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20131210185601-54377-237160/tinymce3-3.5.8.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20131210185601-54377-237161/tinymce3-3.5.8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20131210185601-54377-237162/tinymce3-3.5.8.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20131210185601-54377-237163/tinymce3-3.5.8.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20131210185601-54377 redports https://qat.redports.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [kde-freebsd] Error using CMake similar to error from earlier list post
Thank you.
On Tue, Dec 10, 2013 at 3:42 AM, David Naylor d...@freebsd.org wrote:
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 superbisq...@gmail.com
wrote:
-- Forwarded message --
From: Joe Nosay superbisq...@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-free...@kde.org
On Sat, Dec 7, 2013 at 3:45 PM, Joe Nosay superbisq...@gmail.com
wrote:
On Fri, Dec 6, 2013 at 7:50 PM, Joe Nosay superbisq...@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.0 +0200
kopete/protocols/jabber/googletalk/libjingle/talk/base/ssladapter.cc
2013-11-04 01:20:20.0 +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,
param) != 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,
param) != 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.
As suggested somewhat by the patch in/for kopete. I tried adding the
function to the file in question. What I did resulted in no change.
-- Configuring done
-- Generating done
-- Build files have been written to:
/usr/home/raspycat/traverso/work/traverso-0.49.2
[ 0%] Building CXX object
src/engine/CMakeFiles/traversoaudiobackend.dir/AudioDeviceThread.o
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDeviceThread.cpp:65:30:
error: use of undeclared identifier 'pthread_self'
[I see this as a solution to that :
http://stackoverflow.com/questions/11488361/lldb-error-use-of-undeclared-identifierbut
how do I implement it as an applied patch ?]
if (pthread_setschedparam (pthread_self(), SCHED_FIFO,
param) != 0) {}
[This was set in kopete and comes up in AudioDeviceThread.cpp as
#ifdef POSIX
extern C{
#include /usr/include/pthread.h
#include /usr/include/unistd.h
}
#endif]
^
/usr/home/raspycat/traverso/work/traverso-0.49.2/src/engine/AudioDeviceThread.cpp:138:30:
error: use of undeclared identifier 'pthread_self'
if (pthread_setschedparam (pthread_self(), SCHED_FIFO,
param) != 0) {
http://clang.debian.net/logs/2011-09-11/traverso_0.49.2-4_lsid64c.buildlog
The log shows that the CLang errors also occurs on other operating
Requirements for ports with 'LEGAL' concerns
If your port falls into any of the following categories - defines RESTRICTED - defines NO_CDROM - defines NO_PACKAGE - has a very restrictive license (not OSI approved) - has special licensing just for FreeBSD - has issues with patents - any other concern which is not currently covered by our LICENSE framework please make sure of the following things (a) the origin listed in LEGAL matches the port origin *exactly* - there should be no wildcards. Please duplicate listings if required. (b) the output of 'make -VLEGAL' matches the third column of LEGAL *exactly* If you have any questions please feel to email ports@ and cc me. -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
pkg audit -F segfault
Hi,
I've just installed pkg-1.2.3 on FreeBSD 8.4-RELEASE-p6.
Running the command pkg audit -F causes a segfault:
# pkg audit -F
Vulnxml file up-to-date.
Segmentation fault (core dumped)
#
Implementing the following patch solves the issue:
--- audit_orig.c 2013-12-11 03:36:21.390625000 +0100
+++ audit.c 2013-12-11 03:36:59.796875000 +0100
@@ -206,9 +206,10 @@
cleanup:
unlink(tmp);
- if (a != NULL)
+ if (a != NULL) {
archive_read_close(a);
archive_read_free(a);
+ }
if (fd = 0)
close(fd);
Thanks in advance for your help.
Phil
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
