Re: Problem(s) with plasma 5.25
I had a similar issue with 5.24.5... I think somewhere between 5.24.3 and 5.25.5 and frameworks 5.93 and 5.94. My solution was I used ALT+F2 and opened the settings. Then I selected 'restore previous desktop session' (I think it was called), applied it, and then 'start a new desktop session' from startup and shutdown. I logged out and logged back in and it seemed fix the problem. That fix doesn't seem to work for 5.25. So I might try to install 5.25 and force install it again to see if that might fix it. On Tue, Jun 21, 2022, 16:31 Adriaan de Groot wrote: > On Tuesday, 21 June 2022 22:55:52 CEST Jeremy wrote: > > The issue is, when I try and start plasma from SDDM or even by using > startx > > from an .xinitrc file with 'exec ck-launch-session startplasma-x11', it > > will show the splash screen, and then a blank screen with the mouse > cursor, > > and then no further activity (no panel on the bottom, no menu to the > left, > > no icons, nothing). > > FWIW, I had this recently -- for a week or so -- with Plasma 5.24.5 (from > ports, though built locally with poudriere) and finally fixed it by force- > upgrading the plasma5\* ports from my poudriere build. I suspect some > underlying library has updated, but not all consumers have had versions > bumped). > > After a forced reinstall of plasma from my local builds, the regular > desktop > came back. > > [ade] (who is messing with qt6 and ignoring newer plasma for now) >
Problem(s) with plasma 5.25
I recently cloned the git repo for plasma 5.25 to test it out. I've been using KDE for years on FreeBSD (since the KDE4) days. I'm running FreeBSD 13.1 stable on an AMD64 computer and I use poudriere to build the apps using x11/plasma5-plasma. The issue is, when I try and start plasma from SDDM or even by using startx from an .xinitrc file with 'exec ck-launch-session startplasma-x11', it will show the splash screen, and then a blank screen with the mouse cursor, and then no further activity (no panel on the bottom, no menu to the left, no icons, nothing). I am able to ALT+F2 and open the run box at the top of the screen and issue the command 'plasmashell --replace', in which the desktop pops up with all of my icons and the panel at the bottom of the screen, the menu and everything works. At this point, I am unsure of what to look for next. There's also an issue with the logout from the menu or from ALT+F2 that crashes the plasma_shell with an abort trap, but that is a separate issue. I've tried clearing out the cache and configure files for Plasma from my user account, as well as creating a new user account. It does the same thing for the new user account as well. I'm using FreeBSD 13.1 stable stable/13-n251449-b8ab9651b1e All of the packages were created through poudriere, and were cloned from the plasma5.25 branch from freebsd-ports-kde repo. I'm using an AMD 4600g (renoir AMD APU) and am having no other issues with Xorg. Infact, when I do 'plasmashell --replace' everything runs just fine. I've saved my xorg-session logs created thru the SDDM folder, but I don't know what to look for, and I'm not seeing big differences between the 5.24 logs and the 5.25 logs. Thanks for all your help. Regards, Jeremy Cox
devel/kio-extras fails to package with SAMBA option disabled
As from the above subject line, devel/kio-extras-22.04.0 fails to package with SAMBA option disabled. Below is a quick plist fix... --- pkg-plist.orig 2022-04-21 13:18:09.452934000 -0500 +++ pkg-plist 2022-04-22 20:52:17.38760 -0500 @@ -48,7 +48,7 @@ share/kio_info/kde-info2html share/kio_info/kde-info2html.conf share/konqueror/dirtree/remote/mtp-network.desktop -share/konqueror/dirtree/remote/smb-network.desktop +%%SAMBA%%share/konqueror/dirtree/remote/smb-network.desktop share/kservices5/directorythumbnail.desktop share/kservicetypes5/thumbcreator.desktop share/locale/ar/LC_MESSAGES/kfileaudiopreview5.mo @@ -809,7 +809,7 @@ share/locale/zh_TW/LC_MESSAGES/kio5_sftp.mo share/locale/zh_TW/LC_MESSAGES/kio5_smb.mo share/locale/zh_TW/LC_MESSAGES/kio5_thumbnail.mo -share/mime/packages/org.kde.kio.smb.xml +%%SAMBA%%share/mime/packages/org.kde.kio.smb.xml share/qlogging-categories5/kio-extras.categories share/qlogging-categories5/kio-extras.renamecategories %%MTP%%share/remoteview/mtp-network.desktop
Re: Missing time in panel
I don't have a file or folder named /var/db/localtime. I do have a file called zoneinfo in /var/db. It's an ASCII text file with the current time zone in it. To answer your second question I did tzsetup and changed my timezone from Chicago to Center, North Dakota since it's a 3 level zone name (America/North_Dakota/Center). There were no issues and the settings page picked up the new time zone with no issues. On Wed, Jun 24, 2020, 03:29 Adriaan de Groot wrote: > On Monday, 22 June 2020 18:38:57 CEST Jeremy wrote: > > And voila! You guys saved me about two days of chasing my tail. Creating > > the symbolic link for /etc/localtime to the Chicago time zone in > > /use/share/zoneinfo fixed the issue. Now the time and date are properly > > displayed on the panel and in the sddm greeter. > > > > Jeremy, the code in Qt is *supposed* to fall back as follows: > > - if /etc/localtime is a symlink, read the link iteself, extract name > - if it isn't, read contents of /var/db/localtime for the name > - otherwise, UTC or blank or something > > Can you take a look at your /var/db/localtime? What's in it? > > [ade] > > PS. That said, I do wonder how this code does in the face of 3-level zone > names, like America/Indiana/Winamac
Re: Missing time in panel
And voila! You guys saved me about two days of chasing my tail. Creating the symbolic link for /etc/localtime to the Chicago time zone in /use/share/zoneinfo fixed the issue. Now the time and date are properly displayed on the panel and in the sddm greeter. Thanks for your help, Jeremy Cox On Mon, Jun 22, 2020, 09:05 Adriaan de Groot wrote: > On Monday, 22 June 2020 12:14:51 CEST Jeremy wrote: > > My /etc/localtime file is a binary file. It isn't a symbolic link to the > > timezone file. > > That's actually a really important bit, there: try moving it aside for a > moment, making it a symlink, and then giving it a try. I thought I had > re-done > the patches handling that case for FreeBSD, and landed them in 5.15. > > [ade] >
Re: Missing time in panel
My /etc/localtime file is a binary file. It isn't a symbolic link to the timezone file. So I'm going to try and revert qt 5.15 and rebuild my repo up to the plasma 5.19.1 update and verify the time displays properly in the panel. If it does then I'll update my repo up to the frameworks 5.71.0 update and see what happens. Maybe it's one of those updates. After that I may just delete the qml cache and my desktop config file. Reconfiguring isn't a big deal. It takes all of a couple of minutes. On Mon, Jun 22, 2020, 04:55 Tobias C. Berner wrote: > Is it a symlink or a real file? > > If I recall correctly, Qt assumes that this is a symlink that points > to the timezone file you want. > > e.g. > > file /etc/localtime > /etc/localtime: symbolic link to /usr/share/zoneinfo/Europe/Zurich > > > > mfg Tobias > > On Mon, 22 Jun 2020 at 11:45, Jeremy wrote: > > > > It says: > > > > localtime: timezone data, version 2, 6 gmt time flags, 6 std time flags, > no leap seconds, 235 transition times, 6 abbreviation chars > > > > On Mon, Jun 22, 2020, 04:39 Tobias C. Berner > wrote: > >> > >> Just a hunch... whats > >> > >> > file /etc/localtime > >> > >> on your system? > >> > >> > >> mfg Tobias > >> > >> On Mon, 22 Jun 2020 at 11:32, Jeremy wrote: > >> > > >> > Plasma 5 does know what the time and date are. When I try to > configure the time and date from the settings page it is correct. It just > doesn't display at all in the panel. Incidentally, trying to add a digital > clock widget directly to the desktop doesn't work either. And the binary > clock widget doesn't work either. I just noticed that the sddm greeter > doesn't display the time or date as well. > >> > > >> > So I'm going to revert the qt 5.15 update and try rebuilding my ports > repo up to the plasma 5.19.1 update and then up to the frameworks 5.71.0 > update and see if either of those are the issue, though I doubt the plasma > 5 point release is the problem. > >> > > >> > On Mon, Jun 22, 2020, 03:29 Tobias C. Berner > wrote: > >> >> > >> >> Moin moin > >> >> > >> >> Interesting -- I have been using that branch for quite some time now, > >> >> and have not noticed this. > >> >> > >> >> > >> >> mfg Tobias > >> >> > >> >> On Sun, 21 Jun 2020 at 21:20, Jeremy wrote: > >> >> > > >> >> > I decided to clone the freebsd-ports-kde qt5-5.15.0 branch and > rebuild plasma5 based on qt5.15, instead of waiting for the exp-run to > complete. > >> >> > > >> >> > The qt5 ports and plasma5 ports rebuilt successfully and are > running well. However, the digital clock on the lower right hand corner of > the panel is missing. I don't see an option to add it. I tried adding a > digital clock widget to the panel and it doesn't display either. > >> >> > > >> >> > And when I click the space where the digital clock should appear, > the calendar pops up. It displays the current month as January and below > that is a comma and the number zero where I believe a holiday event might > appear(?) I don't remember. In the boxes where the numbered days should be, > the numbers start with negative five and increase numerically by one as in > a normal calendar and end in 36. > >> >> > > >> >> > I wanted to see if anyone else has experienced these issues before > I try a drastic step like clearing out all of the configuration and qml > cache files. > >> >> > > >> >> > Thank you guys for all of your hard work keeping plasma5 current > and updated regularly. > >> >> > > >> >> > Regards, > >> >> > Jeremy Cox >
Re: Missing time in panel
I forgot to add that this is 12 stable (r362388) on amd64. The git branch I used for qt5-5.15.0 is identical to the one from freebsd-ports-kde. The qt5-5.15.0 branch on freebsd-ports-kde is on revision 20fe16b.
Missing time in panel
I decided to clone the freebsd-ports-kde qt5-5.15.0 branch and rebuild plasma5 based on qt5.15, instead of waiting for the exp-run to complete. The qt5 ports and plasma5 ports rebuilt successfully and are running well. However, the digital clock on the lower right hand corner of the panel is missing. I don't see an option to add it. I tried adding a digital clock widget to the panel and it doesn't display either. And when I click the space where the digital clock should appear, the calendar pops up. It displays the current month as January and below that is a comma and the number zero where I believe a holiday event might appear(?) I don't remember. In the boxes where the numbered days should be, the numbers start with negative five and increase numerically by one as in a normal calendar and end in 36. I wanted to see if anyone else has experienced these issues before I try a drastic step like clearing out all of the configuration and qml cache files. Thank you guys for all of your hard work keeping plasma5 current and updated regularly. Regards, Jeremy Cox
Report issue similar to BUG 234132
After trying to update the Intel video driver to 20181203: > As of Dec 24 11:55:52 pkg[18901]: xf86-video-intel upgraded: > 2.99.917.20180906 -> 2.99.917.20181203 the problem is resolved. > The issue is not resolved for me yet. I continue to have screen flickering and rendering issues. However, by switching over to the modesetting driver, the issue doesn't occur for me anymore.
Re:Report issue similar to or same as BUG 234132
After reading the bug report again more carefully, I went back and reinstalled the originally updated ports from my poudriere repo with KF5 5.53, QT5 5.12 Plasma 5.12 xserver 1.20.3 and mesa 18.3.1, and disabled the integrated Intel HD 4600 graphics and switched back to my discrete nvidia card. While using the x11/nvidia-driver, KDE is working normally again with no issues with flickering or rendering.
Report issue similar to or same as BUG 234132
I would like to report an issue similar to BUG 234132. I was running FreeBSD stable 12 build r341835. My install included xserver 1.20 and mesa 18.3.1, with the drm-kmod for FreeBSD 12 (based on Linux KPI 4.16), using Haswell HD 4600 integrated video. I am also using the Intel driver, not modesetting. I was using Plasma 5.12.7, KF5 5.52 and QT5 5.11. Everything in Plasma was working fine, all of the KDE apps ran correctly and I had no issues. When I upgraded to KF5 5.53 and QT5 5.12, I ran into very similar issues to what was reported from BUG 234132. There were rendering and screen flickering issues. My KDE desktop was virtually unusable from those issues. So first I uninstalled and reinstalled all of my apps from my poudriere repo and cleared the .cache folders in my accounts that I log into. The issue remained. I then downgraded my versions of xserver back to 1.18 and mesa back to 18.1.9 (essentially using the current ports tree) with a clean repo from poudriere. With Plasma versions 5.12.7, KF5 5.53 and QT5 5.12, the issues remained unchanged. I then reverted the updates for QT5 5.12 and KF5 5.53 back to QT5 5.11 and KF5 5.52, and cleaned out the .cache folders again, and rebuilt with a clean poudriere repo and the issue is gone. So I am essentially using the ports tree from right before the QT5 5.12 and KF5 5.53 commits were made. Everything is running normally and all of the KDE programs are running fine. I'm sorry for the lengthily post. I hope this can shed a little more light on the issue.
Re: x11/plasma5-plasma-desktop fails to build
That is weird. I just rebuilt a bunch of plasma5 stuff again to update all of the kf5 stuff to 5.43.0. x11/plamsa5-plasma-desktop rebuilt fine again (twice now). But you can also look at the suggestion from Kwanza.Pili comment #5 from the kde bug report. https://bugs.kde.org/show_bug.cgi?id=389982 My fix is to comment out the line in kcms/lookandfeel/kcm.cpp that starts > with K_PLUGIN_FACTORY_WITH_JSON. The build is then succeeds. I tried Kwanza.Pili's suggestion before I applied Tobias's patch and that also worked for me. I also created a new and clean ports tree and repository with poudriere just for plasma 5.12 building and testing to ensure it would build and work correctly. On Mon, Feb 12, 2018 at 7:51 AM, Stefan Rumetshofer <steru...@gmail.com> wrote: > On my system the build has failed again with the same error as in the > first post :( > > Stefan > > 2018-02-11 19:46 GMT+01:00 Stefan Rumetshofer <steru...@gmail.com>: > >> Hi Tobias, >> >> I have applied the patch. Poudriere is now running. This could take a >> while. >> >> 2018-02-11 11:19 GMT+01:00 Tobias C. Berner <tcber...@freebsd.org>: >> >>> Moin moin, >>> >>> Could you try with this patch applied to the ports tree? >>> http://people.freebsd.org/~tcberner/patches/0001-Add-custom- >>> target-to-kf5-kcoreaddons-desktop2json.patch >>> >>> >>> mfg Tobias >>> >>> On 10 February 2018 at 21:57, Jeremy <jeremy.m@gmail.com> wrote: >>> >>>> I'm afraid I can't get plasma5-plasma-desktop to build either. It fails >>>> with exactly the same error that Stefan Rumetshofer reported. I have tried >>>> to build it several times. I am using poudriere with 12 current. I have >>>> tried to build it using MAKE_JOBS_UNSAFE as well and it still will not >>>> build. A couple of CMake warnings I see from the build log: >>>> >>>> CMake Warning (dev) at >>>> /usr/local/lib/cmake/KF5Package/KF5PackageMacros.cmake:26 >>>> (message): >>>> Deprecated: use kpackage_install_bundled_package >>>> Call Stack (most recent call first): >>>> kcms/lookandfeel/CMakeLists.txt:59 (kpackage_install_package) >>>> This warning is for project developers. Use -Wno-dev to suppress it. >>>> >>>> CMake Warning at /usr/local/lib/cmake/KF5Package/KF5PackageMacros.cmake:73 >>>> (message): >>>> KPackage components should be specified in reverse domain notation. >>>> Appstream information won't be generated for kcm_lookandfeel. >>>> Call Stack (most recent call first): >>>> kcms/lookandfeel/CMakeLists.txt:59 (kpackage_install_package) >>>> >>>> I am scratching my head on this one. >>>> >>>> Thanks for your help in advance, >>>> Jeremy Cox >>>> >>> >>> >> >
Re: x11/plasma5-plasma-desktop fails to build
Thanks for the patch! I applied it and rebuilt those ports with poudriere with no issues this time. Plasma 5.12 is working well. Thanks guys for all your hard work keeping KDE updated and working on FreeBSD. Regards, Jeremy Cox On Feb 11, 2018 12:46, "Stefan Rumetshofer" <steru...@gmail.com> wrote: Hi Tobias, I have applied the patch. Poudriere is now running. This could take a while. 2018-02-11 11:19 GMT+01:00 Tobias C. Berner <tcber...@freebsd.org>: > Moin moin, > > Could you try with this patch applied to the ports tree? > http://people.freebsd.org/~tcberner/patches/0001-Add-custom- > target-to-kf5-kcoreaddons-desktop2json.patch > > > mfg Tobias > > On 10 February 2018 at 21:57, Jeremy <jeremy.m@gmail.com> wrote: > >> I'm afraid I can't get plasma5-plasma-desktop to build either. It fails >> with exactly the same error that Stefan Rumetshofer reported. I have tried >> to build it several times. I am using poudriere with 12 current. I have >> tried to build it using MAKE_JOBS_UNSAFE as well and it still will not >> build. A couple of CMake warnings I see from the build log: >> >> CMake Warning (dev) at >> /usr/local/lib/cmake/KF5Package/KF5PackageMacros.cmake:26 >> (message): >> Deprecated: use kpackage_install_bundled_package >> Call Stack (most recent call first): >> kcms/lookandfeel/CMakeLists.txt:59 (kpackage_install_package) >> This warning is for project developers. Use -Wno-dev to suppress it. >> >> CMake Warning at /usr/local/lib/cmake/KF5Package/KF5PackageMacros.cmake:73 >> (message): >> KPackage components should be specified in reverse domain notation. >> Appstream information won't be generated for kcm_lookandfeel. >> Call Stack (most recent call first): >> kcms/lookandfeel/CMakeLists.txt:59 (kpackage_install_package) >> >> I am scratching my head on this one. >> >> Thanks for your help in advance, >> Jeremy Cox >> > >
Re:x11/plasma5-plasma-desktop fails to build
I'm afraid I can't get plasma5-plasma-desktop to build either. It fails with exactly the same error that Stefan Rumetshofer reported. I have tried to build it several times. I am using poudriere with 12 current. I have tried to build it using MAKE_JOBS_UNSAFE as well and it still will not build. A couple of CMake warnings I see from the build log: CMake Warning (dev) at /usr/local/lib/cmake/KF5Package/KF5PackageMacros.cmake:26 (message): Deprecated: use kpackage_install_bundled_package Call Stack (most recent call first): kcms/lookandfeel/CMakeLists.txt:59 (kpackage_install_package) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning at /usr/local/lib/cmake/KF5Package/KF5PackageMacros.cmake:73 (message): KPackage components should be specified in reverse domain notation. Appstream information won't be generated for kcm_lookandfeel. Call Stack (most recent call first): kcms/lookandfeel/CMakeLists.txt:59 (kpackage_install_package) I am scratching my head on this one. Thanks for your help in advance, Jeremy Cox
Please modify x11/plasma5-plasma-integration Makefile from plasma5 branch
x11-fonts/hack-font has been updated to version 3 and no longer supplies .otf fonts but does supply .ttf fonts. Please modify the x11/plasma5-plasma-integration Makefile from the plasma5 branch to reflect that change so poudriere doesn't report a run-depends build failure while building plasma5-plasma-integration. It is the second line under RUN_DEPENDS... Hack-Regular.otf Thank you guys very much for your hard work on this mammoth project! Regards, Jeremy Cox
Re:Bug in systemsettings5
Thanks for the fix for that issue. I was wondering if it was an issue on my side in compiling the port. Thanks for all your hard work! Regards, Jeremy Cox
Please remove qt5-declarative from devel/kdevelop Makefile
I noticed in the plasma5 branch of the github repo for freebsd-ports-kde that the Makefile for devel/kdevelop still refers to the now expired qt5-declarative port in the first line of USE_QT5=. I'm not trying to build kdevelop, but it does stop "make index" from completing. But other than that hiccup, Plasma 5 is quite enjoyable on FreeBSD. Thank you all for your hard work. Sincerely, Jeremy Cox
Is there a difference between kde5 and plasma5?
Hello all, I must say thank you for your continued efforts to port the newest version of KDE to FreeBSD. I'm so excited because I got it working. I used the x11/kde5 metaport. According to the instructions, it says to use x11/plasma5-plasma. Is there a difference between which ports will be built between using plasma5-plasma or the kde5 metaport? It is working pretty well, and x11/sddm was also successfully built and is functioning well. I'm using kde5 with xorg server 1.18.4 and Nvidia. Thank you all again for your hard work! Regards Jeremy Cox
[kde-freebsd] Question about KDE4's prefix when KDE3 deleted.
I am wondering if KDE4's prefix (${LOCALBASE}/kde4) will be changed
when you delete the KDE3? I am a big fan of hier(7), so wondering
about it.
BTW: Please add me in CC as I ain't in this list.
--
mezz.free...@gmail.com - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] How to remove erroneous deps from pkgng
On Sat, Jul 21, 2012 at 11:56 PM, Doug Barton do...@freebsd.org wrote: KDE folks Jason's suggestion (by private e-mail for some reason) was that we add pkgconfig to USE_GNOME= for every port that depends on kdelibs that doesn't already have it; since almost, if not actually all of them are currently relying on the run-dep side effect. I can't see any reason NOT to do this, but if you have an objection please speak up sooner rather than later. On 07/21/2012 21:33, Jeremy Messenger wrote: On Sat, Jul 21, 2012 at 4:04 PM, Doug Barton do...@freebsd.org wrote: On 07/21/2012 13:48, Jason E. Hale wrote: IMO I don't really see what the hurry is. This has been the behavior for years. Yes, and some of us have been annoyed by it for years as well. :) The current behavior is wrong, and becomes increasingly painful in a world where most FreeBSD users are using packages because it drags in a totally pointless package to essentially every FreeBSD system. Fixing this bug is a good thing, and needs to be done sooner rather than later. snip It is unnecessary to be in hurry when that pkg-config has been in the bsd.gnome.mk for about nine years. The sooner we start fixing it, the better off we are. I already have a better solution available for weeks. Therefore, you (and others) need to be patient because when I add the :build/:run dependency in the bsd.gnome.mk then that pkg-config runtime dependency will be re-added. Um, yeah ... don't do that. You need to start to respect the people's work and plan, Doug. Also I am part of team that maintaining the bsd.gnome.mk. Yes it will be re-add if anyone plan to remove it, because I already have planned add the :build/:run feature in the bsd.gnome.mk that the without :* will be both build/run time dependency. It is impossible for me to not re-add it. It is not going to be long because I already have function :build/:run in the bsd.mate.mk (was repocopied from bsd.gnome.mk) available. The only thing that I don't plan is to chase thousands of port to have the 'pkgconfig;build'. If anyone want to take up this task is cool with me. I mis-attributed your patch to Jason previously, sorry about that. But before it goes in your patch should have the logic I spoke about in my previous posts, to make sure that the USE_GNOME bits cannot get added as the wrong kinds of deps. And no I am not going to work on chase all ports to have the 'pkgconfig:build' (sorry). Not asking you to. I'm asking you to fix your patch so that things that should only be one kind of dep or the other (like pkgconfig, but not necessarily limited to it) are handled properly by default if the right :label is not attached, and error out if the wrong one is. That way the work that's being done now to fix ports that need explicit build deps for pkg-config will solve this part of the problem for you. As you pointed out, the current situation has existed for a long time already. If we have to wait another week or 2 for the pkg-config run dep problem to be fixed properly before your patch gets committed, that's not really a problem. Doug -- Change is hard. -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] How to remove erroneous deps from pkgng
On Sun, Jul 22, 2012 at 6:22 PM, Max Brazhnikov m...@freebsd.org wrote: On Sun, 22 Jul 2012 09:51:40 -0500 Jeremy Messenger wrote: You need to start to respect the people's work and plan, Doug. Also I am part of team that maintaining the bsd.gnome.mk. Yes it will be re-add if anyone plan to remove it, because I already have planned add the :build/:run feature in the bsd.gnome.mk that the without :* will be both build/run time dependency. in kde4.mk we support not only run/build suffixes, but also have default dependence type if suffix is not set. The only thing that I don't plan is to chase thousands of port to have the 'pkgconfig;build'. If anyone want to take up this task is cool with me. Why should we change lots of ports and always keep eyes on new ports, if it can be altered once in .mk ?? Because it's not a right solution. There are very few need pkg-config in the runtime dependency. Also I already have designed feature that way (it's not for pkg-config, but all stuff in the bsd.gnome.mk) and it doesn't break anything by defaut. But don't worry because bapt, kwm and I have discussed about add USE_PKGCONFIG in the bsd.port.mk and rip pkg-config out of bsd.gnome.mk. It's even better, but I know it's more work like USE_GNOME=pkgconfig:build. Cheers, Mezz Max -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] How to remove erroneous deps from pkgng
On Sun, Jul 22, 2012 at 4:16 PM, Doug Barton do...@freebsd.org wrote: On 07/22/2012 07:51, Jeremy Messenger wrote: You need to start to respect the people's work and plan, Doug. Also I am part of team that maintaining the bsd.gnome.mk. Yes it will be re-add if anyone plan to remove it, because I already have planned add the :build/:run feature in the bsd.gnome.mk that the without :* will be both build/run time dependency. It is impossible for me to not re-add it. It is not going to be long because I already have function :build/:run in the bsd.mate.mk (was repocopied from bsd.gnome.mk) available. The only thing that I don't plan is to chase thousands of port to have the 'pkgconfig;build'. If anyone want to take up this task is cool with me. So what you're saying is that in spite of the fact that the community has identified a bug that it wants to fix, a bug which was added by the team maintaining bsd.gnome.mk, that you are refusing to modify your patch to handle the bug; but instead are demanding your right to reintroduce the bug, and then further demanding the right to not fix it after the patch is in? Remove the runtime dependency is a bug either because there are a few that need it in the runtime dependency. I have written a best solution than remove that runtime line. It will be 99% bug free when all ports have the right :build/:run. And furthermore, you're refusing to even look at the other dependencies which are handled by bsd.gnome.mk to see if similar bugs were introduced *by your team*, but you're happy to let everyone else sort out the problems in thousands of ports for you. Quiet simple, I do not have time for that huge project. I already have added :build/:run feature before anyone complain about the pkg-config dependency. The feature happened to address this issue and fix all pkg-config dependency was not part of my TODO list. My method does not break before or after patch any port, but still have the wrong dependency which it's minor and can be fixed by edit to pkgconfig:build. And you want me to respect that? -- Change is hard. -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] Re: Building KDE on PowrPC
On Tue, Mar 15, 2011 at 11:42 PM, Super Bisquit superbisq...@gmail.com wrote: Okay kde4 breaks at /usr/ports/devel/py-gobject with configure missing gobject introspection. Gobject-introspection 0.10.4 (I am also building gnome3) stops at asking for the file to patch. This is affecting both desktop suites. Please post the error log that way I don't have to throw a wild guess. Cheers, Mezz On Mon, Mar 14, 2011 at 9:22 PM, Super Bisquit superbisq...@gmail.com wrote: It just stopped at security/gnupg(2). I had to cd to work/gnupg* ad do ./configure then make. After it is finished, cd to x11/kde4 and make. Okay, gpg2 fails at work/gpg*/keyserver/gpgkeys_hkp.c:385 undefined reference to 'xfree.' I went back and enabled gpg1 from gpgme options. On 3/14/11, Alberto Villa avi...@freebsd.org wrote: On Sunday 13 March 2011 17:46:54 Super Bisquit wrote: I'm doing a new build of kde4 on a Quicksilver 2002 G4. All is set for default configurations. Whatever won't build, I'll report hello! sorry for being so late. so, you started a build outside tinderbox, right? good! if you still need help to setup a tinderbox i'll be happy to help, but i think we don't need both a build outside and inside tinderbox, so just choose your preferred method :) -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla I couldn't possibly fail to disagree with you less. -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] cvs commit: ports/Mk bsd.qt.mk ports/accessibility/qt4-accessible Makefile pkg-descr pkg-plist ports/chinese/qt4-codecs-cn Makefile pkg-descr pkg-plist ports/chinese/qt4-codecs-tw Ma
On 2010-Jan-21 21:13:21 +, Max Brazhnikov m...@freebsd.org wrote: The FreeBSD KDE team is pleased to announce Qt-4.6.1 for FreeBSD. Should there be something in /usr/ports/UPDATING? Also, it blows up for me in textproc/qt4-xml on amd64/8-stable: server% cd /usr/ports/textproc/qt4-xml make clean make configure === Cleaning for qt4-xml-4.6.1 === Extracting for qt4-xml-4.6.1 = MD5 Checksum OK for KDE/qt-everywhere-opensource-src-4.6.1.tar.gz. = SHA256 Checksum OK for KDE/qt-everywhere-opensource-src-4.6.1.tar.gz. === Patching for qt4-xml-4.6.1 === Applying extra patch /usr/ports/textproc/qt4-xml/../../devel/qt4/files/patch-configure === qt4-xml-4.6.1 depends on file: /usr/local/lib/qt4/libQtCore.so - found === qt4-xml-4.6.1 depends on file: /usr/local/bin/moc-qt4 - found === qt4-xml-4.6.1 depends on file: /usr/local/bin/qmake-qt4 - found === Configuring for qt4-xml-4.6.1 /bin/mkdir -p /usr/ports/work/usr/ports/textproc/qt4-xml/work/qt-everywhere-opensource-src-4.6.1/mkspecs ... Qt is now configured for building. Just run 'make'. Once everything is built, you must run 'make install'. Qt will be installed into /usr/local To reconfigure, run 'make confclean' and 'configure'. /usr/bin/sed -i.bak -e 's|/usr/local/lib/qt4/pkgconfig|/usr/local/libdata/pkgconfig|g' -e 's|.*$(QMAKE).*||g' /usr/ports/work/usr/ports/textproc/qt4-xml/work/qt-everywhere-opensource-src-4.6.1/src/xml/Makefile /usr/bin/sed -i.bak -E -e 's|-L.[^[:space:]]*qt-x11-opensource.[^[:space:]]*lib||g' -E -e 's|(.*location=).*moc|\1/usr/local/bin/moc-qt4|g' -E -e 's|(.*location=).*uic|\1/usr/local/bin/uic-qt4|g' /usr/ports/work/usr/ports/textproc/qt4-xml/work/qt-everywhere-opensource-src-4.6.1/lib/pkgconfig/QtXml.pc /usr/bin/patch -d /usr/ports/work/usr/ports/textproc/qt4-xml/work/qt-everywhere-opensource-src-4.6.1 /usr/ports/work/usr/ports/textproc/qt4-xml/work/extrapatch-src-xml-Makefile Hmm... Looks like a unified diff to me... The text leading up to this was: -- |--- src/xml/Makefile.orig 2009-12-04 16:04:02.944271152 +1000 |+++ src/xml/Makefile 2009-12-04 16:07:07.986728782 +1000 -- Patching file src/xml/Makefile using Plan A... Hunk #1 failed at 533. 1 out of 1 hunks failed--saving rejects to src/xml/Makefile.rej done *** Error code 1 [Full log on request] -- Peter Jeremy pgpRkFSuAWxcE.pgp Description: PGP signature ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] cvs commit: ports/Mk bsd.qt.mk ports/accessibility/qt4-accessible Makefile pkg-descr pkg-plist ports/chinese/qt4-codecs-cn Makefile pkg-descr pkg-plist ports/chinese/qt4-codecs-tw Ma
On 2010-Jan-24 17:12:30 +0300, Max Brazhnikov m...@issp.ac.ru wrote:
On Sun, 24 Jan 2010 19:08:21 +1100, Peter Jeremy wrote:
On 2010-Jan-21 21:13:21 +, Max Brazhnikov m...@freebsd.org wrote:
The FreeBSD KDE team is pleased to announce Qt-4.6.1 for FreeBSD.
Should there be something in /usr/ports/UPDATING?
It's a regular update, there's nothing interesting for UPDATING :)
OK. I wasn't sure.
Also, it blows up for me in textproc/qt4-xml on amd64/8-stable:
Working on this. Do you have non-default QMAKESPEC?
No. And, as far as I can tell, I didn't have any Qt stuff installed
prior to yesterday (definitely all the direct dependencies are newly
built).
I've found the immediate reason why the patch fails: The
install_flat_headers target in ${WRKSRC}/src/xml/Makefile
refers to $(INSTALL_FILE) whilst
textproc/qt4-xml/files/extrapatch-src-xml-Makefile refers
to $(INSTALL_PROGRAM) - the former looks more correct.
I notice you have resolved the problem in a cleaner way. This
fixes the build problem for me, thanks.
--
Peter Jeremy
pgpk9SSQvZObK.pgp
Description: PGP signature
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] Co-ordination of some efforts on oscaf
On Fri, 27 Nov 2009 12:50:53 -0600, Joe Marcus Clarke mar...@marcuscom.com wrote: On Fri, 2009-11-27 at 12:23 -0500, Thomas Abthorpe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rumour has it that oscaf, http://oscaf.sourceforge.net, has released 0.1 and that future releases of KDE and Gnome will require it. Does anybody have this on their radar, so we can avoid a duplication of effort? This is the first I'm hearing of this, so, no, I don't have it on my radar. Me either and I don't know what oscaf (will check later when we actually need it) is. Cheers, Mezz My next project is porting DevKit-power to FreeBSD. Joe -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/139884: audio/akode: fix dependency on libltdl
The following reply was made to PR ports/139884; it has been noted by GNATS. From: Jeremy Messenger me...@cox.net To: bug-follo...@freebsd.org, t...@ulyssis.org Cc: Subject: Re: ports/139884: audio/akode: fix dependency on libltdl Date: Sat, 24 Oct 2009 10:56:52 -0500 Before anyone commit this patch. Make sure to add ':22' in the libltdl, ie: -USE_AUTOTOOLS= libltdl -USE_AUTOTOOLS= libtool:22 +USE_AUTOTOOLS= libtool:22 libltdl:22 Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/135860: [PATCH] x11/kdebase3: Unbreak on -CURRENT
The following reply was made to PR ports/135860; it has been noted by GNATS. From: Jeremy Messenger me...@cox.net To: Daniel M. Eischen eisc...@vigrid.com Cc: bug-follo...@freebsd.org Subject: Re: ports/135860: [PATCH] x11/kdebase3: Unbreak on -CURRENT Date: Sun, 05 Jul 2009 14:47:29 -0500 On Sun, 05 Jul 2009 11:09:04 -0500, Daniel M. Eischen eisc...@vigrid.com wrote: I'm not sure why you disabled usb_revision.h. It will not build on -current without including this. How old -CURRENT do you have? Have you ran 'make delete-old' when you update -CURRENT? It does not exist in today -CURRENT, see here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/Attic/usb_revision.h (attic, removed) http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ (no usb_revision.h) kde3 has been borken on -current for a while now. Can we please get this incorporated? Use my patch works great. Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/135860: [PATCH] x11/kdebase3: Unbreak on -CURRENT
The following reply was made to PR ports/135860; it has been noted by GNATS. From: Jeremy Messenger me...@cox.net To: Daniel Eischen deisc...@freebsd.org Cc: bug-follo...@freebsd.org Subject: Re: ports/135860: [PATCH] x11/kdebase3: Unbreak on -CURRENT Date: Sun, 05 Jul 2009 21:26:45 -0500 On Sun, 05 Jul 2009 20:01:59 -0500, Daniel Eischen deisc...@freebsd.org wrote: On Sun, 5 Jul 2009, Jeremy Messenger wrote: On Sun, 05 Jul 2009 11:09:04 -0500, Daniel M. Eischen eisc...@vigrid.com wrote: I'm not sure why you disabled usb_revision.h. It will not build on -current without including this. How old -CURRENT do you have? Have you ran 'make delete-old' when you update -CURRENT? It does not exist in today -CURRENT, see here: My -current was a fresh install from June 2009 8.0 snapshot on amd64. I updated to -current sources from July 1, 2009, or thereabouts. I did not run 'make delete-old'. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/Attic/usb_revision.h (attic, removed) http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ (no usb_revision.h) kde3 has been borken on -current for a while now. Can we please get this incorporated? Use my patch works great. I am rebuilding to see if works now. I'm not sure where those defines are going to come from though. They don't appear to be anywhere else. Are you going to commit this? No. I am not a KDE user and maintainer. :-) When I tested stuff with USB devices, I have no idea which it was works from HAL or KDE's USB stuff.. Mostly of stuff look like was from HAL, but I can't say for sure since I have no idea. Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/135860: [PATCH] x11/kdebase3: Unbreak on -CURRENT
The following reply was made to PR ports/135860; it has been noted by GNATS. From: Jeremy Messenger me...@cox.net To: bug-follo...@freebsd.org, u...@spoerlein.net Cc: Subject: Re: ports/135860: [PATCH] x11/kdebase3: Unbreak on -CURRENT Date: Thu, 02 Jul 2009 10:26:27 -0500 Your extrapatch-libusb20 does not apply clean. You didn't test the 'make patch' before you submit it. The fix is pretty very simple by correct the path of like this: --- usbdevices.h.orig 2006-07-22 10:15:22.0 +0200 +++ usbdevices.h 2009-06-20 13:19:42.0 +0200 It should be: --- kcontrol/usbview/usbdevices.h.orig 2006-07-22 10:15:22.0 +0200 +++ kcontrol/usbview/usbdevices.h 2009-06-20 13:19:42.0 +0200 But I also update the patch to make work with -CURRENT again by disable the usb_revision.h. Here is update: http://people.freebsd.org/~mezz/diff/extrapatch-libusb20 Keep in mind, I haven't test it in the runtime but I will later. Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] May I commit your ports to fix the hardcore?
Hello, May I commit your ports to fix the hardcore of ltmain.sh and libtool? Here are the patches: kde@: http://people.freebsd.org/~mezz/diff/kdeutils3.diff anatoly.borodin@: http://people.freebsd.org/~mezz/diff/directfb.diff alecn2002@: http://people.freebsd.org/~mezz/diff/kmymoney2.diff Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] May I commit your ports to fix the hardcore?
On Thu, 02 Jul 2009 14:56:31 -0500, Thomas Abthorpe tabtho...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On July 2, 2009 03:30:46 pm Jeremy Messenger wrote: May I commit your ports to fix the hardcore of ltmain.sh and libtool? Here are the patches: kde@: http://people.freebsd.org/~mezz/diff/kdeutils3.diff KDE hat Hi Jeremey Feel free to commit the patch. /hat - KDE + /KDE Now I can view it in my browser. ;-) Committed! Thank you and miwi too. Cheers, Mezz :) Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpNEPAACgkQ5Gm/jNBp8qCxHQCeIPfcfgQvgWfufaA5mYtodXKB CjEAn3/PjPsis/Gy1kCWRZnNHnxlh2Fs =amc/ -END PGP SIGNATURE- -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/135860: [PATCH] x11/kdebase3: Unbreak on -CURRENT
The following reply was made to PR ports/135860; it has been noted by GNATS. From: Jeremy Messenger me...@cox.net To: bug-follo...@freebsd.org, u...@spoerlein.net Cc: Subject: Re: ports/135860: [PATCH] x11/kdebase3: Unbreak on -CURRENT Date: Thu, 02 Jul 2009 15:25:24 -0500 FYI: I have tested it in runtime by insert a USB flash drive and it appears fine in file browser. Not sure if it uses KDE's usb or HAL. Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] Proper procedure to update hal on -current
On Fri, 17 Apr 2009 11:28:45 -0500, Mel Flynn mel.flynn+fbsd.curr...@mailing.thruhere.net wrote: On Friday 17 April 2009 10:35:39 Mel Flynn wrote: Hi Johannes, On Friday 17 April 2009 09:31:46 Johannes Dieterich wrote: Do I need to temporarily uninstall devel/libusb (it doesn't build now anyway, but maybe upgrading to today's current will fix that) then reinstall it? My procedure was to deinstall devel/libusb, then I also encountered the same kind of mising dependencies as you do but for me a pkgdb -F afterwards would fix them. Then hal would also build for me. :-) Ah, this relies on ldconfig -r finding /usr/lib/libusb and thus not installing devel/libusb. Gotcha. Actually, it don't :( and libusb marked as IGNORE, portmaster complaints and downhill there. Hence the patch below. Whether this patch disables usb features, I don't know. Will have to dig into cmake and find out where it stores what is enabled/disabled. I personal would like to see USE_LIBUSB (or without LIB) add in bsd.port.mk. Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] Call for Help: QT4.5 problems on FreeBSD.
On Sat, 07 Feb 2009 04:53:30 -0600, Martin Wilke m...@freebsd.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy,
I've started work on QT 4.5 RC1 and I'm almost finished,
but I've run into some problemes and I need your help.
QT 4.5 now has gtk20 support which means x11-toolkit/qt4-gui
now depends on gtk20. The build failed with:
http://nopaste.info/16e19abbb9_nl.html
I fixed that with set CLFAGS:
CONFIGURE_ENV?= QTDIR=${WRKSRC} PATH=${WRKSRC}/bin:$$PATH \
CFLAGS=${CFLAGS}
MAKE_ENV?=QTDIR=${WRKSRC} LD_LIBRARY_PATH=${WRKSRC}/lib \
PATH=${WRKSRC}/bin:$$PATH CFLAGS=${CFLAGS}
CFLAGS+= -I${LOCALBASE}/include/gtk-2.0 -I${LOCALBASE}/include/atk-1.0 \
-I${LOCALBASE}/include/cairo -I${LOCALBASE}/include/pango-1.0 \
-I${LOCALBASE}/include/glib-2.0
You should use pkg-config instead of hardcore. You can check in
x11-toolkits/pango for example.
--
GLIB2_CFLAGS= `pkg-config glib-2.0 --cflags`
[...]
CONFIGURE_ENV= CPPFLAGS=-I${LOCALBASE}/include/freetype2 \
${GLIB2_CFLAGS} -I${LOCALBASE}/include \
LDFLAGS=-L${LOCALBASE}/lib
--
You can do same with --libs for below in the 'LIBS +=' part. I am surpised
for QT to not use pkg-config or something to allow QT to get buildable
without have someone to add hack. Maybe, you should report to QT
bugtracker or something. Or maybe there is something missing.
As for the rest other than this, I have no idea for QT problem.
Cheers,
Mezz
Build is now fine but all qt4-gui dependency on ports
fail now with:
http://nopaste.info/efd2d1f63f_nl.html
A dirty workaround is to set:
${ECHO_CMD} LIBS += -lgobject-2.0 ${WRKSRC}/${PORTNAME}.pro
This fixed the build for qt4-* ports that use gui. But
qt4* dependency on ports failed with the same error.
I think the dirty workaround is really bad, what we need here
a good fix. Also I already tested setting -lgobject-2.0
to the CFLAGS from qt4-gui but then all ports failed with
/usr/local/lib/qt4/libQtGui.so: undefined reference to
`QCoreApplicationPrivate::checkReceiverThread(QObject*)
Now, the question is, is this a general problem with QT 4.5
or a ports problem? Could someone please take a look and give
us some help?
You can find the patch here:
http://people.freebsd.org/~miwi/qt4/qt45rc1.diff
Note: Please set 'WANT_QT_DEBUG=YES' to your /etc/make.conf.
Thanks Martin
- --
+---+---+
| PGP: 0x05682353 | Jabber : miwi(at)BSDCrew.de |
| ICQ: 169139903 | Mail : miwi(at)FreeBSD.org |
+---+---+
| Mess with the Best, Die like the Rest! |
+---+---+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)
iEYEARECAAYFAkmNaCkACgkQFwpycAVoI1Pz6gCdHgoxp/H3VL/LgXQ0Kp/8xUa3
on8AoIeogTyqtdHp8Pk8LqWcLKv+Qmjh
=YNue
-END PGP SIGNATURE-
___
freebsd-po...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
--
me...@cox.net - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0!
FYI: These have been committed in FreeBSD ports tree. You now can run 'marcusmerge -U' to unmerge ports-stable and remove it. I will removing everything in ports-stable tonight. Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] portmaster failure
On Thu, 26 Jun 2008 02:35:00 -0500, Rene Ladan [EMAIL PROTECTED] wrote:
Hi,
with both the marcuscom ports-stable and the area51 tree merged into
the ports tree,
I get this failure from 'portmaster -a' :
--8-888--
self# portmaster -a
=== Gathering distinfo list for installed ports
=== Starting check of installed ports for available updates
=== Checking ports for recursive 'make config'
Unknown modifier '9'
/usr/ports/Mk/bsd.gnome.mk, line 657: Malformed conditional
(${_USE_GNOME_ALL:Mltverhack:9}==)
Unknown modifier '9'
Error expanding embedded variable.
=== Is /usr/ports/x11/pixman/Makefile missing?
=== Aborting update
=== The following actions were performed:
--8-888--
All 3 trees were updated this morning.
I think this could become a real problem when the ports-stable tree
gets merged into CVS.
If area51 tree has its own bsd.port.mk (maybe more if there is any) change
then you can't use ports-stable unless area51 merges with ports-stable's
bsd.port.mk change. If you want to stop to use area51 tree and use
ports-stable tree. You have to make sure you always run 'marcusmerge -u -m
ports-stable' at the each time when you update your FreeBSD ports tree by
portsnap, cvsup or whatever.
Cheers,
Mezz
Regards,
Rene
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] A bug in QtCore.pc or qglobal.h?
On Sat, 21 Jun 2008 14:04:08 -0500, Max Brazhnikov [EMAIL PROTECTED] wrote:
On Sat, 21 Jun 2008 11:20:38 -0500, Jeremy Messenger wrote:
Hello folks,
I am wondering if there is a bug in QtCore.pc for not have
-I/usr/local/include or qglobal.h for should be '#include
QtCore/qconfig.h' - '#include qconfig.h'? A simple test.cc failed
to
compile unless I add -I/usr/local/include.
-
# cat test.cc
#include cstdio
#include QtGlobal
extern C int main(void)
{
printf(found version %s, QT_VERSION_STR);
#if QT_VERSION = 0x040200
printf(, OK.\n);
return 0;
printf(, expected version 4.2.0 or higher\n);
return 1;
#endif
}
-
-
# c++ -O -Wall -o test test.cc `pkg-config QtCore --cflags --libs`
In file included from /usr/local/include/QtCore/QtGlobal:1,
from test.cc:2:
/usr/local/include/QtCore/qglobal.h:62:28: error: QtCore/qconfig.h: No
such file or directory
/usr/local/include/QtCore/qglobal.h:942:31: error: QtCore/qfeatures.h:
No
such file or directory
/usr/local/include/QtCore/qglobal.h:1139:4: error: #error Qt not
configured correctly, please run configure
/usr/local/include/QtCore/qglobal.h:2036:6: error: #error Qt not
configured correctly, please run configure
-
The solution is to add -I/usr/local/include.
-
# c++ -O -Wall -o test test.cc `pkg-config QtCore --cflags --libs`
-I/usr/local/include
# ./test
found version 4.3.4, OK.
-
-
# pkg-config QtCore --cflags --libs
-DQT_SHARED -I/usr/local/include/QtCore -pthread -L/usr/local/lib
-lQtCore -lz -lm -lgthread-2.0 -lglib-2.0 -liconv
-
BTW: Please add me in CC.
Cheers,
Mezz
/usr/local/include was removed (incorrectly) from Qt*.pc. The problem is
that
qt3 installs headers (one of them is qconfig.h) to /usr/local/include
and
this sometimes confuses qt4 ports.
I have both qt3 and qt4 installed, and I don't have any problem. I think
it's matter of order. Does qt4 still has problem even if it has
/usr/local/include in the last order? Like this:
-I/usr/local/include/QtCore -I/usr/local/include
I believe that it needs to be fix in *.pc files. The qt3 doesn't has
QtCore, so I think it should be no problem.
Cheers,
Mezz
Max
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] A bug in QtCore.pc or qglobal.h?
On Sun, 22 Jun 2008 03:34:04 -0500, Max Brazhnikov [EMAIL PROTECTED] wrote:
On Sun, 22 Jun 2008 01:18:13 -0500, Jeremy Messenger wrote:
On Sat, 21 Jun 2008 14:04:08 -0500, Max Brazhnikov [EMAIL PROTECTED]
wrote:
On Sat, 21 Jun 2008 11:20:38 -0500, Jeremy Messenger wrote:
Hello folks,
I am wondering if there is a bug in QtCore.pc for not have
-I/usr/local/include or qglobal.h for should be '#include
QtCore/qconfig.h' - '#include qconfig.h'? A simple test.cc
failed
to
compile unless I add -I/usr/local/include.
-
# cat test.cc
#include cstdio
#include QtGlobal
extern C int main(void)
{
printf(found version %s, QT_VERSION_STR);
#if QT_VERSION = 0x040200
printf(, OK.\n);
return 0;
printf(, expected version 4.2.0 or higher\n);
return 1;
#endif
}
-
-
# c++ -O -Wall -o test test.cc `pkg-config QtCore --cflags --libs`
In file included from /usr/local/include/QtCore/QtGlobal:1,
from test.cc:2:
/usr/local/include/QtCore/qglobal.h:62:28: error: QtCore/qconfig.h:
No
such file or directory
/usr/local/include/QtCore/qglobal.h:942:31: error:
QtCore/qfeatures.h:
No
such file or directory
/usr/local/include/QtCore/qglobal.h:1139:4: error: #error Qt not
configured correctly, please run configure
/usr/local/include/QtCore/qglobal.h:2036:6: error: #error Qt not
configured correctly, please run configure
-
The solution is to add -I/usr/local/include.
-
# c++ -O -Wall -o test test.cc `pkg-config QtCore --cflags --libs`
-I/usr/local/include
# ./test
found version 4.3.4, OK.
-
-
# pkg-config QtCore --cflags --libs
-DQT_SHARED -I/usr/local/include/QtCore -pthread -L/usr/local/lib
-lQtCore -lz -lm -lgthread-2.0 -lglib-2.0 -liconv
-
BTW: Please add me in CC.
Cheers,
Mezz
/usr/local/include was removed (incorrectly) from Qt*.pc. The problem
is
that
qt3 installs headers (one of them is qconfig.h) to /usr/local/include
and
this sometimes confuses qt4 ports.
I have both qt3 and qt4 installed, and I don't have any problem. I think
it's matter of order. Does qt4 still has problem even if it has
/usr/local/include in the last order? Like this:
-I/usr/local/include/QtCore -I/usr/local/include
This might break some qt4-dependent ports, if their include path will be
like
-I/usr/local/include/QtCore -I/usr/local/include
-I/usr/local/include/QtGui
Good point, I see that. I am surpised about that QT developers don't fix
this problem. I wouldn't put '#include QtCore/*.h' in many headers if
they are living in include/QtCore/ already and have *.pc point to
/usr/local/include/QtCore will cover it.
I believe that it needs to be fix in *.pc files. The qt3 doesn't has
QtCore, so I think it should be no problem.
the fix is needed indeed, moving qt3 headers out from /usr/local/include
will help
Sounds good.
Cheers,
Mezz
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
[kde-freebsd] A bug in QtCore.pc or qglobal.h?
Hello folks,
I am wondering if there is a bug in QtCore.pc for not have
-I/usr/local/include or qglobal.h for should be '#include
QtCore/qconfig.h' - '#include qconfig.h'? A simple test.cc failed to
compile unless I add -I/usr/local/include.
-
# cat test.cc
#include cstdio
#include QtGlobal
extern C int main(void)
{
printf(found version %s, QT_VERSION_STR);
#if QT_VERSION = 0x040200
printf(, OK.\n);
return 0;
printf(, expected version 4.2.0 or higher\n);
return 1;
#endif
}
-
-
# c++ -O -Wall -o test test.cc `pkg-config QtCore --cflags --libs`
In file included from /usr/local/include/QtCore/QtGlobal:1,
from test.cc:2:
/usr/local/include/QtCore/qglobal.h:62:28: error: QtCore/qconfig.h: No
such file or directory
/usr/local/include/QtCore/qglobal.h:942:31: error: QtCore/qfeatures.h: No
such file or directory
/usr/local/include/QtCore/qglobal.h:1139:4: error: #error Qt not
configured correctly, please run configure
/usr/local/include/QtCore/qglobal.h:2036:6: error: #error Qt not
configured correctly, please run configure
-
The solution is to add -I/usr/local/include.
-
# c++ -O -Wall -o test test.cc `pkg-config QtCore --cflags --libs`
-I/usr/local/include
# ./test
found version 4.3.4, OK.
-
-
# pkg-config QtCore --cflags --libs
-DQT_SHARED -I/usr/local/include/QtCore -pthread -L/usr/local/lib
-lQtCore -lz -lm -lgthread-2.0 -lglib-2.0 -liconv
-
BTW: Please add me in CC.
Cheers,
Mezz
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
[kde-freebsd] CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0!
Hello folks, First all, ahze did most of work. Thanks ahze! Yesterday, I am just merely pick up and help him. Right now, he is pretty busy with move to different state but he is still with this project when he can. It might be a bit long email as I am going to list each ports in subject and TODO tasks. Please add my email and gnome@ in CC, no matter what, that way my team and I can follow up better and quicker. Thanks! x11/pixman: Update to 0.10.0 --- Firefox 3 needs it. Orignal, the shared library was bumped and ahze has added a new feature in our USE_GNOME=ltverhack by can control the number of shared library. To control the number of shared library, add the ltverhack:N. Right now pixman has USE_GNOME=ltverhack:9 to make it stays same at libpixman-1.so.9. If anyone want to use ltverhack:N in one of your port, you need to make sure the ABI doesn't change to use it. We will need more users to test to make sure it doesn't break any function in other ports that depend on pixman. I am running on it without change anything and it works great. --- graphics/cairo: Update to 1.6.4 --- Firefox 3 needs it. We have updated most cairo binding ports too. Let us know if we have missed some or cairo breaks your desktop/application. --- graphics/poppler: Update to 0.8.3 --- The shared library version has been changed. All ports that depend on poppler will have to be bump. We still need to bring more ports in MC ports-stable to test it. We don't have it all at the moment, but we will. The poppler-qt and poppler-qt4 still need to be work on. I don't have QT3/QT4 install right now, so it would be nice if one of you can help me. I will installing QT3/QT4 anyway, btw. KDE maintainers, please help to test on koffice-kde3 and kdegraphics3 when poppler-qt* are done as I don't know much about KDE. --- www/firefox3: Update to 3.0 final --- The bsd.gecko.mk has been moved from www/mozilla/ to Mk/. You no longer need to include bsd.gecko.mk/Makefile.common by manual. We still keep it in backward compatibility, so the rest ports won't be break. We haven't add some other ports to have Firefox 3 support yet, so if you want to add in your ports early then feel free to send me patch(es) and I shall add in MC ports-stable. --- TODO tasks: --- - Bring more ports that depend on poppler in ports-stable. - Need to update the document for bsd.gecko.mk (USE_GECKO). - Fix plist in firefox-devel, I hope to get it fix by tomorrow or so in this week. - Add firefox3 in some ports' USE_GECKO if these support, but it's safe to wait either. (no hurry) - Test and test. - Maybe more if there is any --- How to use MC ports-stable and upgrade? --- You can grab marcusmerge[1] and run 'marcusmerge -m ports-stable'. If you want to update your ports tree, you have to run cvsup, csup, portsnap or different method first then marcusmerge second at the everytime. If you want to unmerge your ports tree, you can run 'marcusmerge -U' and be sure to update your ports tree to bring ports back. Be sure to read in marcusmerge manpage[2] for more info. To upgrade your installed ports, you can just simple 'portmaster -a' or 'portupgrade -a'. While we don't have most ports that depend on poppler get bump yet, so be expect to get a bit problem in runtime at the moment. But it is easy to fix by rebuild/reinstall port. To downgrade, well you have to do it by manual. As for the MC ports (GNOME development) users, I have moved these ports from ports module to ports-stable module. You will need to run 'marcusmerge -U' first then update ports tree then MC ports-stable then at last MC ports. [1] http://www.marcuscom.com/downloads/marcusmerge [2] http://www.marcuscom.com/marcusmerge.8.html --- With all of these changes, I want this to be tested in the pointyhat-exp first before merges into FreeBSD ports tree. The more help we get will get faster pointyhat-exp test and merge into FreeBSD ports tree. ;-) Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] heads up: updating GraphicsMagick
On Mon, 12 May 2008 13:12:02 -0500, Mikhail Teterin [EMAIL PROTECTED] wrote: понеділок 12 травень 2008 02:04 по, Erwin Lansing Ви написали: On Mon, May 12, 2008 at 01:42:16PM -0400, Mikhail Teterin wrote: ? 12 ??? 2008 01:36 ??, Erwin Lansing ?? : I intend to update the GraphicsMagick port with the attached diff in a few days. Among other things, it ups the shared-library versions and may otherwise affect your ports. I don't see any of the dependent ports that need changes. Can you send the full patch? I was not planning to touch any dependant ports. Just notifying the maintainers. In that case, your patch is incomplete and cannot be committed. Please provide a full patch including the necessary changes to the dependent ports. I'll take your opinion on whether This isn't option. It's a common rule/practice. Cheers, Mezz or not I can commit an upgrade to a port I maintain under advisement. Thank you. Yours sincerely, -mi -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] Problem building x11-toolkits/qt33 on 6.3/amd64
On Sat, Feb 02, 2008 at 12:08:36PM +1100, Peter Jeremy wrote: I am unable to get qt33 to build and am getting the following errors. My ports tree is up-to-date and I've rebuilt the config file. I've checked pointyhat and it's not reporting any error. Any ideas where to look next? False alarm. I found that the i386 Qt was visible in my searchpath and this was confusing the amd64 build. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpv6DBXYbPF1.pgp Description: PGP signature ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
[kde-freebsd] Problem building x11-toolkits/qt33 on 6.3/amd64
I am unable to get qt33 to build and am getting the following errors. My ports tree is up-to-date and I've rebuilt the config file. I've checked pointyhat and it's not reporting any error. Any ideas where to look next? turion% make clean === Cleaning for qt-3.3.8_6 turion% make === Found saved configuration for qt-3.3.8_6 === Extracting for qt-3.3.8_6 = MD5 Checksum OK for KDE/qt-x11-free-3.3.8.tar.bz2. = SHA256 Checksum OK for KDE/qt-x11-free-3.3.8.tar.bz2. === Patching for qt-3.3.8_6 === Applying extra patch /usr/ports/x11-toolkits/qt33/files/0081-format-string-fixes.diff === Applying FreeBSD patches for qt-3.3.8_6 === qt-3.3.8_6 depends on executable: qmake - found === qt-3.3.8_6 depends on file: /usr/local/libdata/xorg/libraries - found === qt-3.3.8_6 depends on shared library: mng - found === qt-3.3.8_6 depends on shared library: png - found === qt-3.3.8_6 depends on shared library: jpeg - found === qt-3.3.8_6 depends on shared library: Xft.2 - found === qt-3.3.8_6 depends on shared library: audio - found === qt-3.3.8_6 depends on shared library: GLU.1 - found === Configuring for qt-3.3.8_6 The specified system/compiler is not supported: /usr/tmp/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/mkspecs//usr/local/share/qt/mkspecs/freebsd-g++ Please see the PLATFORMS file for a complete list. === Script configure failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the /usr/tmp/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/x11-toolkits/qt33. *** Error code 1 Stop in /usr/ports/x11-toolkits/qt33. turion% ls -l /usr/tmp/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/config.log ls: /usr/tmp/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/config.log: No such file or directory turion% uname -a FreeBSD turion.vk2pj.dyndns.org 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #32: Tue Jan 1 13:59:31 EST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/turion amd64 turion% -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpx5NbJuQ48P.pgp Description: PGP signature ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] multislot cardreader and hald
On Fri, 21 Dec 2007 05:59:44 -0600, Andriy Gapon [EMAIL PROTECTED] wrote: on 20/12/2007 19:03 Jeremy Messenger said the following: I am no expert on hald, but if I understand it correct. If there is no probe in hald then hald will never know if you put/keep your da disks in and pull out. I bet other OSs do the same things. Correct me if I am wrong. I now see what you are saying and this makes a lot of sense indeed. And I agree that FreeBSD kernel is overly verbose about such a condition - after all it is normal that a device with a (field) removable media can have no media. I need to check how FreeBSD 7 behaves in this respect FreeBSD 7 beahves same. I have 7.0-BETA4 (Dec 13). If I put DVD movie in and I will get over 16k lines in message under a minute. http://people.freebsd.org/~mezz/messages.txt.bz2 If I put a blank CD in and I only get less than ten lines in messages. I can't wait for someone to fix FreeBSD because that over 16k lines under a minute is very annoy. Cheers, Mezz - I still use 6.2. BTW, it seems that the messages come from SCSI/CAM code, so USB code might not be a culprit here, it's just a transport for SCSI. OTOH, I wonder why the same doesn't happen for empty CD tray ? - I mean the constant querying (errors are still printed on access). This is a very un-educated guess: maybe HAL knows that acd/cd can have have no media and does some checks before accessing it, but maybe it expects that da always has media and so it tries to access it without any special checks ? I.e. one can simply open and try to read da device or one could issue some SCSI commands to query the actual HW. -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
Re: [kde-freebsd] gettext error
On 2007-Apr-07 06:38:12 -0700, FreeBSD WickerBill [EMAIL PROTECTED] wrote: Whatever the final decision, if it entails another 'world-wide compiler thrash test' then please advise in UPDATING to run the portupgrade with the --batch flag so people don't wind up baby sitting their consoles ;-) Note that '--batch' is not a total panacea. I've been bitten in the past by batch updates breaking my system when I lost config options that I needed (php5 defaults to not building the Apache plugin). -- Peter Jeremy pgpQ4sPJCe79K.pgp Description: PGP signature ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd
