Re: PHP version retirement
On 2019-08-10 01:17, Martin Waschbüsch wrote: Hi all, At least the last two versions of PHP, 5.6 & 7.0, were removed from ports as soon as (or even shortly before) they were no longer actively maintained upstream. I am unsure what the exact reasoning behind this was, but I do not think it is a good idea moving forward: I suppose it is true that outdated & no longer supported versions of PHP could be seen as a security risk. So far so good. However, if, for whatever reason (and I think there are legitimate ones), I still need to use a now obsolete version of PHP, having them removed from ports effectively makes it harder for me to keep everything else up-to-date. I might have to stick with an old ports revision so I cannot update other packages. If I just keep PHP as is, and update other packages, I cannot easily switch to a new version of FreeBSD itself, because I'd have to go back to an old revision of ports (hopefully working with the OS version I updated to) to compile PHP and then do other packages. Libraries / dependencies may change and break my PHP, etc. So, on top of possible security concerns for the outdated software I use, I basically get an overall less secure / stable system to boot. Now, I am not suggesting we leave every old and outdated PHP version in ports, but why remove a port just days after it received its last security update upstream? (With PHP 5.6 it was actually removed from ports before it got its last update upstream). Would it not be better to have, say, the last two versions before current stable still in ports but with a huge disclaimer saying: use at your own risk, etc.? What do y'all think? Martin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-port Umm this was just the kick in the pants that I needed to switch to PHP 7. See https://www.glaver.org/blog/?p=1109 for a desperation 'I need PHP5.6' hack which I used during this update. I must say that the update to PHP 7 was relatively painless - there is PHP6 to PHP7 update support and lots of help/suggestions. I also found an embarassing amount of bad PHP code during the update process, something I should have suspected I would find. Note that the changes suggested by Mr. Glaver seem to be applicable to new versions of the Ports tree UPDATING and .../.mk files so you can use the latest Ports tree with the appropriate minor modifications. You can even generate a script to apply these updates/mods each time you run 'portsnap'. But I digress... -- Patrick Powell Astart Technologies papow...@astart.com1509 Hollow Ct., Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11/kde4 pkg not present in repository
This was not quite what I was expecting. Is there a site where you can do a search for the status of a build for a package? This site shows statistics about the numbers of packages, etc., but not what was built, when, etc. Perhaps I am asking the wrong question... On 09/06/17 21:37, Yuri wrote: On 09/06/17 18:54, Patrick Powell wrote: The x11/kde package is not present on the latest repository, for FreeBSD 11.0 and 11.1. You can check status of individual packages here: http://package21.nyi.freebsd.org Yuri -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
x11/kde4 pkg not present in repository
The x11/kde package is not present on the latest repository, for FreeBSD 11.0 and 11.1. I was wondering if there is a log/information about which packages have been built or failed to build? I did a quick check of the FreeBSD documentation but there does not seem to be information on this. Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: State of FUSE on FreeBSD
A grateful note of thanks for this effort, especially to Nikolaus Rath and the FreeBSD maintainers! On 08/03/17 13:22, Julian Elischer wrote: On 3/8/17 7:38 pm, Nikolaus Rath wrote: Hello, I am the upstream maintainer of libfuse. I'd like to refresh / improve the FreeBSD support in libfuse. My goal is for libfuse not to require any FreeBSD specific patches. For us libfuse "just worked" so we haven't touched it. We had to touch the kernel part of fuse a little so remove some overly restrictive permission checks, and fix some issues to do with page boundaries (from memory) but nothing in the library. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)
On 07/19/17 23:19, Konstantin Belousov wrote: On Wed, Jul 19, 2017 at 10:06:13PM -0400, Alexander Kabaev wrote: On Wed, 19 Jul 2017 22:50:04 +0200 (CEST) Gerald Pfeifer <ger...@pfeifer.com> wrote: On Fri, 14 Apr 2017, Alexander Kabaev wrote: it was suggested multiple times that the whole fixinc step is ultimately harmful and serves no useful purpose and probably should be disabled in built packages outright. Is there a reason not to do it? Even Redhat appears to do the slimming in their rpms: For the more current lang/gcc* ports (not the gcc5-aux and gcc6-aux ports which I do not maintain) I have now removed packaging the headers processed by fixincludes, so any problems in that direction should be gone. Gerald Thank you, Gerald! This is very good news, thank you. Gcc should be much more usable now. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Do you have a patch/revision ID for this change? I would like to test this with some ports that gcc failed on. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to get pkg to recognize local repository?
On 07/16/17 22:21, Matthias Apitz wrote:
El día lunes, julio 17, 2017 a las 05:10:06a. m. +, Thomas Mueller escribió:
How do I get pkg to recognize a local repository such as /mnt/usr/packages/All,
or does pkg only recognize remote repositories?
...
I use:
$ ls -l /usr/local/etc/pkg/repos/*.conf
-rw-r--r-- 1 root wheel 35 12 mar. 11:05
/usr/local/etc/pkg/repos/FreeBSD.conf
-rw-r--r-- 1 root wheel 96 12 mar. 11:05
/usr/local/etc/pkg/repos/myrepo.conf
$ cat /usr/local/etc/pkg/repos/FreeBSD.conf
FreeBSD: { enabled: no }
$ cat /usr/local/etc/pkg/repos/myrepo.conf
FreeBSD: {
url: "file:///usr/local/PKGDIR.20170304",
enabled: true,
}
HIH
matthias
Just out of curiosity (and because I might want to do this) how can you
specify two (or more) repositories
and have them searched in some order. For example, you might have a
local respository with some
ports/packages that you are currently debugging/fixing. You want pkg to
search the local respository
first and then if it does not find the packages to use the default
(remote) repository.
--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting Cell 858-518-7581 FAX 858-751-2435
Web: papowell at astart dot com
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work
ows categories for builds for 8.4 9.3 10.1 10.3 11.0 head (Nothing for stable/*/ .) But the 10.3 rows show no package builds. I would guess that they start once 10.1 stops (approximately). So it may be that 11.1 will not get package builds until 11.0 stops (approximately). If so unless lang/gcc* are changed to bootstrap differently they will configure to match release/11.0.1/ and will not be compatible with the vm_ooffset_t and vm_pindex_t changes in stable/11/ and release/11.1.0/ . But as I understand updating how the lang/gcc* builds work to remove such dependencies is under investigation. I do not know any timing relative to release/11.1.0/ if my understanding is right. Until then (if I was right): Unless there are separate packages made for targeting release/11.0.1/ vs. release/11.1.0/ it is not obvious when lang/gcc* packages will be generally compatible with various folks choices about what to install as the system version within the release/11.*/ and stable/11/ family. This would likely be true even if they were built on release/11.1.0/ : then release/11.0.1/ likely would have compatibility problems. The ABI versioning does not cover the specific issues involved based on how vm_ooffset_t and vm_pindex_t were changed and what the lang/gcc* builds do relative to such changes. Yet there is incompatibility for some fairly-significant-usage ports. Aspect #2: stable/10/ and release/10.4.0/ Just covered for completeness: I do not see a MFC of -r313194 to stable/10/ : its sys/sys/types.h dates back to 2015-Oct-10. So it looks like 10.x has a permanent difference in this area: 10.x continues to get separate lang/gcc* package builds from 11.x and later. No problem for this context as far as I know. Note: To simplify I choose to not be explicit about what authors wrote what original text. If that becomes an issue, it is correctable. Blame me for any errors in the above. === Mark Millard markmi at dsl-only.net ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
How to use cached packages
I ran into a problem where I needed to reinstall a package. However, I did not have network access to the pkg repository. I did have a system which had all of the pkgs which I needed in the pkg cache. I can easily copy these to the system, as well as the pkg database, etc. So: is there a SIMPLE way to have pkg check to see if a pkg is already in the pkg cache and use that before trying to go to the repository? Is there a SIMPLE way to prevent pkg from trying to check the pkg repository for an update? I strongly suspect that something like: pkg --do_not_check_for_latest_version --use_cached_pkg install firefox Any help on this before I tear out the three strands of hair I have left would be appreciated. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problem with gcc5 std library when building ports
On 10/26/16 16:01, Dewayne Geraghty wrote: Have spent a couple of days trying to build around 800 ports with gcc5. This one has me stumped! Can anyone help regarding the apparant absence of snprintf from std? Am I missing something, perhaps LDCONFIG or? I've looked in /usr/ports/Mk/ bsd.gcc.mk and /usr/ports/Mk/bsd.port.mk but this is an area that I'm unfamiliar, so nothing really stood out. If I change the compiler from gcc5 to clang everything compiles and runs correctly. I have in /etc/make.conf USE_GCC= 5 and to use clang, I just comment out the above. So everything is constant, on FreeBSD 10.3Stable (updated and rebuilt overnight) For example: /usr/ports/devel/jsoncpp (but many share this problem) g++5 -o buildscons/linux-gcc-FreeBSD/src/lib_json/json_reader.o -c -O2 -pipe -DOPENSSL_NO_SSL2 -DOPENSSL_NO_SSL3 -g0 -ggdb0 -DSTRIP_FBSDID -UDEBUGGING -UDEBUG -march=c3-2 -mtune=c3-2 -Wl,-rpath=/usr/local/lib/gcc5 -fno-strict-aliasing --std=c++11 -Wl,-rpath=/usr/local/lib/gcc5 -Iinclude src/lib_json/json_reader.cpp src/lib_json/json_reader.cpp: In member function 'std::__cxx11::string Json::Reader::getLocationLineAndColumn(Json::Reader::Location) const': src/lib_json/json_reader.cpp:34:18: error: 'snprintf' is not a member of 'std' #define snprintf std::snprintf And for completeness: # ldconfig -r | grep -E "gcc|\+" search directories: /lib:/usr/lib:/usr/lib/compat:/usr/local/lib:/usr/local/lib/gcc5:/usr/local/lib/heimdal:/usr/local/lib/perl5/5.20/mach/CORE 35:-lgcc_s.1 => /lib/libgcc_s.so.1 38:-lc++.1 => /usr/lib/libc++.so.1 126:-lcc1.0 => /usr/local/lib/gcc5/libcc1.so.0 127:-lgcc_s.1 => /usr/local/lib/gcc5/libgcc_s.so.1 128:-lstdc++.6 => /usr/local/lib/gcc5/libstdc++.so.6 129:-lcilkrts.5 => /usr/local/lib/gcc5/libcilkrts.so.5 130:-lssp.0 => /usr/local/lib/gcc5/libssp.so.0 131:-lquadmath.0 => /usr/local/lib/gcc5/libquadmath.so.0 132:-lgfortran.3 => /usr/local/lib/gcc5/libgfortran.so.3 133:-lobjc.4 => /usr/local/lib/gcc5/libobjc.so.4 134:-lgomp.1 => /usr/local/lib/gcc5/libgomp.so.1 135:-lgomp-plugin-host_nonshm.1 => /usr/local/lib/gcc5/libgomp-plugin-host_nonshm.so.1 136:-litm.1 => /usr/local/lib/gcc5/libitm.so.1 137:-latomic.1 => /usr/local/lib/gcc5/libatomic.so.1 Regards, Dewayne ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Way way back in the early days of the standardization of the C library, the Great Minds decided that putting snprintf into the C library would not be done as it was 'not part of the deployed routines' or something similar. So they left in sprintf, which ended up causing more boundary overruns and attacks then any other routine. Don't get me started about strcpy, etc. etc. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Inconsistency? (was Re: misc/jive deleted)
On 10/26/16 03:56, David Demelier wrote: On 10/26/2016 09:32 AM, Kurt Jaeger wrote: Hi! I think unless FreeBSD makes explicit antichrist statement, there is no problem having a daemon mascot. I have never heard any religious problem so far. Or then I missed something. Approx. 20 years ago (?), some FreeBSD developer with a old-style logo on a t-shirt was asked to leave some saloon in Texas because the logo suggested that they worship the antichrist. Brilliant ! :-) There was a job (in rec.humor.funny?) about it 8-} That's why this reference to the demon logo is made 8-} ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" I have an autographed T Shirt by the artist - Phil Foglio. Who also did the artwork for the MythAdventures (Graphic Novel) as well as others. When asked for an update at one of the San Diego Comic Cons, he just laughed hysterically and then politely said 'No!' See http://www.studiofoglio.com/ for examples of his work. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP] extracting LoadModule out of httpd.conf
On 08/12/16 09:15, olli hauer wrote: On 2016-08-12 16:32, Patrick Powell wrote: On 08/10/16 14:07, Miroslav Lachman wrote: Mathieu Arnold wrote on 08/10/2016 17:42: Hi, It is coming. https://reviews.freebsd.org/D7460 constructive comments welcome. ... I plead with the people making this change to update apachectl to list the modules that are loaded: # apachectl modules mod_perl It is already there, use the same parameter as for httpd direct `apachectl -M' And when you update mod_perl and the U&*(()* httpd.conf file gets mangled and the mod_perl line is removed or commented out, you now stand a fighting chance of finding this. With the change to itty-bitty files this would be even more useful. Just out of curiosity, how are you going to now deal with temporarily commenting out LoadModule entries? Since more then one year mod_perl2 installs a .sample file and no longer changes httpd.conf https://svnweb.freebsd.org/ports/head/www/mod_perl2/pkg-plist?r1=35=389628 But I have to admit this is not the case for all modules in the ports tree Thanks for the pointer to the -M option. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP] extracting LoadModule out of httpd.conf
On 08/10/16 14:07, Miroslav Lachman wrote: Mathieu Arnold wrote on 08/10/2016 17:42: Hi, It is coming. https://reviews.freebsd.org/D7460 constructive comments welcome. I don't think I will do that for Apache 2.2 because it expires at the end of the year. I agree that there are problems with LoadModule lines in httpd.conf. Because some modules add / remove or comment / uncomment lines in this file making pkg upgrade painful. So I moved some 3rd party modules configuration in to different included file to solve this issue. But I am not sure I we really need to split httpd.conf in to 20, 30, or more little files as proposed in comments in https://reviews.freebsd.org/D7460 I disagree with "httpd.conf never gets changed by the user" - we are always editing httpd.conf on all our servers. For example Listen to listen only on specified IP, ServerAdmin, CustomLog format and couple of Included *.conf files at the end of the httpd.conf I cannot agree with splitting httpd.conf in to many small files. Change like this was made for dovecot.conf (24 files in conf.d) and it is lot of pain to find something in this mess or edit more than one thing in one file. I understand that machine (scripted) editing of one big file is worse than deleting / replacing small files but for us humans one (or a few) files are easily editable than tens of small files. So... LoadModule can be extracted from httpd.conf (and nothing else). I am not sure if it should be one file for all modules or separate files for each module. Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" I plead with the people making this change to update apachectl to list the modules that are loaded: ># apachectl modules mod_perl And when you update mod_perl and the U&*(()* httpd.conf file gets mangled and the mod_perl line is removed or commented out, you now stand a fighting chance of finding this. With the change to itty-bitty files this would be even more useful. Just out of curiosity, how are you going to now deal with temporarily commenting out LoadModule entries? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libvncserver
On 06/24/16 14:51, Walter Schwarzenfeld wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210533: -Solution Add this line CONFIGURE_ARGS= --without-libva to libvcnserver/Makefile ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Perhaps this might be better? CONFIGURE_ARGS+= --without-libva -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how do you force make install to overwrite conflicting files from another port?
On 06/03/16 10:53, Lowell Gilbert wrote: Patrick Powell <papow...@astart.com> writes: Suppose that you have a portA which is a dependency of a lot of other ports. You also have a portB which is a replacement/update/upgrade for portA. PortB provides replacements for the executables generated/supplied by PortA but for various reasons you still want to use some of PortA installed items such as libraries, etc. I tried doing the following: # pkg install PortA # cd /usr/ports/xxx/PortB # make install Installing PortB... pkg-static: PortB conflicts with PortA (installs files into the same place). Problematic file: /usr/local/bin/utilityl *** Error code 70 Is there an option, or a way similar to using 'make FORCE_PGK_REGISTER=YES install' to force overwriting the conflicting files? Not directly, no. The way to do it straight from the ports tree is to remove the "PortA" *first* (with "pkg delete -f"), and then install "PortB". You end up losing the dependency information that PortA had formerly had, but things will work. Upgrade tools (pkg, portmaster, portupgrade, at least) have a "-o" option that fixes up the dependency information. When you do the 'pkg delete -f PortA' then it will also delete the libraries installed by PortA. if you do 'cd ...PortB; make install' and it will now install the files that were in conflict, but there are now some libraries installed by PortA which are missing. I understand that this is on the outskirts of package/port management, but there are times when you want to install a test version of a utility which has only part of the functionality of another port. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
how do you force make install to overwrite conflicting files from another port?
Suppose that you have a portA which is a dependency of a lot of other ports. You also have a portB which is a replacement/update/upgrade for portA. PortB provides replacements for the executables generated/supplied by PortA but for various reasons you still want to use some of PortA installed items such as libraries, etc. I tried doing the following: # pkg install PortA # cd /usr/ports/xxx/PortB # make install Installing PortB... pkg-static: PortB conflicts with PortA (installs files into the same place). Problematic file: /usr/local/bin/utilityl *** Error code 70 Is there an option, or a way similar to using 'make FORCE_PGK_REGISTER=YES install' to force overwriting the conflicting files? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: HTML5 videos crashes Firefox
My setup is a little different. I have a Dell M6800 with NVIDEA:
vgapci0: port 0xe000-0xe07f mem
0xf400-0xf4ff,0xe000-0xefff,0xf000-0xf1ff irq 16
at device 0.0 on pci1
nvidia0: on vgapci0
vgapci0: child nvidia0 requested pci_enable_io
vgapci0: child nvidia0 requested pci_enable_io
vgapci0: Boot video device
From /var/log/Xorg.0.log:
[ 12870.311] (II) LoadModule: "glx"
[ 12870.311] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[ 12870.319] (II) Module glx: vendor="NVIDIA Corporation"
[ 12870.319]compiled for 4.0.2, module version = 1.0.0
[ 12870.319]Module class: X.Org Server Extension
[ 12870.319] (II) NVIDIA GLX Module 346.96 Sun Aug 23 21:29:48 PDT 2015
[ 12870.319] (II) LoadModule: "dbe"
[ 12870.319] (II) Module "dbe" already built-in
[ 12870.319] (II) LoadModule: "dri"
[ 12870.319] (II) Module "dri" already built-in
[ 12870.319] (II) LoadModule: "dri2"
[ 12870.319] (II) Module "dri2" already built-in
[ 12870.319] (II) LoadModule: "extmod"
[ 12870.319] (II) Module "extmod" already built-in
[ 12870.319] (II) LoadModule: "record"
[ 12870.319] (II) Module "record" already built-in
[ 12870.319] (II) LoadModule: "vnc"
[ 12870.319] (II) Loading /usr/local/lib/xorg/modules/extensions/libvnc.so
[ 12870.453] (II) Module vnc: vendor="Constantin Kaplinsky"
[ 12870.453]compiled for 1.17.4, module version = 1.0.0
[ 12870.453]Module class: X.Org Server Extension
[ 12870.453]ABI class: X.Org Server Extension, version 9.0
[ 12870.453] (II) LoadModule: "nvidia"
[ 12870.463] (II) Loading /usr/local/lib/xorg/modules/drivers/nvidia_drv.so
[ 12870.463] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 12870.463]compiled for 4.0.2, module version = 1.0.0
[ 12870.463]Module class: X.Org Video Driver
[ 12870.463] (II) NVIDIA dlloader X Driver 346.96 Sun Aug 23 21:08:26
PDT 2015
[ 12870.463] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 12870.463] (--) Using syscons driver with X support (version 16777218.0)
[ 12870.463] (--) using VT number 9
When I run firefox and try to view a video from youtube I get:
laptop_93: {10} % firefox | /tmp/f
Bus error (core dumped)
I updated to the latest pkg versions of firefox.
Side Note: I set up a couple of VirtualBox VMs, one for 10.3 RC3 and
one for 9.3. Just out of
curiousity I ran firefox on them and I was able to view the videos. I
am wondering if the
issue is related to the NVIDIA driver on my laptop. I wonder if the
issue is related to the NVIDIA
driver/GPU support.
On 03/31/16 14:31, Andrea Venturoli wrote:
On Tue, 29 Mar 2016 10:37:47 -0700, Christoph Brinkhaus wrote:
The only thing I get are error messages as below:
$ ssh fox firefox
libGL error: failed to open drm device: No such file or directory
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
1459272168729 addons.xpi WARNBootstrap state is invalid
(missing
add-ons:
Guess you have an Intel GPU (mine is a Radeon).
I got another machine, which runs 10.1/amd64 with an Intel GPU and
that works fine (btw, not even those warnings).
I also saw you tried ssh to another box and I did that too.
Just to summarize:
_ 10.2/i386/Radeon -> crash;
_ 10.1/amd64/Intel -> fine;
_ ssh from 10.2/i386/Radeon to 10.1/amd64/Intel -> fine.
Patrick, could you please tell us what GPU you have? Configured options?
Just wish I could get some info out of that core :(
bye & Thanks
av.
--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting 858-874-6543 FAX 858-751-2435
Web: www.astart.com
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: HTML5 videos crashes Firefox
I just tried one of the videos and my firefox crashed as well. FreeBSD laptop_93.private 9.3-RELEASE-p30 FreeBSD 9.3-RELEASE-p30 #0: Mon Nov 2 10:11:50 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src /sys/GENERIC amd64 X firefox-43.0.3_1,1 Web browser based on the browser portion of Mozilla On 03/29/16 09:20, Andrea Venturoli wrote: On Sun, 27 Mar 2016 10:12:07 -0700, Christoph Brinkhaus wrote: Hello Andrea, Hello and thanks for your help. I have tried the first video I get from youtube without problems. May be you post an url where the crash occurs. I can just go to youtube.it/com and choose a random one; e.g.: https://www.youtube.com/watch?v=hrJLzq_coUg https://www.youtube.com/watch?v=LbVEXCh63pQ (Please forgive me for linking that crap, but you asked it :) The options I use are according to pkg info ALSA : on BUNDLED_CAIRO : off CANBERRA : off DBUS : on DEBUG : off DTRACE : off FFMPEG : on GCONF : off GIO : on GNOMEUI : off GTK2 : on GTK3 : off INTEGER_SAMPLES: off LIBPROXY : off OPTIMIZED_CFLAGS: off PGO : off PROFILE : off PULSEAUDIO : off TEST : off I had: ALSA : off BUNDLED_CAIRO : on CANBERRA : off DBUS : on DEBUG : off DTRACE : on FFMPEG : on GCONF : off GIO: on GNOMEUI: off GTK2 : off GTK3 : on INTEGER_SAMPLES: off LIBPROXY : off OPTIMIZED_CFLAGS: on PGO: off PROFILE: off PULSEAUDIO : on RUST : on TEST : off However, I tried your set of options (with RUST on and off, since you don't have it): things didn't change, still crashing. > The version is 45.0.1,1 45.0.1_3,1, here, but I also went through 45.0.1,1, which crashed in the same way. May be you try pkg_libchk from sysutils/bsdadminscripts if the libraries are in order. I used sysutil/libchk, which should do more or less the same thing: there were some unresolved references in binaries which should not be related to FireFox: I solved that, but it's still crashing. Any other thing to check? Do you have an i386 kernel? Yes. I am not sure if there might be a possible issue. Any pointer on that? *If* firefox is incompatible with i386 I might switch, but it's going to be a very long work; so I'd like to get some hint about this before I venture myself in such a trouble. When I have started using FreeBSD I thought amd64 is just for AMD processors. But amd64 is also ok for Intel. I know the difference. However this box's install predates amd64: I was using it more than 10 years ago (5.x or 6.x possibly) and it's still there through several hardware and software upgrades. Until now I haven't found any good reason to drop everything and reinstall from scratch... > This is likely the newest one. I am not completely up to date because > I mostly upgrade only when there are vulnerabilities. So do I, but I've gone through every minor update since I'm experiencing these crashes. bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: www/mod_auth_mysql2 should be disabled for apache24
On 11/06/15 08:03, Andreas Nilsson wrote: Hello, Trying to resort to this module for mysql auth support in apache, I got the exact same problem: httpd: Syntax error on line 533 of /usr/local/etc/apache24/httpd.conf: Syntax error on line 2 of /usr/local/etc/apache24/Includes/my-ssl.conf: Cannot load libexec/apache24/mod_auth_mysql.so into server: /usr/local/libexec/apache24/mod_auth_mysql.so: Undefined symbol "ap_requires" Since ap_requires was removed with apache24 release, there is no point in building for apache24. Best regards Andreas ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Apparently these modules have been replaced/upgraded by mod_dbd Here is what I have in an httpd.conf file: LOADMODULE # LoadModule authn_dbd_module libexec/apache24/mod_authn_dbd.so LoadModule authz_dbd_module libexec/apache24/mod_authz_dbd.so LoadModule dbd_module libexec/apache24/mod_dbd.so DBDriver mysql DBDParams "host=127.0.0.1 dbname=useraccounts user=secret pass=password" DBDMin 1 DBDKeep 8 DBDMax 20 DBDExptime 300 And a matching entry in htaccess. I suspect this could be added to the VirtualHost entry rather than in a separate file. AuthBasicProvider dbd AuthDBDUserPWQuery "SELECT password FROM permissions WHERE id = %s" Require valid-user AuthType Basic AuthName "accounting" There were quite a few helpful 'HOWTOs' on using the mod_dbd module and MySQL. Note that you may need to update/add MySQL support to the devel/apr1 module as it is not included by default. I hope this helps or at least gives some hints on using the mod_dbd module approach. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
9.3 to 10.2 migration, determining if clang is used
I just started doing a 9.3 to 10.2 migration of a bunch of applications and discovered that some of the options used to generate the applications were slightly different. I just know that this has been covered before, but I could not find a definitive method or set of methods to use to determine if the old GCC compiler or the new CLANG compiler is being used. Could the ports wizards (and/or autoconf experts) help me a bit? (Aside: the clang compiler diagnostics and warnings are very thorough and quite clear. Nicely done, especially the addition of the information about the flag to turn this warning off. I also like the pragmas to control warnings and the push/pop pragma facility. This may have been in the GCC compiler but I missed it.) 1. If the application is to be generated via the PORT infrastructure, what do you put in the port Makefile to determine if CLANG (10.2) or GCC (9.3) is being used? Something like below. Note: the examples below are a bit contrived, but the idea is to set some MAKE variable to different values depending on CLANG or GCC in use. .if defined(CC_IS_CLANG) MYFLAGS+= -Wall -Werror -Wno-error=unused .else .if defined(CC_IS_GCC) MYFLAGS+= -Wall -Werror -Wno-unused .endif .endif 2. A simple test for configure that checks the for the CLANG compiler: # Check for programs AC_PROG_CC # we may need to add this to the configure macro set? AC_PROG_CLANG if test "$ac_cv_using_clang" = yes; then CFLAGS="$CFLAGS -Wall -Werror -Wno-error=unused" else if test "$ac_cv_c_compiler_gnu" = yes; then CFLAGS="$CFLAGS -Wall -Werror -Wno-unused" fi; fi; It could even be something simpler if the AC_PROG_CC configure macro sets, for example, the $ac_gcc_version shell variable with a value that indicates CLANG in use then the following would be useful: if test "$ac_gcc_version" -gt 999 ; then ... fi; -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS-UP] switching default Perl to 5.22
On 08/28/15 09:16, Mathieu Arnold wrote: +--On 28 août 2015 19:11:21 +0300 Konstantin Belousov <kostik...@gmail.com> wrote: | Previous policy, even if informal, was to wait for 5.xx.1 before bringing | the port to the tree. May be, we should wait for xx.1 before switching | the default port, at least ? The previous policy was "oh shit, our default version is not supported any more, let's try and see how it goes with the version that will not be supported after this year." I've been bumping default Perl versions every six months for a long time so that we could catch up. Also, if everyone waits for the .1 release before using it, there will never be a .1 release. Ummm... Guilty as charged. The only reason I updated to 5.20 was that the pkg repository changed. However, I think that making 5.22 the default before fixing up (for me at least) some issues with modperl support might be a bit premature. Just for my information, and because I just know you will laugh and you need some amusement: Where and what do you stick 'USE_PERL='? /etc/make.conf? I don't mind trying to compile the modules I use and see if they work. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS-UP] switching default Perl to 5.22
Please do not switch to a new version of Perl until ModPerl2 works. This, for me, is a show stopper, and I suspect for a lot of people. Do you have a list of the current Perl Modules or associated items that do not work? On 08/28/15 08:06, Kurt Jaeger wrote: Hi! In one or two weeks, I'll be switching the default Perl version to 5.22, and from now on, the new Perl will be added at the end of May when released, and switched to at the beginning of September. mod_perl is still broken with 5.22. Which is very sad. So maybe it's premature to switch the default ? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Apache 2.4 must become default NOW
On 07/13/14 17:46, Michelle Sullivan wrote:
Baptiste Daroussin wrote:
On Mon, Jul 07, 2014 at 12:27:48AM +0200, olli hauer wrote:
On 2014-07-05 19:09, Bjoern A. Zeeb wrote:
Hi,
given ports@ ist listed as maintainer, you get the email. The Subject says it.
The world has moved on; in March I had a hard time arguing, in July I just
cannot anymore. We must switch to 2.4; whatever breaks needs fixing, but
somehow other distributions have managed and we did not and keep screwing our
users missing a lot of security features.
Please fix!
—
Bjoern A. Zeeb Come on. Learn, goddamn it., WarGames, 1983
Hi Bjoern,
nothing against this change, except your complain comes a little bit late.
The portstree was already tagged for 9.3 some days ago so this change would be
a possible issue for all users using the 9.3 packages.
Before the default version can be changed a full expr. run by portmgr@ is
required and all possible issues should be fixed.
Unluckily we have a rolling ports tree (not like RHEL and others where such a
change happens during new major releases) so there should be also a time frame
to warn users about such a change.
I remember endless discussions about the removal of apache13 after it was
already deprecated nearly one year after upstream deprecation ...
Just provide the patch for the change and warn the user about the change, now,
just do not MFH it to the quarterly branch, so the user willing to keep apache22
for a while can live on the quarterly branch for the next 3 months :)
I don't see the problem for the people using 9.3 packages, if they want
stability they will stay on quarterly branch which still provides by default
apache22 for 3 month.
Hopefully when pkg 1.3 will land we will be able to add new feature to the ports
tree aka build the apache module for all supported apache version leading to
anyone using package being able to chose the apache version they what whatever
the default is (but we are not there yet :))
One would have hoped that mod_perl2 would have had this removed first:
.if ${APACHE_VERSION} 22
BROKEN= Does not build with apache24
.endif
Just my small (557 packages) build set:
Skipped ports: devel/bugzilla44 devel/p5-Log-Dispatch
www/p5-Apache-DBI www/p5-HTML-Mason www/p5-HTML-Mason-PSGIHandler
www/p5-MasonX-Profiler www/p5-RT-Authen-ExternalAuth www/p5-libapreq2
www/rt40
Michelle
I believe that this has been fixed for at least since Sept 2014. There
is a 'test and debugging' version of mod_perl2 that appears to have the
required mods/changes, but they have not been rolled into the upstream
distribution.
I wonder what happened to the mod_perl updating process...
--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting 858-874-6543 FAX 858-751-2435
Web: www.astart.com
___
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: Generating port changes easily
On 02/27/15 23:34, Kubilay Kocak wrote: On 28/02/2015 3:35 AM, Patrick Powell wrote: I have made some modifications to a port - couple of lines in the Makefile, and an updated pkg-plist. Once upon a time I was shown a script (run_this_script?) to help with updating a port. 1. Copy the original files in the port to XXX.orig (or something) For example cp Makefile Makefile.orig 2. Make your changes For example: vi Makefile 3. Now run this script which will generate a DIFF file which can be posted: run_this_script ... /tmp/changes.shar ? run_this_script ... /tmp/diffs ? 4. Post the generated file to bugzilla with an update request. Ummm... is there such a 'run_this_script' or am I indulging in wishful thinking? If the changes you make are in the ports files, porttools has a `port diff` command (which uses a reference ports tree to create diffs against. You can use /usr/ports as that reference, and in fact I believe that is the default. You can then just port diff path-to-patch-file.diff, ready for attachment into a new bugzilla issue. If the patch is against WRKSRC source code, you can a) cp WRKSRC/file WRKSRC/file.orig b) edit file c) make makepatch (from the port dir) makepatch recursively searches WRKSRC for *.orig files, and automatically creates correctly named patch-foo patch files in /files for you. Hope that helps -- koobs Excellent suggestions, both. I tried port diff AND make makepatch - both seemed to work as advertised. Thanks for the help! -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ 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
Generating port changes easily
I have made some modifications to a port - couple of lines in the Makefile, and an updated pkg-plist. Once upon a time I was shown a script (run_this_script?) to help with updating a port. 1. Copy the original files in the port to XXX.orig (or something) For example cp Makefile Makefile.orig 2. Make your changes For example: vi Makefile 3. Now run this script which will generate a DIFF file which can be posted: run_this_script ... /tmp/changes.shar ? run_this_script ... /tmp/diffs ? 4. Post the generated file to bugzilla with an update request. Ummm... is there such a 'run_this_script' or am I indulging in wishful thinking? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ 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: new warning - ap24-mod_perl2 has no direct installation candidates, change it to ap24-mod_perl2
I upgraded pkg to today to 1.4.10 and got the following new (and
different) warning:
{142} # pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
Checking for upgrades (43 candidates): 97%
ap24-mod_perl2 has no direct installation candidates, change it to
ap24-mod_perl2 has no direct installation candidates, change it to
ap24-mod_perl2? [Y/n]:
Checking for upgrades (43 candidates): 100%
Processing candidates (43 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
{144} # pkg -v
1.4.10
.
The ap24-mod_perl2 port is www/mod_perl2. I use different options from
the default, so I need to compile the port.
I also lock it so that pkg does not try to modify it when I do 'pkg
upgrade'.
This has worked fine until the latest version of pkg. I now get the 'no
direct installation candidates' message.
Question: why is this message generated?
Question: what can I do to suppress the message and still not have pkg
update the port from the repository?
--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting 858-874-6543 FAX 858-751-2435
Web: www.astart.com
___
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: /compat/linux and /usr/compat/linux
On 02/11/15 10:23, Martin Simmons wrote: FWIW, the pre-9.0 installer (sysinstall) creates /usr/compat with /compat linked to it, but it bsdinstall doesn't. See http://lists.freebsd.org/pipermail/freebsd-emulation/2011-December/009339.html __Martin ___ freebsd-emulat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org This is what I was wondering about. So it happened wayback... I suspect that creating a symbolic link from /compat to (say) /usr/compat or /usr/local/compat would cause problems with ports and PKGng. Not on installation but on deletion and/or update. Any comments from the freebsd-ports? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ 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: /compat/linux and /usr/compat/linux
On 02/12/15 06:58, Patrick Powell wrote:
On 02/11/15 06:54, Patrick Powell wrote:
Note: just as a side note on this, shouldn't the location actually
be /usr/local/compat? But I digress...
Murphy's Law Strikes Again. I wanted to see what the latest
port/package did:
# pkg install linux_base-c6
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
The following 1 packages will be affected (of 0 checked):
New packages to be INSTALLED:
linux_base-c6: 6.6_2
The process will require 0 GiB more space.
21 MiB to be downloaded.
Proceed with this action? [y/N]: y
pkg:
http://pkg.FreeBSD.org/FreeBSD:9:amd64/latest/All/linux_base-c6-6.6_2.txz:
Not Found
This is interesting. I have:
d11rmi7: {120} # pkg search linux_base-c6
linux_base-c6-6.6_2
But when I checked the URL
http://pkg.FreeBSD.org/FreeBSD:9:amd64/latest/All/ I found
linux_base-c6-6.6_3.txz
Is the repository index out of step with the repository contents? Note
that I did a port upgrade before
trying the install.
--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting 858-874-6543 FAX 858-751-2435
Web: www.astart.com
___
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: FreeBSD Bug 196703, p5-Wx, wxglade, and webkit-gtk2
On 02/11/15 12:36, Dave Hayes wrote: Hello. :) I'm trying to get p5-Wx to build properly. A test program fails with this: Can't load '/usr/local/lib/perl5/site_perl/mach/5.18/auto/Wx/Wx.so' for module Wx: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/local/lib/libwx_baseu-3.0.so.0 not found at /usr/local/lib/perl5/5.18/mach/DynaLoader.pm line 190. at client/wxtest.pl line 6. This apparently is a side effect of the GCC compiler version used to compile things. Here is a similar problem. You will have to have the correct C++ libraries for the version of GCC compiler you have installed. Good luck on this one... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192928 -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ 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 segmentation fault
This just happened today. Any comments/suggestions?
laptop_93: {356} # pkg -v
1.4.4
laptop_93: {357} # pkg delete p5-Archive-Zip
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0
packages in the universe):
Installed packages to be REMOVED:
p5-Archive-Zip-1.42
The operation will free 226 kB.
Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling p5-Archive-Zip-1.42...
[1/1] Deleting files for p5-Archive-Zip-1.42: 100%
laptop_93: {358} # pkg install p5-Archive-Zip
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
apr-1.5.1.1.5.4 is locked and may not be modified
apr-1.5.1.1.5.4 is locked and may not be modified
apr-1.5.1.1.5.4 is locked and may not be modified
Checking integrity... done (0 conflicting)
The following 1 packages will be affected (of 0 checked):
New packages to be INSTALLED:
p5-Archive-Zip: 1.42
The process will require 226 kB more space.
Proceed with this action? [y/N]: y
[1/1] Installing p5-Archive-Zip-1.42...
[1/1] Extracting p5-Archive-Zip-1.42: 100%
Child process pid=50074 terminated abnormally: Segmentation fault: 11
--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting 858-874-6543 FAX 858-751-2435
Web: www.astart.com
___
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: BIND REPLACE_BASE option
On 01/15/15 09:00, Roger Marquis wrote: This sounds like you, like many other people have done in the past, have built an in-house solution based on the tools available at the time, which includes 'make package' I wouldn't call it an in-house solution since the package target is a feature of the ports infrastructure. We simply 'make package' and install other systems from the resulting package. This does not, however, appear to be as well supported by portsng/pkgng as it was in the previous versions. Now it just exits with no message and a 0 exit-code without creating the package unless you've created /usr/ports/packages and/or specified one or more of WRKDIRPREFIX, PACKAGES and PKGREPOSITORY. What documentation there is seems to be based on older versions (like much of the FreeBSD website) and I haven't found anything on the differences between 'make package' and Poudriere. Roger ___ 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 This is actually a side effect of the STAGING implementation. The package file is put into the port (created) work sub directory. Now if I could only find the documentation that tells me how to put, say, WORK_DIRECTORY=/var/tmp/work into the /etc/make.conf file or something similar I would be a very (well, not so grumpy) happy camper. I read this somewhere once but I cannot find it again. WRKDIRPREFIX? WORKDIRPREFIX? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ 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: BIND REPLACE_BASE option
On 01/12/15 11:46, Chris H wrote: My main complaint with pkg is the persistent misunderstanding that binary packages are a direct replacement for ports. http://www.wonkity.com/~wblock/docs/html/pkg.html I'd be inclined to agree here. There are some ports that almost demand a local version - apr (Apache Portability Library) being one of them. Currently, I am locking 'apr' so that pkg upgrade does not clobber apr, and this has worked so far. Just an observation. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com ___ 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: linux-c6-flashplugin11 fetch error
On 11/11/14 08:00, Dave wrote: On Tuesday 11 November 2014 17:07:57 Johannes Meixner wrote: Hi Dave, I've updated the Flash versions to 11.2r202.418 in revision 372450 given Adobe had taken down the old 406 version. Please update your portstree and see if that solves your issues. Best, -xmj Yes thanks, that did it. I'd already updated the ports tree via portsnap earlier today and again just before doing the build but I guess I just got caught in the window between ports being updated and the portsnap server catching up. ___ 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 I filed a bug report for a missing 'pixmap' library. This port update is now fetching all of the needed libraries. Thanks for your work! ___ 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
Suggestion on how to add search order to multiple reponsitories
Currently there does not appear to be simple way to specify the
order that repositories searched for packages, or at least there
is none documented as such that I can find.
Suppose we add a 'repo_order' field to the repository specification, i.e. -
FreeBSDMyStuff: {
URL: http://myserver/${ABI}/latest
ENABLED: yes
MIRROR_TYPE: SRV
repo_order: 1
}
FreeBSD: {
URL: http://pkg.freebsd.org/${ABI}/latest
ENABLED: yes
MIRROR_TYPE: SRV
repo_order: 2
}
When doing a search for packages, the found/discovered packages
would be sorted by the value of the order field. By default, if
there is no value for the order field then this entry would come
last. If there are two entries with no or the same order value
then they would be sorted on the repo name, as is currently done.
Also, when displaying repositories, i.e. - pkg -v -v, you would
sort the display entries by the repo_order field as well.
Just to jumpstart this effort I am attaching a set of patches for
pkg-1.4.0.pre-alpha15. This implements the basic functionality to
add repo_order to the repository definitions and adds support to
display the repo_order when doing 'pkg search'.
I would happy to add this ordering functionality to other parts of
the pkg support, but I need a bit of help with the current code.
From my understanding/reading/crystal ball gazing/looking at the
code entrails, it appears that when doing a 'pkg install X' the X
is first used to determine the set of packages in question. Once
these have been determined there is a rather intimidating (recursive
as well?) procedure which is used to determine any dependencies.
Somewhere in this process there is a place where the listed/named
repositories are searched for candidates for dependencies. It
appears at a casual reading that the repositories are searched in
the reverse order they were put in the reponsitory list and candidates
found during the search are then added to the dependency list as
they are found. This has the effect of having entries found in
earlier listed repositories overwrite those found in later listed
respositories (I thought this was VERY clever!).
Rather than modify this code, I would suggest adding a 'repository
ordering' step or routine. Just after the repositories are
found/listed, the repository list should be sorted (stably) using
the name and the repo_order field. That is, all of the repositories
with a lower repo_order value would be moved ahead of those with
lower repo_order values, while preserving the order for those with
the same repo_order value.
If this is done and the algorithm for searching the repositories
is as I have outlined it, then you should get the desired repository
priority effect. And perhaps no other code changes would be required.
I hope. Perhaps. Maybe.
*** pkg-1.4.0.pre-alpha15/docs/pkg_printf.3 Mon Sep 15 13:18:26 2014
--- pkg-1.4.0.pre-alpha15.orig/docs/pkg_printf.3Sun Jun 8 12:59:52 2014
***
*** 644,655
Valid only during operations when one version of a package is being
replaced by another.
.Vt struct pkg *
- .It Cm %Z
- Repository Order (repo_order) [integer] value.
- Value is set in the repository information and is limited to 0-100 (default
100).
- When selecting packages for installation, repositories with lower order
numbers
- are searched before packages with higher order numbers.
- .Vt struct pkg *
.It Cm %a
Autoremove flag [boolean]
.Vt struct pkg *
--- 644,649
*** pkg-1.4.0.pre-alpha15/docs/pkg.conf.5 Mon Sep 15 13:33:02 2014
--- pkg-1.4.0.pre-alpha15.orig/docs/pkg.conf.5 Sun Sep 14 15:11:40 2014
***
*** 271,279
.Va hw.ncpu
is used.
Default: 0.
- .It Cm REPO_ORDER: integer [1-100, default 100]
- Repositories with lower repo_order values are examined before reponsitories
with
- larger repo_order values.
.El
.Sh REPOSITORY CONFIGURATION
To use a repository you will need at least one repository
--- 271,276
***
*** 422,438
.Sy REPOS_DIR
search path, with individual repository configuration files in the
same directory processed in alphabetical order.
! This search order is modified by the
! .Sy repo_order
! value; repositories with smaller
! .Sy repo_order
! values are searched befor repositories with larger
! .Sy repo_order
! values.
! Packages found earlier in the search order take precedence,
! meaning that
! if the same package is available from several repositories
! the first one found in the search order will be used.
This behaviour may be overridden per-package by adding a
.Sy repository
annotation to the installed package.
--- 419,427
.Sy REPOS_DIR
search path, with individual repository configuration files in the
same directory processed in alphabetical order.
! Earlier files take precedence, meaning that packages will be downloaded
! from them preferentially where the same package is available from several
! repositories.
This behaviour may be
Re: FreeBSD Port: x11-servers/xorg-server
On 09/22/14 23:50, Kevin Oberman wrote: On Mon, Sep 22, 2014 at 9:19 PM, William A. Mahaffey III w...@hiwaay.net wrote: On 09/22/14 16:38, Patrick Powell wrote: On 09/21/14 16:52, William A. Mahaffey III wrote: On 09/21/14 18:12, Robert_Burmeister wrote: William A. Mahaffey III wrote On 09/21/14 11:41, Robert_Burmeister wrote: On 13.09.2014 22:10, Robert Burmeister wrote: FreeBSD 10.1 i386 xorg-server 1.12.4_9,1 and 1.12.4_1,1 Still don't have mouse support after upgrade from 1.12.4_8,1 [ 1786.822] (EE) Failed to load module mouse (module does not exist, 0) Have you installed x11-drivers/xf86-input-mouse? [ 1786.825] (EE) Failed to load module kbd (module does not exist, 0) And x11-drivers/xf86-input-keyboard? ___ Installing x11-drivers/xf86-input-mouse and x11-drivers/xf86-input-keyboard fixed the problem, however, I don't understand why upgrading from xorg-server 1.12.4_8,1 to xorg-server 1.12.4_9,1 would require new drivers, or lose the ones it had. I would think these drivers would/should be a dependency for xorg-server in the Ports system... ___ I have had that same problem verbatim the last 2 x-server upgrades I did, that was the fix, (re?)install the kbd mouse drivers. I (pkg-)upgraded this A.M., no such issues -- Even more interesting... x11-drivers/xf86-input-mouse and x11-drivers/xf86-input-keyboard have xorg-server as a dependency, and so cannot be a circular dependency. I'm guessing that the mouse and keyboard drivers got deleted as dependents of xorg-server during the upgrade, but there are no dependencies in my desktop build process that require that they be put back, even through a complete system recompile. I'm thinking 'x11-drivers/xorg-drivers' and 'x11/xorg-minimal' should be bumped when xorg-server is upgraded. (When my current recompile is done, I will check that my xorg-drivers didn't get removed as well.) I am using pkg, no ports, no recompiling FBSD 9.3, BTW Just a thought - check to make sure that the x11-drivers/xf86-input-keyboard port on the PKGng server you are using was actually rebuilt for the new version of xorg-server. I had this problem a couple of weeks ago and the X log file hinted that the keyboard driver was not compatible with the version of xorg-server. At the time I thought that this was due to a lag in the PKGng server building the new drivers so I compiled and installed the x11-drivers/xf86-input-keyboard. The problem went away. This appears to be the same sort of issue. Perhaps the driver(s) are not getting rebuilt for the new version of xorg-server? Or perhaps this is related to packages on the 'with_new_xorg' PKGng server versus packages on the standard PKGng server? ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-x11 To unsubscribe, send any mail to freebsd-x11-unsubscr...@freebsd.org Would that (drivers not getting rebuilt right) be a pkg problem or an X11 problem (or something else) ? Just checking -- William A. Mahaffey III It's a ports issue. The ports system (which is used by pkg) depends on incrementing version numbers to tell when a port has been updated and needs to be rebuilt or when a port needs updating because a dependency has been updated in a way that affects the port. The former is typically the result of a change to a port that changes hte version number. The later is a bump of the PORT_REVISION to indicate to the ports system that some change that did not come from a change upstream, but local to FreeBSD requires a port rebuild. In this case, it does not work. The actual version number has not changed as the upstream version has not changed. PORT_REVISION would result in the ports being rebuilt, but that does not play with the definition of WITH_NEW_XORG. I somehow needs to be bumped when any system sets WITH_NEW_XORG and I don't see any way in hte current structure to do this. It is the result of having two parallel ports trees. One possible fix is to have code in the Makefile to check WITH_NEW_XORG and, if it is defined, use a different PORT_REVISION. If the old Xorg driver gets a bump of PORT_REVESION, the new one would, as well, but I don't see any reason this could not be done as both numbers are in the same Makefile and should be only a few lines apart. something like: . if defined(WITH_NEW_XORG) PORT_REVISION=2 . else PORT_REVISION=1 . endif This may break the index, so I'm not sure it would work as simply as this, but I bet it could be made to work, -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-x11 To unsubscribe, send any mail to freebsd-x11
Re: Switching from building ports to packages
On 09/14/14 20:09, Chad J. Milios wrote:
On 09/14/14 16:34, Matt Reimer wrote:
I'd like to switch from building everything from source using ports to
using packages as much as possible. This requires identifying which
ports
I'm currently building use the same port knobs as the binary packages
that
FreeBSD builds. Is there an easy way of showing how my port configs
differ
from the defaults that are used to build binary packages?
Thanks in advance.
Matt
this script below will do exactly that from the port building machine
if you built them all in one place. (it gathers from
/var/db/ports/*/options but does not mine the data from
/var/db/pkg/local.sqlite.) if you'd like to extract options out of
your installed binary pkg ng's or pkg_og's or dir of .txz's or .tbz's
laying around somewhere and compare those to the current ports tree,
let me know. it's slightly more difficult but not terrible.
in case of mail munging and for your convenience this script is posted
to https://cargobay.net/LpYDhX3U with SHA256 (LpYDhX3U) =
4ef3dae564d861fd32efad267bb3e360a498d4688bb86fca7e2a0a195e58a34f
#!/bin/sh
_=/dev/null
cd /usr/ports
_a=PORT_DBDIR=/var/empty
for p in /var/db/ports/*; do
p=${p#/*/*/*/}
c=${p%%_*}
d=${p#*_}
if cd $c/$d; then
for z in a b; do
eval make \$_$z showconfig 2$_ /tmp/$$.$z
done
if ! diff /tmp/$$.[ab] $_; then
echo $c/$d
diff /tmp/$$.[ab] | grep ^ | cut -c 2-
fi
cd ../..
fi
done
rm /tmp/$$.[ab]
___
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
Ahh!!! Thank you.
Just to get this on record and to be able to search and find it - could
you post the script that does the check against the pkgng database?
If you are downloading the packages from the 'standard' FreeBSD package
repository it would be useful to be able to see what options they built
the packages with.
___
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: Any update planned for www/mod_log_sql2
On 09/06/14 02:05, Simon Wright wrote: Hi Team! I was wondering whether mod_log_sql2 will be or can be updated to work with the new default of Apache24? Apache22 is specified explictly in the Makefile. I'm not sure whether mod_log_mysql is a replacement/substitute but that is also linked explicitly to Apache22. An indication of any time line or migration path would be much appreciated! Many thanks. Simon Wright. ___ 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 I had a quick look at this (Note: I am NOT an Apache module expert, but I have updated a couple of them that I needed). The source code for the module needs to be updated to match Apache 2.4. There are more than a few trivial changes here. I you feel brave, look at: http://httpd.apache.org/docs/trunk/developer/new_api_2_4.html and http://httpd.apache.org/docs/2.4/developer/modguide.html and http://httpd.apache.org/docs/current/mod/mod_example.html ___ 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: Does pkg automatically download INDEX?
On 08/09/14 18:15, Naram Qashat wrote: On 08/09/14 19:45, Scot Hetzel wrote: On Fri, Aug 8, 2014 at 7:00 PM, Naram Qashat cyberb...@cyberbotx.com wrote: On 08/04/14 07:28, David Wolfskill wrote: On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote: On 08/03/14 22:14, David Wolfskill wrote: On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote: ... If there is a way to find out when any process is attempting to modify a file, that would probably help me narrow it down, but I'm not aware of anything that can do that, ... Well, chflags schg /usr/ports/INDEX* would *prevent* the modification ... This was a really good suggestion. Glad to help. :-) Peace, david OK, so while no programs have whined or complained, I get the feeling that something on my system is running portsnap without my knowledge. When I had set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg flag on that as well, and now I notice there are a bunch of files called .fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a file called .portsnap.INDEX. As far as I know, I don't have anything configured to run portsnap, but is there something that defaults to running portsnap occasionally? I couldn't find anything that would do that. Do your have a crontab entry that is running portsnap with the -I (update INDEX) option? http://www.pl.freebsd.org/doc/handbook/portsnap.html As far as I can tell, no, none of my crontabs have any references to portsnap in them. This is making me a bit stumped as to why it would be happening. I checked the main /etc/crontab, I checked the crontabs in /var/cron/tabs. I have searched inside of /etc and /usr/local/etc for anything related to portsnap. Nothing that would be doing this is coming up at all. Thanks, Naram Qashat ___ 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 I ran into something similar once, and found out what was happening this way. 1. replace the portsnap executable with a shell script. Rename portsnap to something like /usr/sbin/portsnap.orig 2. This shell script should dump the current ENV and other stuff to a log file. Don't forget to put in a timestamp. And then do: exec /usr/sbin/portsnap.orig $* I did this and found that there was something in one of the .login scripts. G... ___ 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: Apache 24 + mod_perl
Hmmm... well, it looks like you need to update the procedures from RedHat which build the mod_perl. I don't think you can build a FreeBSD port on a Linux system, although stranger things have happened. On 08/06/14 19:43, Jie Gao wrote: The patch, or rather the patching itself, does not work with a box of Red Hat Enterprise Linux Server release 6.5 for me here. Regards, Jie * Patrick Powell papow...@astart.com wrote: Date: Wed, 6 Aug 2014 17:27:15 -0700 From: Patrick Powell papow...@astart.com To: olli hauer oha...@gmx.de CC: Steve Hay steve.m@googlemail.com, Kurt Jaeger li...@opsec.eu, po...@freebsd.org, modp...@perl.apache.org modp...@perl.apache.org Subject: Re: Apache 24 + mod_perl User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130714 Thunderbird/17.0.7 On 08/06/14 14:34, olli hauer wrote: On 2014-08-06 22:45, Patrick Powell wrote: On 08/06/14 00:19, Steve Hay wrote: On 3 August 2014 22:13, Patrick Powell papow...@astart.com wrote: On 08/03/14 08:25, olli hauer wrote: On 2014-08-01 23:34, Kurt Jaeger wrote: Hi! Question: when will mod_perl be available for Apache 24? There's a PR where people are discussing this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471 This PR needs more testers etc. I've updated the PR with a patch against the latest mod_perl trunk revision (r1602105). The patch against the port can be grabbed from here or from our bugzilla http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff Please test *at own risk*, and report issues to upstream and here so we can integrate fresh upstream fixes and update the port. The first proposed patch will allows the port to build but I have to many concerns for integrating this simple fix into the tree. I don't believe the first patch on the PR will work right else it would take the upstream dev. work and time for mod_perl2 at absurdI -um ... I have taken a slightly different approach, using the mod_perl2 SVN /httpd24 branch as the starting point. The httpd24 branch is obselete. It was used for the initial development of httpd-2.4 support, but was superseded by httpd24threading, and since then everything from both branches has been merged back to trunk. The current trunk is largely ready for a 2.0.9 release supporting httpd-2.4, pending some more testing and fixes as necessary. I tried using the trunk a couple of days ago and it did not compile. Just to make sure that I am using the right SVN respository and branch, what is the URL of the trunk SVN repository? I am more than happy to try testing mod_perl. Hm, with the following patch applied to www/mod_perl2 it builds fine for me on FreeBSD 8.4 / 10.0 (amd64) an apache-2.4.10 http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff The patch does some adjustments in the port / pkg-plist and fetches a complete archive containing all patches so the sources are the same as the upstream (r1602105) trunk/httpd24threade branch. After applying the patch and using the command `make patch' it is easy to compare the sources against upstream sources (check out before) http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24threading http://svn.apache.org/repos/asf/perl/modperl/trunk Easiest way to apply the patch against the unmodified port: $ cd www/mod_perl2 $ fetch http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff $ patch -p1 mod_perl2-2.0.8_apache24.diff PS: I've updated the patch because it needs some additional handling for pkg-plist if build against apache-2.2.x (Provider.pm/Provider.so) I tried your procedure (see above). The patch applied, I was able to compile the mod_perl, and 'make test' ran and it passed all of the critical tests. I then ran some more of my tests for the functionality it used. These passed. I would say that unless somebody else comes up with a problem that I would use this as a baseline for distribution/installation. That is, I would put up the modified Makefile, with a warning, but would allow people to make/install it by specifying an option such as make IGNORE_WARNING=yes Of course, the FreeBSD Ports team may have different views on this... but until the upstream mod_perl team puts out mod_perl-2.0.9 officially I think that this is the best we can do. Also, some more testers will be able to try it out and report any problems ___ 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 1.3.5.1 - Assertion failed
I am setting up a new system which needs KDE. Note that
I set up a similar system a couple of weeks ago using the new_xorg
repository and the installation worked fine (OK, as well
as an installation on a new OS, new system, new Video Card,
and a set of new applications works). When I try to repeat
this I now get following error:
# pkg install x11/kde4
Updating repository catalogue
FreeBSD repository is up-to-date
FreeBSD_new_xorg repository is up-to-date
All repositories are up-to-date
Assertion failed: (var == elt-var), function pkg_solve_sat_problem,
file pkg_solv
e.c, line 508.
Child process pid=1384 terminated abnormally: Abort trap: 6
Setup: FreeBSD 9.3-Release, amd 64
pkg: pkg-1.3.5.1
Repositories:
/etc/pkg/FreeBSD.conf:
# $FreeBSD: releng/9.3/etc/pkg/FreeBSD.conf 263939 2014-03-30 15:30:33Z
bdrewery $
#
# To disable this repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo FreeBSD: { enabled: no } /usr/local/etc/pkg/repos/FreeBSD.conf
#
FreeBSD: {
url: pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
mirror_type: srv,
signature_type: fingerprints,
fingerprints: /usr/share/keys/pkg,
enabled: yes
}
/usr/local/etc/pkg/repos/FreeBSD.conf:
FreeBSD: {
url: pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
mirror_type: srv,
enabled: yes
}
/usr/local/etc/pkg/repos/FreeBSD_new_xort.conf:
# /usr/local/etc/pkg/repos/FreeBSD_new_xorg.conf
# It is still required to have /etc/pkg/FreeBSD.conf installed and enabled.
# If that file is missing or if /usr/share/keys/pkg is missing see:
# http://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc
FreeBSD_new_xorg: {
url: pkg+http://pkg.FreeBSD.org/${ABI}/new_xorg;,
mirror_type: srv,
signature_type: fingerprints,
fingerprints: /usr/share/keys/pkg,
enabled: yes
}
___
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: Apache 24 + mod_perl
On 08/06/14 00:19, Steve Hay wrote: On 3 August 2014 22:13, Patrick Powell papow...@astart.com wrote: On 08/03/14 08:25, olli hauer wrote: On 2014-08-01 23:34, Kurt Jaeger wrote: Hi! Question: when will mod_perl be available for Apache 24? There's a PR where people are discussing this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471 This PR needs more testers etc. I've updated the PR with a patch against the latest mod_perl trunk revision (r1602105). The patch against the port can be grabbed from here or from our bugzilla http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff Please test *at own risk*, and report issues to upstream and here so we can integrate fresh upstream fixes and update the port. The first proposed patch will allows the port to build but I have to many concerns for integrating this simple fix into the tree. I don't believe the first patch on the PR will work right else it would take the upstream dev. work and time for mod_perl2 at absurdI -um ... I have taken a slightly different approach, using the mod_perl2 SVN /httpd24 branch as the starting point. The httpd24 branch is obselete. It was used for the initial development of httpd-2.4 support, but was superseded by httpd24threading, and since then everything from both branches has been merged back to trunk. The current trunk is largely ready for a 2.0.9 release supporting httpd-2.4, pending some more testing and fixes as necessary. I tried using the trunk a couple of days ago and it did not compile. Just to make sure that I am using the right SVN respository and branch, what is the URL of the trunk SVN repository? I am more than happy to try testing mod_perl. ___ 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: Apache 24 + mod_perl
On 08/06/14 14:34, olli hauer wrote: On 2014-08-06 22:45, Patrick Powell wrote: On 08/06/14 00:19, Steve Hay wrote: On 3 August 2014 22:13, Patrick Powell papow...@astart.com wrote: On 08/03/14 08:25, olli hauer wrote: On 2014-08-01 23:34, Kurt Jaeger wrote: Hi! Question: when will mod_perl be available for Apache 24? There's a PR where people are discussing this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471 This PR needs more testers etc. I've updated the PR with a patch against the latest mod_perl trunk revision (r1602105). The patch against the port can be grabbed from here or from our bugzilla http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff Please test *at own risk*, and report issues to upstream and here so we can integrate fresh upstream fixes and update the port. The first proposed patch will allows the port to build but I have to many concerns for integrating this simple fix into the tree. I don't believe the first patch on the PR will work right else it would take the upstream dev. work and time for mod_perl2 at absurdI -um ... I have taken a slightly different approach, using the mod_perl2 SVN /httpd24 branch as the starting point. The httpd24 branch is obselete. It was used for the initial development of httpd-2.4 support, but was superseded by httpd24threading, and since then everything from both branches has been merged back to trunk. The current trunk is largely ready for a 2.0.9 release supporting httpd-2.4, pending some more testing and fixes as necessary. I tried using the trunk a couple of days ago and it did not compile. Just to make sure that I am using the right SVN respository and branch, what is the URL of the trunk SVN repository? I am more than happy to try testing mod_perl. Hm, with the following patch applied to www/mod_perl2 it builds fine for me on FreeBSD 8.4 / 10.0 (amd64) an apache-2.4.10 http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff The patch does some adjustments in the port / pkg-plist and fetches a complete archive containing all patches so the sources are the same as the upstream (r1602105) trunk/httpd24threade branch. After applying the patch and using the command `make patch' it is easy to compare the sources against upstream sources (check out before) http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24threading http://svn.apache.org/repos/asf/perl/modperl/trunk Easiest way to apply the patch against the unmodified port: $ cd www/mod_perl2 $ fetch http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff $ patch -p1 mod_perl2-2.0.8_apache24.diff PS: I've updated the patch because it needs some additional handling for pkg-plist if build against apache-2.2.x (Provider.pm/Provider.so) I tried your procedure (see above). The patch applied, I was able to compile the mod_perl, and 'make test' ran and it passed all of the critical tests. I then ran some more of my tests for the functionality it used. These passed. I would say that unless somebody else comes up with a problem that I would use this as a baseline for distribution/installation. That is, I would put up the modified Makefile, with a warning, but would allow people to make/install it by specifying an option such as make IGNORE_WARNING=yes Of course, the FreeBSD Ports team may have different views on this... but until the upstream mod_perl team puts out mod_perl-2.0.9 officially I think that this is the best we can do. Also, some more testers will be able to try it out and report any problems ___ 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: Apache 24 + mod_perl
OK, here are the results of my initial tests. See ++ TEST ++ at
the end of these notes for the results
Sun Aug 3 07:01:46 PDT 2014
I started with FreeBSD 93, perl5.16
test94: {90} # uname -a
FreeBSD test94.private 9.3-RELEASE FreeBSD 9.3-RELEASE #0 r268512:
Thu Jul 10 23:44:39 UTC 2014
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
test94: {92} # perl -v
This is perl 5, version 16, subversion 3 (v5.16.3) built for
amd64-freebsd-thread-multi
test94: {93} # pkg info perl5
perl5-5.16.3_11
Name : perl5
Version: 5.16.3_11
Installed on : Tue Jul 29 07:04:39 PDT 2014
Origin : lang/perl5.16
Architecture : freebsd:9:x86:64
Prefix : /usr/local
Categories : perl5 lang devel
Licenses : GPLv1 or ART10
Maintainer : p...@freebsd.org
WWW: http://www.perl.org/
Comment: Practical Extraction and Report Language
Options:
DEBUG : off
GDBM : off
MULTIPLICITY : off
PERL_64BITINT : on
PERL_MALLOC: off
PTHREAD: on
SITECUSTOMIZE : off
THREADS: on
USE_PERL : on
Shared Libs required:
libperl.so
Annotations:
cpe: cpe:/a:perl:perl:5.16.3::~~~freebsd~~
Flat size : 47.4MiB
Description:
Perl is a language that combines some of the features of C, sed, awk and
shell. See the manual page for more hype. There are also many books
published by O'Reilly Assoc. See pod/perlbook.pod for more
information.
***
Now read the article:
https://forums.freebsd.org/viewtopic.php?f=5t=46523. We are
going to do some of the steps, with minor modifications.
1. Install apache24
# cd /usr/ports/www/apache24
# make install
OR
pkg install apache24
2. Start to install mod_perl2, fetch the source code:
# cd /usr/ports/www/mod_perl2
# make fetch
This will fetch mod_perl-2.0.8.tar.gz and put it in /usr/ports/distfiles
Now untar mod_perl-2.0.8.tar.gz
# cd /usr/ports/distfiles
# tar xvf mod_perl-2.0.8.tar.gz
3. We will create a dummy mod_perl-2.0.9 distribution file. We
will need the Apache-Reload, Apache-SizeLimit, and Apache-Test
Perl Modules from mod_perl-2.0.8 , which are not in the SVN
distribution we are going to fetch, but are in the mod_perl-2.0.8
distribution. Note that these appear to be the latest versions;
if in doubt check the Apache Web site.
# mkdir mod_perl-2.0.9
# tar cf - -C mod_perl-2.0.8 Apache-Reload Apache-SizeLimit
Apache-Test | tar xvf - -C mod_perl-2.0.9
4. Now get the latest http24 branch from the Apache Mod_perl SVN repository:
You may need to install wget:
# pkg install wget
# wget --no-parent -r
http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24/
This will create a
svn.apache.org/repos/asf/perl/modperl/branches/httpd24 directory.
Now we copy these files to the mod_perl-2.0.9 directory:
# tar cf - -C
svn.apache.org/repos/asf/perl/modperl/branches/httpd24 . | tar xvf - -C
mod_perl-2.0.9
# ls mod_perl-2.0.9
Apache-Reload LICENSE README
bin t
Apache-SizeLimitMETA.yml README-SVN
build todo
Apache-Test Makefile.PL RELEASE
index.html util
BRANCHING Makefile.old STATUS
lib xs
Changes ModPerl-Registry SVN-MOVEpatches
INSTALL NOTICE WrapXS src
5. Create a tar file of mod_perl-2.0.9
# tar cfz mod_perl-2.0.9.tar.gz mod_perl-2.0.9
6. Now we modify the www/mod_perl2 port
# cd /usr/ports/www/mod_perl2
Edit Makefile, and make the following changes:
a) we set PORTVERSION to 2.0.9
b) we set USET_APACHE to 22+
c) remove the 'Broken' warning
*** 2,8
# $FreeBSD: head/www/mod_perl2/Makefile 362013 2014-07-15
22:14:23Z ohauer $
PORTNAME= mod_perl
! PORTVERSION= 2.0.8
PORTREVISION= 1
PORTEPOCH=3
CATEGORIES= www perl5
--- 2,8
# $FreeBSD: head/www/mod_perl2/Makefile 362013 2014-07-15
22:14:23Z ohauer $
PORTNAME= mod_perl
! PORTVERSION= 2.0.9
PORTREVISION= 1
PORTEPOCH=3
CATEGORIES= www perl5
***
*** 18,34
SUB_FILES=pkg-message
SUB_LIST= APACHEMODDIR=${APACHEMODDIR}
! USE_APACHE= 22
USES= gmake perl5
USE_PERL5=configure
USE_CSTD= gnu89
.include bsd.port.pre.mk
- .if ${APACHE_VERSION} 22
- BROKEN= Does not build with apache24
- .endif
-
# Using apxs in this way is problematic if apache2 is installed
under a
# different PREFIX than mod_perl2, because the mod_perl2
installation will
# use paths returned by apxs to install some components. Fixes
welcome.
Re: Apache 24 + mod_perl
Here are the build.log and test.log files mentioned in this posting
On 08/03/14 07:09, Patrick Powell wrote:
OK, here are the results of my initial tests. See ++ TEST ++ at
the end of these notes for the results
Sun Aug 3 07:01:46 PDT 2014
I started with FreeBSD 93, perl5.16
test94: {90} # uname -a
FreeBSD test94.private 9.3-RELEASE FreeBSD 9.3-RELEASE #0 r268512:
Thu Jul 10 23:44:39 UTC 2014
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
test94: {92} # perl -v
This is perl 5, version 16, subversion 3 (v5.16.3) built for
amd64-freebsd-thread-multi
test94: {93} # pkg info perl5
perl5-5.16.3_11
Name : perl5
Version: 5.16.3_11
Installed on : Tue Jul 29 07:04:39 PDT 2014
Origin : lang/perl5.16
Architecture : freebsd:9:x86:64
Prefix : /usr/local
Categories : perl5 lang devel
Licenses : GPLv1 or ART10
Maintainer : p...@freebsd.org
WWW: http://www.perl.org/
Comment: Practical Extraction and Report Language
Options:
DEBUG : off
GDBM : off
MULTIPLICITY : off
PERL_64BITINT : on
PERL_MALLOC: off
PTHREAD: on
SITECUSTOMIZE : off
THREADS: on
USE_PERL : on
Shared Libs required:
libperl.so
Annotations:
cpe: cpe:/a:perl:perl:5.16.3::~~~freebsd~~
Flat size : 47.4MiB
Description:
Perl is a language that combines some of the features of C, sed, awk and
shell. See the manual page for more hype. There are also many books
published by O'Reilly Assoc. See pod/perlbook.pod for more
information.
***
Now read the article:
https://forums.freebsd.org/viewtopic.php?f=5t=46523. We are
going to do some of the steps, with minor modifications.
1. Install apache24
# cd /usr/ports/www/apache24
# make install
OR
pkg install apache24
2. Start to install mod_perl2, fetch the source code:
# cd /usr/ports/www/mod_perl2
# make fetch
This will fetch mod_perl-2.0.8.tar.gz and put it in
/usr/ports/distfiles
Now untar mod_perl-2.0.8.tar.gz
# cd /usr/ports/distfiles
# tar xvf mod_perl-2.0.8.tar.gz
3. We will create a dummy mod_perl-2.0.9 distribution file. We
will need the Apache-Reload, Apache-SizeLimit, and Apache-Test
Perl Modules from mod_perl-2.0.8 , which are not in the SVN
distribution we are going to fetch, but are in the mod_perl-2.0.8
distribution. Note that these appear to be the latest versions;
if in doubt check the Apache Web site.
# mkdir mod_perl-2.0.9
# tar cf - -C mod_perl-2.0.8 Apache-Reload Apache-SizeLimit
Apache-Test | tar xvf - -C mod_perl-2.0.9
4. Now get the latest http24 branch from the Apache Mod_perl SVN
repository:
You may need to install wget:
# pkg install wget
# wget --no-parent -r
http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24/
This will create a
svn.apache.org/repos/asf/perl/modperl/branches/httpd24 directory.
Now we copy these files to the mod_perl-2.0.9 directory:
# tar cf - -C
svn.apache.org/repos/asf/perl/modperl/branches/httpd24 . | tar xvf -
-C mod_perl-2.0.9
# ls mod_perl-2.0.9
Apache-Reload LICENSE README bin t
Apache-SizeLimitMETA.yml README-SVN build
todo
Apache-Test Makefile.PL RELEASE index.html
util
BRANCHING Makefile.old STATUS lib xs
Changes ModPerl-Registry SVN-MOVE
patches
INSTALL NOTICE WrapXS src
5. Create a tar file of mod_perl-2.0.9
# tar cfz mod_perl-2.0.9.tar.gz mod_perl-2.0.9
6. Now we modify the www/mod_perl2 port
# cd /usr/ports/www/mod_perl2
Edit Makefile, and make the following changes:
a) we set PORTVERSION to 2.0.9
b) we set USET_APACHE to 22+
c) remove the 'Broken' warning
*** 2,8
# $FreeBSD: head/www/mod_perl2/Makefile 362013 2014-07-15
22:14:23Z ohauer $
PORTNAME= mod_perl
! PORTVERSION= 2.0.8
PORTREVISION= 1
PORTEPOCH=3
CATEGORIES= www perl5
--- 2,8
# $FreeBSD: head/www/mod_perl2/Makefile 362013 2014-07-15
22:14:23Z ohauer $
PORTNAME= mod_perl
! PORTVERSION= 2.0.9
PORTREVISION= 1
PORTEPOCH=3
CATEGORIES= www perl5
***
*** 18,34
SUB_FILES=pkg-message
SUB_LIST= APACHEMODDIR=${APACHEMODDIR}
! USE_APACHE= 22
USES= gmake perl5
USE_PERL5=configure
USE_CSTD= gnu89
.include bsd.port.pre.mk
- .if ${APACHE_VERSION} 22
- BROKEN= Does not build with apache24
- .endif
-
# Using apxs in this way is problematic if apache2 is installed
under a
# different PREFIX than mod_perl2, because the mod_perl2
installation will
# use paths returned
Re: Apache 24 + mod_perl
Looks like either the attachments are too large or they do not have an
acceptable mime-type
as described in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handboohttp://www.freebsd.org
On 08/03/14 07:16, Patrick Powell wrote:
Here are the build.log and test.log files mentioned in this posting
On 08/03/14 07:09, Patrick Powell wrote:
OK, here are the results of my initial tests. See ++ TEST ++ at
the end of these notes for the results
Sun Aug 3 07:01:46 PDT 2014
I started with FreeBSD 93, perl5.16
test94: {90} # uname -a
FreeBSD test94.private 9.3-RELEASE FreeBSD 9.3-RELEASE #0 r268512:
Thu Jul 10 23:44:39 UTC 2014
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
test94: {92} # perl -v
This is perl 5, version 16, subversion 3 (v5.16.3) built for
amd64-freebsd-thread-multi
test94: {93} # pkg info perl5
perl5-5.16.3_11
Name : perl5
Version: 5.16.3_11
Installed on : Tue Jul 29 07:04:39 PDT 2014
Origin : lang/perl5.16
Architecture : freebsd:9:x86:64
Prefix : /usr/local
Categories : perl5 lang devel
Licenses : GPLv1 or ART10
Maintainer : p...@freebsd.org
WWW: http://www.perl.org/
Comment: Practical Extraction and Report Language
Options:
DEBUG : off
GDBM : off
MULTIPLICITY : off
PERL_64BITINT : on
PERL_MALLOC: off
PTHREAD: on
SITECUSTOMIZE : off
THREADS: on
USE_PERL : on
Shared Libs required:
libperl.so
Annotations:
cpe: cpe:/a:perl:perl:5.16.3::~~~freebsd~~
Flat size : 47.4MiB
Description:
Perl is a language that combines some of the features of C, sed, awk and
shell. See the manual page for more hype. There are also many books
published by O'Reilly Assoc. See pod/perlbook.pod for more
information.
***
Now read the article:
https://forums.freebsd.org/viewtopic.php?f=5t=46523. We are
going to do some of the steps, with minor modifications.
1. Install apache24
# cd /usr/ports/www/apache24
# make install
OR
pkg install apache24
2. Start to install mod_perl2, fetch the source code:
# cd /usr/ports/www/mod_perl2
# make fetch
This will fetch mod_perl-2.0.8.tar.gz and put it in
/usr/ports/distfiles
Now untar mod_perl-2.0.8.tar.gz
# cd /usr/ports/distfiles
# tar xvf mod_perl-2.0.8.tar.gz
3. We will create a dummy mod_perl-2.0.9 distribution file. We
will need the Apache-Reload, Apache-SizeLimit, and Apache-Test
Perl Modules from mod_perl-2.0.8 , which are not in the SVN
distribution we are going to fetch, but are in the mod_perl-2.0.8
distribution. Note that these appear to be the latest versions;
if in doubt check the Apache Web site.
# mkdir mod_perl-2.0.9
# tar cf - -C mod_perl-2.0.8 Apache-Reload Apache-SizeLimit
Apache-Test | tar xvf - -C mod_perl-2.0.9
4. Now get the latest http24 branch from the Apache Mod_perl SVN
repository:
You may need to install wget:
# pkg install wget
# wget --no-parent -r
http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24/
This will create a
svn.apache.org/repos/asf/perl/modperl/branches/httpd24 directory.
Now we copy these files to the mod_perl-2.0.9 directory:
# tar cf - -C
svn.apache.org/repos/asf/perl/modperl/branches/httpd24 . | tar xvf -
-C mod_perl-2.0.9
# ls mod_perl-2.0.9
Apache-Reload LICENSE README bin t
Apache-SizeLimitMETA.yml README-SVN
build todo
Apache-Test Makefile.PL RELEASE
index.html util
BRANCHING Makefile.old STATUS
lib xs
Changes ModPerl-Registry SVN-MOVE
patches
INSTALL NOTICE WrapXS src
5. Create a tar file of mod_perl-2.0.9
# tar cfz mod_perl-2.0.9.tar.gz mod_perl-2.0.9
6. Now we modify the www/mod_perl2 port
# cd /usr/ports/www/mod_perl2
Edit Makefile, and make the following changes:
a) we set PORTVERSION to 2.0.9
b) we set USET_APACHE to 22+
c) remove the 'Broken' warning
*** 2,8
# $FreeBSD: head/www/mod_perl2/Makefile 362013 2014-07-15
22:14:23Z ohauer $
PORTNAME= mod_perl
! PORTVERSION= 2.0.8
PORTREVISION= 1
PORTEPOCH=3
CATEGORIES= www perl5
--- 2,8
# $FreeBSD: head/www/mod_perl2/Makefile 362013 2014-07-15
22:14:23Z ohauer $
PORTNAME= mod_perl
! PORTVERSION= 2.0.9
PORTREVISION= 1
PORTEPOCH=3
CATEGORIES= www perl5
***
*** 18,34
SUB_FILES=pkg-message
SUB_LIST= APACHEMODDIR=${APACHEMODDIR}
! USE_APACHE= 22
USES= gmake perl5
USE_PERL5=configure
USE_CSTD= gnu89
.include bsd.port.pre.mk
- .if ${APACHE_VERSION} 22
- BROKEN= Does
Re: Apache 24 + mod_perl
On 08/03/14 08:25, olli hauer wrote: On 2014-08-01 23:34, Kurt Jaeger wrote: Hi! Question: when will mod_perl be available for Apache 24? There's a PR where people are discussing this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191471 This PR needs more testers etc. I've updated the PR with a patch against the latest mod_perl trunk revision (r1602105). The patch against the port can be grabbed from here or from our bugzilla http://people.freebsd.org/~ohauer/diffs/apache/mod_perl2-2.0.8_apache24.diff Please test *at own risk*, and report issues to upstream and here so we can integrate fresh upstream fixes and update the port. The first proposed patch will allows the port to build but I have to many concerns for integrating this simple fix into the tree. I don't believe the first patch on the PR will work right else it would take the upstream dev. work and time for mod_perl2 at absurd-um ... I have taken a slightly different approach, using the mod_perl2 SVN /httpd24 branch as the starting point. This branch, much to my surprised, after adding some missing Perl Modules, compiled and almost all of the tests ran and passed. I am currently trying some of my own tests to see if the functionality that I need is present. As Olli says: Please test/use at your own risk. Report problems. Personally, I am expecting Apache 24 to die a horrible death when I start testing this stuff... ___ 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 meta.txz: Not Found
I updated to pkg-1.3.3 and am getting these annoying messages: pkg: http://pkg.FreeBSD.org/freebsd:9:x86:64/latest/meta.txz: Not Found pkg: http://pkg.FreeBSD.org/freebsd:9:x86:64/new_xorg/meta.txz: Not Found They appear to be harmless, but is there a way to turn them off or can the repository put in meta.txz file? Ummm... I think that the 'official' FreeBSD repositories should not generate these messages... ___ 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
Apache 24 + mod_perl
Question: when will mod_perl be available for Apache 24? Is anybody
using it (see below), and what problems (if any) were there? The method
outlined below may or may not work - I haven't tried it. Any comments
or suggestions?
Background:
I wanted to update to Apache 24/FreeBSD 9.2. Everything went fine until
I hit mod_perl. The
current Port Makefile as of Fri 01 Aug 2014 is marked as:
.if ${APACHE_VERSION} 22
BROKEN= Does not build with apache24
.endif
Apparently mod_perl is currently not compatible with Apache24. The
perl-modperl mailing list has a posting:
http://mail-archives.apache.org/mod_mbox/perl-modperl/201402.mbox/%3CCADED=k4p2hfc6k1san3mpmm8vz+gwt5rsij5samvlrv7z5z...@mail.gmail.com%3E
This has the following information:
Date: Sun, 16 Feb 2014 15:36:18 GMT
The Debian project is shipping mod_perl with httpd24 support
based on http://svn.apache.org/repos/asf/perl/modperl/branches/httpd24/.
An update on the state of things regarding httpd-2.4 support in mod_perl:
We are working hard to get this done and are 99% of the way there.
Both volunteers and volunteers' time is limited, though, so progress
has been slow. A lot of work has taken place in the httpd24 branch,
and as Dominic says, some Linux distros are already shipping that.
There is also a posting on how to abuse the mod_perl2 port, download the
source from the SVN repository and force mod_perl2 to compile it:
https://forums.freebsd.org/viewtopic.php?f=5t=46523
___
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: When poudriere jails become stuck in a loop
On 07/18/14 02:41, Beeblebrox wrote: I have observed that some poudriere jails, on occasion, get stuck in a hanging pattern. If I go to a jail that became stuck, top always shows something like: PID USERNAME THR PRI NICE SIZE RES STATE C TIMEWCPU COMMAND 91534 root 1 233 21840K 2376K CPU33 0:00 0.02% top 24713 root 1 523 49828K 0K wait2 0:13 0.00% pkg-static 24637 root 1 233 9048K 148K wait0 0:00 0.00% make 26552 root 1 523 190M44K urdlck 0 0:00 0.00% dot 24652 root 1 523 16988K 0K wait1 0:00 0.00% sh 26551 root 1 523 16988K 0K wait3 0:00 0.00% sh The solution I have found is to kill the process named dot (26552 in this case). Poudriere then picks up from where it left off and successfully completes the package build. Regards. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/When-poudriere-jails-become-stuck-in-a-loop-tp5929736.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ 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 I think I have observed the same issue. When you say 'go to a jail' what did you do to see this information? I get a lot of other info that clouds the issue. ___ 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
Missing pkg x11/kde4
I was following the directions in the FreeBSD handbook and did: pkg install x11/kde4 There does not appear to be a kde4 package in the respository. Did the build fail for this? ___ 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: Some suggestions about PKGNG documentation
On 07/05/14 03:18, Mike Brown wrote: Warren Block wrote: The documentation team has a standing offer to either assist with markup or accept content-only submissions and do the markup on them. That's good to know. I was under the impression it had to be submitted as DocBook XML. Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsuXMbscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org OK. Its been 10 years since I lasted looked at the FBSD documents. Nowever, I know SGML, XML, and have written documents in them. 1. Point me to the source of one of the documents as a starting point. 2. Point me to the tools that I need to use to massage the document. (There used to be a Documenter's Handbook, is it still around?) I will take one of these documents as a starting point and then update it. HOWEVER... I am hoping that one of the document team will 'proof' this for format and content. ___ 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: kde4 packages, WITHOUT_NEW_XORG fails
On 07/04/14 16:28, Kevin Oberman wrote: On Fri, Jul 4, 2014 at 4:15 PM, Patrick Powell papow...@astart.com mailto:papow...@astart.com wrote: On 07/04/14 14:23, Koop Mast wrote: [...] On 4-7-2014 22:49, Kevin Oberman wrote: This discussion begs the question of why won't WITH_NEW_XORG work for you? I am aware of some pretty old hardware that simply has no support in recent Xorg servers, but these are pretty old by now. And, as time passes, the bit rot will make more and more things fail with the old code. I am far from an X expert, but a post to x11@ of the failure you see WITH_NEW_XORG including the Xorg.0.log, /etc/make.conf, /etc/src.conf and any Xorg.conf you are using might get things working (and might not). x11@ is a far better place to ask any of the questions about X issues. I should also recommend that, if you have not already tried, move your Xorg.conf aside and let X try to configure itself. It is very rare to require a full configuration these days. Most only need things for added fonts and extra modules. The xorg.conf on my laptop is only about 27 lines long and mostly added fonts. ports/UPDATING states: 20140218: AFFECTS: users of KDE SC 4 AUTHOR: k...@freebsd.org KDE SC ports have been updated to 4.12.2. kdeadmin, kdenetwork, kdesdk, and kdetoys ports have been split due to upstream changes. KDE Workspace port has been updated to 4.11.6. It requires modern Mesa libraries, provided by WITH_NEW_XORG knob. To update Xorg ports to newer version follow instructions at https://wiki.freebsd.org/Graphics So it not possible anymore to run KDE4 with WITHOUT_NEW_XORG. -Koop Ahhh!!! I missed that. If this is the case, then perhaps the default for generating the PKGNG repository should be WITH_NEW_XORG? Then we could use the PKGNG respository for KDE4 applications. OR: we could have two repositories: one which uses WITHOUT_NEW_XORG and has the old Xorg drivers and no KDE4 support and one with WITH_NEW_XORG which has the new Xorg drivers and KDE4 support. I think I read some discussion about this possibility but I can't recall the outcome. Your timing is MOST excellent. Koop just announced those repositories were available a few hours ago. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=306646+0+current/freebsd-announce The repositories cover 9.x and 10.x for i386 and amd64. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com mailto:rkober...@gmail.com Huzzah! Hurrah Ummm... hold on a bit here... No 8.4 support? Why not just toss it in, with the usual: Warning! Here there be dragons. Or at least untested and verified packages. These have been compiled with make.conf containing: MAKE_NEW_XORG=yes At least doing this will provide KDE4 packages in an easy to access fashion. As for the XORG support, this seems to work fine for me as well, so I do not need compatibility with the old drivers... Yes, yes... sloth. ___ 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
kde4 packages, WITHOUT_NEW_XORG fails
I have run into a problem trying to recompile the KDE4 packages with WITHOUT_NEW_XORG=YES. From the CHANGES file: 20140416: AFFECTS: users of x11/xorg graphics/dri graphics/libGL and related ports AUTHOR: x...@freebsd.org The default xorg version has been switched on FreeBSD 10-STABLE and FreeBSD 9-STABLE. To upgrade graphics/libGL, graphics/dri and related MESA ports, it is necessary to first remove the old versions of those ports. No special upgrade procedure is needed for xorg ports but it is necessary to recompile all xorg drivers (xf86-*) and other ports that depend on the xserver version, including emulators/virtualbox-ose-additions. Portrevisions have been bumped where needed, but users of drivers not in the ports tree will need to recompile those. If it is important to stay on the old versions, it is possible to specify WITHOUT_NEW_XORG= in /etc/make.conf to get the old xorg distribution. My make.conf file: WITH_PKGNG=yes WITHOUT_NEW_XORG=yes I did portsnap fetch update, and then did: # cd /usr/ports/x11/kde4 # make missing /tmp/missing_files I massaged the /tmp/missing_files to use pkg to try to download a package if it was in the repository. If they were not, I then tried to use 'make BATCH=YES install' to compile and install the port. Here is the output of the script, showing the errors for the ports that did not compile. x11-themes/kdeartwork4 deskutils/kdeplasma-addons x11-clocks/kdetoys4 x11/kde4-workspace net/kget net/krdc x11-clocks/ktux graphics/libEGL graphics/libglesv2 print/indexinfo graphics/libglapi multimedia/libdvdcss Output: + p x11-themes/kdeartwork4 + pkg install x11-themes/kdeartwork4 Updating repository catalogue pkg: No packages matching 'x11-themes/kdeartwork4' available in the repositories + cd /usr/ports/x11-themes/kdeartwork4 + make BATCH=yes install ===Verifying install for /usr/local/lib/libkworkspace.so in /usr/ports/x11/kde4-workspace === kde-workspace-4.11.9 requires modern libGL. Please, set WITH_NEW_XORG and update your ports. *** Error code 1 Stop in /usr/ports/x11/kde4-workspace. *** Error code 1 Stop in /usr/ports/x11-themes/kdeartwork4. + p deskutils/kdeplasma-addons + pkg install deskutils/kdeplasma-addons Updating repository catalogue pkg: No packages matching 'deskutils/kdeplasma-addons' available in the repositories + cd /usr/ports/deskutils/kdeplasma-addons + make BATCH=yes install ===Verifying install for /usr/local/lib/libkworkspace.so in /usr/ports/x11/kde4-workspace === kde-workspace-4.11.9 requires modern libGL. Please, set WITH_NEW_XORG and update your ports. *** Error code 1 Stop in /usr/ports/x11/kde4-workspace. *** Error code 1 Stop in /usr/ports/deskutils/kdeplasma-addons. + p x11-clocks/kdetoys4 + pkg install x11-clocks/kdetoys4 Updating repository catalogue pkg: No packages matching 'x11-clocks/kdetoys4' available in the repositories + cd /usr/ports/x11-clocks/kdetoys4 + make BATCH=yes install === Staging for kdetoys-4.12.5 ===Verifying install for /usr/local/bin/ktux in /usr/ports/x11-clocks/ktux ===Verifying install for /usr/local/lib/libkworkspace.so in /usr/ports/x11/kde4-workspace === kde-workspace-4.11.9 requires modern libGL. Please, set WITH_NEW_XORG and update your ports. *** Error code 1 Stop in /usr/ports/x11/kde4-workspace. *** Error code 1 Stop in /usr/ports/x11-clocks/ktux. *** Error code 1 Stop in /usr/ports/x11-clocks/kdetoys4. + p x11/kde4-workspace + pkg install x11/kde4-workspace Updating repository catalogue pkg: No packages matching 'x11/kde4-workspace' available in the repositories + cd /usr/ports/x11/kde4-workspace + make BATCH=yes install === kde-workspace-4.11.9 requires modern libGL. Please, set WITH_NEW_XORG and update your ports. *** Error code 1 Stop in /usr/ports/x11/kde4-workspace. + p net/kget + pkg install net/kget Updating repository catalogue kg: No packages matching 'net/kget' available in the repositories + cd /usr/ports/net/kget + make BATCH=yes install ===Verifying install for /usr/local/lib/libkworkspace.so in /usr/ports/x11/kde4-workspace === kde-workspace-4.11.9 requires modern libGL. Please, set WITH_NEW_XORG and update your ports. *** Error code 1 Stop in /usr/ports/x11/kde4-workspace. *** Error code 1 Stop in /usr/ports/net/kget. + p net/krdc + pkg install net/krdc Updating repository catalogue pkg: No packages matching 'net/krdc' available in the repositories + cd /usr/ports/net/krdc + make BATCH=yes install === Building for krdc-4.12.5 [ 83%] Built target krdc /usr/ports/net/krdc/work/krdc-4.12.5/vnc/vncclientthread.cpp: In member function 'void VncClientThrea d::clientSetKeepalive()': /usr/ports/net/krdc/work/krdc-4.12.5/vnc/vncclientthread.cpp:610: error: 'TCP_KEEPIDLE' was not decla red in this scope /usr/ports/net/krdc/work/krdc-4.12.5/vnc/vncclientthread.cpp:616: error: 'TCP_KEEPINTVL' was not decl ared in this scope
Re: kde4 packages, WITHOUT_NEW_XORG fails
On 07/04/14 09:56, Kevin Oberman wrote: On Fri, Jul 4, 2014 at 9:14 AM, Patrick Powell papow...@astart.com mailto:papow...@astart.com wrote: I have run into a problem trying to recompile the KDE4 packages with WITHOUT_NEW_XORG=YES. From the CHANGES file: 20140416: AFFECTS: users of x11/xorg graphics/dri graphics/libGL and related ports AUTHOR: x...@freebsd.org The default xorg version has been switched on FreeBSD 10-STABLE and FreeBSD 9-STABLE. To upgrade graphics/libGL, graphics/dri and related MESA ports, it is necessary to first remove the old versions of those ports. No special upgrade procedure is needed for xorg ports but it is necessary to recompile all xorg drivers (xf86-*) and other ports that depend on the xserver version, including emulators/virtualbox-ose-additions. Portrevisions have been bumped where needed, but users of drivers not in the ports tree will need to recompile those. If it is important to stay on the old versions, it is possible to specify WITHOUT_NEW_XORG= in /etc/make.conf to get the old xorg distribution. My make.conf file: WITH_PKGNG=yes WITHOUT_NEW_XORG=yes I did portsnap fetch update, and then did: # cd /usr/ports/x11/kde4 # make missing /tmp/missing_files I massaged the /tmp/missing_files to use pkg to try to download a package if it was in the repository. If they were not, I then tried to use 'make BATCH=YES install' to compile and install the port. Unfortunately, many ports have been updated with calls to the Mesa API that do not exist in the WITHOUT_NEW_XORG version of Mesa. As a result, you can no longer build/run recent version of those ports WITHOUT_NEW_XORG. KDE is probably the bast known of these. That leaves two options: 1. Move to the new Xorg versions (which may not support some older hardware) 2. Use an old (and possibly vulnerable) version of KDE The Xorg and KDE folks simply don't provide any other options that I am aware of. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com mailto:rkober...@gmail.com OK, then could they please update the CHANGES file and state that? And/or put a warning in the UPDATING or CHANGES ports file: WITHOUT_NEW_XORG option not supported I appreciate the problems, I was just hoping that there was a trivial solution to them... ___ 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: kde4 packages, WITHOUT_NEW_XORG fails
On 07/04/14 14:23, Koop Mast wrote: On 4-7-2014 22:49, Kevin Oberman wrote: On Fri, Jul 4, 2014 at 12:03 PM, Patrick Powell papow...@astart.com wrote: On 07/04/14 09:56, Kevin Oberman wrote: On Fri, Jul 4, 2014 at 9:14 AM, Patrick Powell papow...@astart.com wrote: I have run into a problem trying to recompile the KDE4 packages with WITHOUT_NEW_XORG=YES. From the CHANGES file: 20140416: AFFECTS: users of x11/xorg graphics/dri graphics/libGL and related ports AUTHOR: x...@freebsd.org The default xorg version has been switched on FreeBSD 10-STABLE and FreeBSD 9-STABLE. To upgrade graphics/libGL, graphics/dri and related MESA ports, it is necessary to first remove the old versions of those ports. No special upgrade procedure is needed for xorg ports but it is necessary to recompile all xorg drivers (xf86-*) and other ports that depend on the xserver version, including emulators/virtualbox-ose-additions. Portrevisions have been bumped where needed, but users of drivers not in the ports tree will need to recompile those. If it is important to stay on the old versions, it is possible to specify WITHOUT_NEW_XORG= in /etc/make.conf to get the old xorg distribution. My make.conf file: WITH_PKGNG=yes WITHOUT_NEW_XORG=yes I did portsnap fetch update, and then did: # cd /usr/ports/x11/kde4 # make missing /tmp/missing_files I massaged the /tmp/missing_files to use pkg to try to download a package if it was in the repository. If they were not, I then tried to use 'make BATCH=YES install' to compile and install the port. Unfortunately, many ports have been updated with calls to the Mesa API that do not exist in the WITHOUT_NEW_XORG version of Mesa. As a result, you can no longer build/run recent version of those ports WITHOUT_NEW_XORG. KDE is probably the bast known of these. That leaves two options: 1. Move to the new Xorg versions (which may not support some older hardware) 2. Use an old (and possibly vulnerable) version of KDE The Xorg and KDE folks simply don't provide any other options that I am aware of. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com OK, then could they please update the CHANGES file and state that? And/or put a warning in the UPDATING or CHANGES ports file: WITHOUT_NEW_XORG option not supported I appreciate the problems, I was just hoping that there was a trivial solution to them... I have no commit bit, but perhaps someone who does will put a note in CHANGES. I certainly think it would be a good idea. This discussion begs the question of why won't WITH_NEW_XORG work for you? I am aware of some pretty old hardware that simply has no support in recent Xorg servers, but these are pretty old by now. And, as time passes, the bit rot will make more and more things fail with the old code. I am far from an X expert, but a post to x11@ of the failure you see WITH_NEW_XORG including the Xorg.0.log, /etc/make.conf, /etc/src.conf and any Xorg.conf you are using might get things working (and might not). x11@ is a far better place to ask any of the questions about X issues. I should also recommend that, if you have not already tried, move your Xorg.conf aside and let X try to configure itself. It is very rare to require a full configuration these days. Most only need things for added fonts and extra modules. The xorg.conf on my laptop is only about 27 lines long and mostly added fonts. ports/UPDATING states: 20140218: AFFECTS: users of KDE SC 4 AUTHOR: k...@freebsd.org KDE SC ports have been updated to 4.12.2. kdeadmin, kdenetwork, kdesdk, and kdetoys ports have been split due to upstream changes. KDE Workspace port has been updated to 4.11.6. It requires modern Mesa libraries, provided by WITH_NEW_XORG knob. To update Xorg ports to newer version follow instructions at https://wiki.freebsd.org/Graphics So it not possible anymore to run KDE4 with WITHOUT_NEW_XORG. -Koop Ahhh!!! I missed that. If this is the case, then perhaps the default for generating the PKGNG repository should be WITH_NEW_XORG? Then we could use the PKGNG respository for KDE4 applications. OR: we could have two repositories: one which uses WITHOUT_NEW_XORG and has the old Xorg drivers and no KDE4 support and one with WITH_NEW_XORG which has the new Xorg drivers and KDE4 support. I think I read some discussion about this possibility but I can't recall the outcome. ___ 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
Some suggestions about PKGNG documentation
OK OK OK - I just started using pkgng. You know the ancient Chinese
curse - 'May you live in interesting times!', well starting to use
pkgng was ... interesting. Attached are some comments concerning the
documentation. I hope you find them useful.
On a side note: from reading the notice about the pending inhumation of
the pkg_xxx system in the Ports tree, until I converted to using pkgng
took less than a day. It would have taken less time if I stopped
playing with 'pkg search' and other commands and concentrated on getting
the latest versions of the ports/packages installed. Poudriere is next
on my todo list..
I have been trying out the PKGng software, and would like to make some
suggestions and ask some questions. The comments and suggestions below
have been made from my notes when I was trying to figure out the pkgng
commands.
BIG SUGGESTION:
TUTORIAL: The Savant's Guide To Ports, Packages, PkgNG
Try to put a lot of the information about pkgng, repositories,
etc. in a single place. I suggest a tutorial format, rather
than a user manual format, with references to the various
man pages, other documents, etc.
1. Installation of PKGng
2. Ports - Use the Source, Luke!
3. Binary Packages - Let Somebody Else Do The Work
4. Respositories -
- what they are
- 'standard' repositories
5. Ports and Pkgng play together - when you use pkg to install
a port then the port system will recognize that it has been
installed. Note: details on how this works would be good.
An EXAMPLE of using
portsnap fetch update
Then:
cd /.../block/port; make package;
updating to latest version: portmaster, portupgrade
OR
pkg add block/port
updating to latest version: pkg upgrade
Discuss advantages, etc. of both methods
6. Simple commands/operations
finding a package in a repository
when was a package updated/created
finding out the last update for a package
installing a package from a reponsitory
upgrading a package from a repository
upgrading ONLY a single package from a repository
Not so simple:
making a package from a port
Question: does 'make package' make a pkgng compatible package
installing the package from a file - pkg add
preventing pkg from updating its database from a respository
multiple respositories
Detailed explanations on pkg set, pkg autoremove and other
non-obvious commands
using 'pkg add' with a package generated from a port
7, Setting up a repository and using multiple repositories
SUGGESTION:
Update http://blogs.freebsdish.org/portmgr/2014/02/03/time-to-bid-farewell-
to-the-old-pkg_-tools/ or point the entry in Mk/bsd.port.mk to an updated
version.
WHY:
The formatting seems to be a little off - action is present as well as
some
spurious UNICODE. Also add a pointer to the
http://lists.freebsd.org/pipermail/freebsd-pkg/2013-October/000107.html
web page.
SUGGESTION:
The https://wiki.freebsd.org/pkgng web page has:
See Pkg packages availability announcement for more information on usage.
with a link to
http://lists.freebsd.org/pipermail/freebsd-pkg/2013-October/000107.html
Correct the
http://lists.freebsd.org/pipermail/freebsd-pkg/2013-October/000107.html
posting or point the link to a new one that has the 'correct' repo file
entries:
Old:
FreeBSD: {
url: http://pkg.FreeBSD.org/${ABI}/latest;,
mirror_type: srv,
enabled: yes
}
Corrected:
FreeBSD: {
url: pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
mirror_type: srv,
enabled: yes
}
SUGGESTION:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html
Using pkgng for Binary package management
Update and edit this document and add the information about specifying
the 'repos' information.
Add information to the WIKI page about the respository format,
purpose, structure, or whatever. Also add this to the WIKI page.
If/When a tutorial is created, add a link to the tutorial.
SUGGESTION:
Add 'pkg repo' or 'man pkg-repo' to give details about the repositories
structure, format,
care and feeding, etc.
SUGGESTION: WIKI https://wiki.freebsd.org/pkgng#PKG
Add a link from the pkgng-intro.html to the WIKI Page.
Add information to the WIKI page about the respository format,
purpose, structure, or whatever.
Add the information in the https://wiki.freebsd.org/PkgPrimer to this
document
I have been trying out the PKGng software, and would like to make some
suggestions and ask some questions. The comments and suggestions below
have been made from my notes when I was trying to figure out the
BIG SUGGESTION:
TUTORIAL: The Savant's Guide To Ports, Packages, PkgNG
Try to put a lot of the information about pkgng, repositories,
etc. in a single place. I suggest a tutorial format, rather
than a user manual format, with references to the various
man pages, other documents, etc.
1. Installaltion of PKGng
2. Ports - Use the Source, Luke!
3. Binary Packages - Let Somebody Else Do The Work
4.
Re: mail/mailman port installation failing
On 05/28/14 21:16, John Marshall wrote: On Wed, 28 May 2014, 16:36 +1000, John Marshall wrote: I'm having no joy trying to install mailman on a new system. Builds fine but won't install. Any tips appreciated. === Registering installation for mailman-2.1.18.1_1 pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/data/sitelist.cfg): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/spam/): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/qfiles/): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/logs/): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/locks/): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/lists/): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/data/): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/archives/public/): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/archives/private/): No such file or directory pkg-static: lstat(/kits/ports/mail/mailman/work/stage/usr/local/mailman/archives/): No such file or directory *** [fake-pkg] Error code 74 After helpful off-list mail from mandree@ which pointed at this being a local problem, I eventually found the following line in /usr/local/etc/ports.conf. mail/mailman: CONFIGURE_ARGS=--with-var-prefix=/data/mailman One of those tweaks one implements to accommodate a local customization, and doesn't even remember it's there 6 or 7 years later. It would appear that this kind of thing doesn't play nicely with the new staging environment. After removing that line from ports.conf and rebuilding the port, it installed happily. Obviously I then had to reshuffle my data directories manually. I must be suffering from advanced memory loss--- when did /usr/local/etc/ports.conf creep into this? Is there a link to documentation on this? ___ 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: Done with this port
On 05/20/14 22:10, Matthias Andree wrote: Am 21.05.2014 03:49, schrieb Paul Schmehl: Thanks. With some of my ports I have been really struggling trying to get staging working. I'd be very interested to see what you did, since it was apparently easy for you to do. A bit of experience with packaging helped indeed. The differences are visible in this automated message: http://lists.freebsd.org/pipermail/svn-ports-head/2014-May/058212.html The INSTALL_TARGET that sets the INSTALL_ROOT (supported by iwidget's Makefile) is useful, and more help (for the MANN conversion) is available on the FreeBSD Wiki: http://wiki.freebsd.org/ports/StageDir/ ___ 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 Mathias, I think that brief description of how you did this would be VERY useful to some of us looking at this problem and not knowing where to start. Perhaps an: 'this is the way it was' and a 'this is the way it should be' document would be good. Or even a list of links to 'helpful hints' documents. Thanks! I really appreciate your efforts on the ports and packages ___ 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
some perl5 modules with .xs components fail to install/package
I also submitted this as a PR.
I installed a FreeBSD 8.4-Release.
Installed perl5:
root@test84:/install/INSTALL_FreeBSD_84 # perl -v
This is perl 5, version 14, subversion 4 (v5.14.4) built for amd64-freebsd
I then compiled and tried to install a laundry list of perl modules.
Some modules need to compile and install .so and .bs files. Some, but
not all,
of these modules had the following error. It appears that the .bs file
is listed in the PLIST
XX === Building package for p5-Bit-Vector-7.3
XX tar: lib/perl5/site_perl/5.14/mach/auto/Bit/Vector/Vector.bs: Cannot
stat: No such file or directory
XX tar: Error exit delayed from previous errors.
But there is no Vector.bs file:
# find work -name '*.bs'(no output - no file found)
I also did:
test84: {60} # cd work/Bit-Vector-7.3/
test84: {61} # make test
PERL_DL_NONLAZY=1 /usr/local/bin/perl5.14.4 -MExtUtils::Command::MM
-MTest::Harness -e undef *Test::Harness::Switches; test_harness(0,
'blib/lib', 'blib/arch') t/*.t
t/00_version.t .. ok
t/01_new.t .. ok
t/02_destroy.t .. ok
t/03__operations.t .. ok
t/04___functions.t .. ok
t/05__primes.t .. ok
t/06__subset.t .. ok
t/07_compare.t .. ok
t/08__resize.t .. ok
t/09__parameters.t .. ok
t/10___intervals.t .. ok
t/11___shift.t .. ok
t/12__string.t .. ok
t/13___increment.t .. ok
t/14___empty.t .. ok
t/15_add.t .. ok
t/16subtract.t .. ok
t/17_gcd.t .. ok
t/28___chunklist.t .. ok
t/30__overloaded.t .. ok
t/40___auxiliary.t .. ok
t/50_freeze_thaw.t .. ok
t/51_file_nstore.t .. ok
All tests successful.
Files=23, Tests=91963, 9 wallclock secs ( 7.84 usr 0.09 sys + 1.54
cusr 0.18 csys = 9.65 CPU)
Result: PASS
So it appears that the .bs file is not generated or required.
I patched the pkg-plist file:
test84: {64} # diff -bc pkg-plist*
*** pkg-plist Fri Oct 25 10:23:07 2013
--- pkg-plist.orig Fri Oct 25 10:22:50 2013
***
*** 5,10
--- 5,11
%%SITE_PERL%%/%%PERL_ARCH%%/Bit/Vector/String.pm
%%SITE_PERL%%/%%PERL_ARCH%%/Bit/Vector/String.pod
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Bit/Vector/.packlist
+ %%SITE_PERL%%/%%PERL_ARCH%%/auto/Bit/Vector/Vector.bs
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Bit/Vector/Vector.so
@dirrm %%SITE_PERL%%/%%PERL_ARCH%%/auto/Bit/Vector
@dirrm %%SITE_PERL%%/%%PERL_ARCH%%/Bit/Vector
And did:
make all install package
test84: {71} # make all install package
=== Installing for p5-Bit-Vector-7.3
=== p5-Bit-Vector-7.3 depends on package: p5-Carp-Clan=0 - found
=== p5-Bit-Vector-7.3 depends on file: /usr/local/bin/perl5.14.4 - found
=== Generating temporary packing list
=== Checking if math/p5-Bit-Vector already installed
Files found in blib/arch: installing files in blib/lib into architecture
dependent library tree
Installing
/usr/local/lib/perl5/site_perl/5.14/mach/auto/Bit/Vector/Vector.so
Installing /usr/local/lib/perl5/site_perl/5.14/mach/Bit/Vector.pm
Installing /usr/local/lib/perl5/site_perl/5.14/mach/Bit/Vector.pod
Installing /usr/local/lib/perl5/site_perl/5.14/mach/Bit/Vector/Overload.pm
Installing /usr/local/lib/perl5/site_perl/5.14/mach/Bit/Vector/String.pod
Installing /usr/local/lib/perl5/site_perl/5.14/mach/Bit/Vector/Overload.pod
Installing /usr/local/lib/perl5/site_perl/5.14/mach/Bit/Vector/String.pm
Installing /usr/local/lib/perl5/5.14/man/man3/Bit::Vector.3
Installing /usr/local/lib/perl5/5.14/man/man3/Bit::Vector::Overload.3
Installing /usr/local/lib/perl5/5.14/man/man3/Bit::Vector::String.3
=== Compressing manual pages for p5-Bit-Vector-7.3
=== Registering installation for p5-Bit-Vector-7.3
=== Building package for p5-Bit-Vector-7.3
I suspect that the pkg-plist entries for the indicated *.bs files are
not needed.
--
XX === Building package for p5-B-Utils-0.21
XX tar: lib/perl5/site_perl/5.14/mach/auto/B/Utils/Utils.bs: Cannot
stat: No such file or directory
XX tar: Error exit delayed from previous errors.
XX === Building package for p5-Bit-Vector-7.3
XX tar: lib/perl5/site_perl/5.14/mach/auto/Bit/Vector/Vector.bs: Cannot
stat: No such file or directory
XX tar: Error exit delayed from previous errors.
XX === Building package for p5-HTML-Parser-3.71
XX tar: lib/perl5/site_perl/5.14/mach/auto/HTML/Parser/Parser.bs: Cannot
stat: No such file or directory
XX tar: Error exit delayed from previous errors.
XX === Building package for p5-Params-Util-1.07
XX tar: lib/perl5/site_perl/5.14/mach/auto/Params/Util/Util.bs: Cannot
stat: No such file or directory
XX tar: Error exit delayed from previous errors.
XX === Building package for p5-Socket-2.012
XX tar: lib/perl5/site_perl/5.14/mach/auto/Socket/Socket.bs: Cannot
stat: No such file or directory
XX tar: Error exit delayed from previous errors.
XX === Building package for p5-Storable-2.45
XX tar: lib/perl5/site_perl/5.14/mach/auto/Storable/Storable.bs: Cannot
stat: No such file or directory
XX tar: Error exit delayed from previous errors.
XX ===
STABLE vs CURRENT packages
I just know that this is somewhere in the FreeBSD Handbook. And I probably deserve the scorn and snickers these questions will get. I just checked the .ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/ site and saw: packages-8-stable ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/ 10/11/1200:00:00 packages-8.3-release ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/ 03/28/1200:00:00 packages-8.4-release ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.4-release/ 05/09/1305:06:00 packages-9-current ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-current 12/09/1100:00:00 packages-9-stable ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/ 04/16/1315:20:00 packages-9.1-release ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/ 04/11/1303:29:00 packages-stable ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-stable 11/07/1100:00:00 I noted that the dates on the some of the packages in packages-8-stable were 2012, while most of those in packages-8.4.-release were much newer - 2013. And I noticed that there was no 'packages-8-current' directory. Questions: what is the relationship between the 'stable', 'release', and 'current' versions? And where is this documented in the FreeBSD Handbook? Is there supposed to be a 'packages-8-current' directory? OK, start the snickers and humiliation :-) ... -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System El Cajon, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com FAX 858-357-9931 ___ 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: Broken SNMP::Info ?
On 06/13/13 14:09, Loïc BLOT wrote: Hi all, i have updated my netdisco today, and some perl libraries due to long unupdated system (1 month). I have a strange problem, i cannot resolve. When i launch netdisco, it says: netdisco -d You need the SNMP::Info perl module, version 3.01 or newer. Please install it and try again. Can't locate SNMP.pm in @INC (@INC contains: /usr/local/bin /usr/local/lib/perl5/5.16/BSDPAN /usr/local/lib/perl5/site_perl/5.16/mach /usr/local/lib/perl5/site_perl/5.16 /usr/local/lib/perl5/5.16/mach /usr/local/lib/perl5/5.16 .) at /usr/local/lib/perl5/site_perl/5.16/SNMP/Info.pm line 16. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.16/SNMP/Info.pm line 16. Compilation failed in require at (eval 12) line 2. BEGIN failed--compilation aborted at (eval 12) line 2. (Before i was in 5.14.4 version and the problem was the same). I have the SNMP-Info port: pkg info|grep SNMP-Info p5-SNMP-Info-3.01 Perl5 module for gathering information from network devices I also tried to upgrade netdisco from recent 1.2 to 1.3, and also downgrade it to 1.1 but the problem persists. I also use MRTG and there is no problem. Anyone have an idea what i can check more, or how to resolve this problem (google doesn't help me)? Thanks for advance ! Make sure you are using 'use SNMP::Info' and not 'use SNMP'. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System El Cajon, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com FAX 858-357-9931 ___ 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: YModem terminal emulator
On 03/04/13 02:51, Andrea Venturoli wrote:
Hello.
I need a terminal emulator able to send a file over a USB/serial line,
using YModem.
So far I tried:
a) cutecom
When I press Send file... and pick, I get
Object::connect: No such signal QProgressDialog::cancelled() in
/usr/ports/comms/cutecom/work/cutecom-0.20.0/qcppdialogimpl.cpp:394
Object::connect: (receiver name: 'CuteCommDlg')
b) minicom
I get:
minicom: cannot open /dev/cuaU0: Permission denied
I also tried /dev/ttyU0, but message is the same.
I even tried running this as root, but I still get Permission denied
:-O
Any hint on these?
Any other port I can try?
bye Thanks
av.
___
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
I run into this a lot when I use USB serial devices. Try using:
ls /dev/cu*
and see what devices you have. For examle:
server:{15} # ls /dev/cu*
/dev/cuau0 /dev/cuau0.init /dev/cuau0.lock /dev/cuau1
/dev/cuau1.init /dev/cuau1.lock
Note that the device is /dev/cuau0 not /dev/cauU0
--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Road, Suite X,
Network and System El Cajon, CA 92019
Consulting 858-874-6543
Web Site: www.astart.com
___
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: wine/i386 for FreeBSD/amd64 port (aka wine-fbsd64)
or USB hard drive, and then be able to run wine on an i386 system. Would wine-fbsd64 be a separate port, or would it be wine built on i386, as the page http://wiki.freebsd.org/Wine suggests? It would be nice to be able to run Wine on i386 as well as amd64. Tom ___ 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 -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System El Cajon, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: epson r2400/2880 printers on freebsd8.2 amd64
On 11/20/11 03:57, David Southwell wrote: On Saturday 19 November 2011 06:44:28 Patrick Powell wrote: On 11/19/11 01:53, David Southwell wrote: Hi Anyone up to date on how to do high quality printing with epson inkjet printers (in my case r2400 and r2880) on freebsd8.2 amd64 systems. print/pips* reports they require 386 and do not compile on amd64. Thanks in advance for useful pointers David ___ 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 If you comment out ONLY_FOR_ARCHS= i386 in /usr/ports/print/pips800/Makefile.pips you can get it to compile. HOWEVER: there are a slew of warnings about 'cast from pointer to integer of different size' that may cause much grief and pain. Most of these appear to be generated in the GTK library, and apparently by the use of a cast to implement the 'offsetof' capability. Good luck... Thanks for the tip I wanted to compile pips780. After commenting out the ONLY_FOR_ARCH-i386 I got the errors shown below. I do not know how to fix them :-(!!! gsconfig.c: In function 'make_gsc': gsconfig.c:142: warning: comparison with string literal results in unspecified behaviour cc -DGS_PATH=\gs\ -DLOCALEDIR=\/usr/local/share/locale\ - DPRINTER_MODEL=\PM-780C\ -DPM780C - DLIBPATH=\/usr/local/lib/pips/libpm780c.so\ - DRSC_PATH=\/usr/local/etc/pipsrc\ -DSPOOL_NAME=\pm780c\ - DLOCALE_PATH=\/usr/local/share/locale\ - DNAVI_PATH=\/usr/local/bin/ekpnavi\ - DDATA_PATH=\/usr/local/libexec/pips/PM780C\ - DRULED_PATH=\/usr/local/libexec/pips/PM780C/BID.PRN\ - DPATCH_PATH=\/usr/local/libexec/pips/PM780C/PATCH.PRN\ - DBAND_PATH=\/usr/local/libexec/pips/PM780C/BAND.PRN\ - DCUT_PATH=\/usr/local/libexec/pips/PM780C/CUT.PRN\ -D_LPR_DIRECT -pipe -g - std=gnu89 -Wall -fsigned-char -L/usr/local/lib -pthread -o gsconfig780 gsconfig.o paper.o -lpthread sed s,%model_name%,PM-780C,; \ s,%bin_name%,pips780,; \ s,%gsconfig_name%,gsconfig780, filter.tmp filter780 gmake[2]: Leaving directory `/usr/ports/print/pips780/work/pips780-2.1.2/src' Making all in ekpd gmake[2]: Entering directory `/usr/ports/print/pips780/work/pips780-2.1.2/ekpd' gmake[3]: Entering directory `/usr/ports/print/pips780/work/pips780-2.1.2/ekpd' cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -pipe -g -std=gnu89 - Wall -c cbtd.c cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -pipe -g -std=gnu89 - Wall -c cbtd_comserv.c cbtd_comserv.c: In function 'comserv_thread': cbtd_comserv.c:162: warning: pointer targets in passing argument 3 of 'accept' differ in signedness cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -pipe -g -std=gnu89 - Wall -c cbtd_datatrans.c cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -pipe -g -std=gnu89 - Wall -c cbtd_setup.c cbtd_setup.c: In function 'parameter_setup': cbtd_setup.c:89: warning: pointer targets in passing argument 4 of 'get_parameter' differ in signedness cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -pipe -g -std=gnu89 - Wall -c cbtd_signal.c cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -pipe -g -std=gnu89 - Wall -c cbtd_thread.c cc -pipe -g -std=gnu89 -Wall -L/usr/local/lib -pthread -o ekpd cbtd.o cbtd_comserv.o cbtd_datatrans.o cbtd_setup.o cbtd_signal.o cbtd_thread.o ./libcbt.a -lpthread /usr/bin/ld: warning: i386 architecture of input file `./libcbt.a(cbtd_wrapper.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `./libcbt.a(ecbteg.o)' is incompatible with i386:x86-64 output /usr/bin/ld: warning: i386 architecture of input file `./libcbt.a(winfunc.o)' is incompatible with i386:x86-64 output /usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 internal error, aborting at /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/reloc.c line 4274 in bfd_generic_get_relocated_section_contents /usr/bin/ld: Please report this bug. gmake[3]: *** [ekpd] Error 1 gmake[3]: Leaving directory `/usr/ports/print/pips780/work/pips780-2.1.2/ekpd' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/print/pips780/work/pips780-2.1.2/ekpd' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/print/pips780/work/pips780-2.1.2' gmake: *** [all-recursive-am] Error 2 *** Error code 1 Stop in /usr/ports/print/pips780. [root@dns1 /usr/ports/print/pips780]# I haven't dug into the source code, but I have seen this error when there is x86 assembly code in an object file. I suspect the issue is with cbtd_wrapper as the name looks suspciously like something that would be assembly. Just a guess, now. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com
Re: epson r2400/2880 printers on freebsd8.2 amd64
On 11/19/11 01:53, David Southwell wrote: Hi Anyone up to date on how to do high quality printing with epson inkjet printers (in my case r2400 and r2880) on freebsd8.2 amd64 systems. print/pips* reports they require 386 and do not compile on amd64. Thanks in advance for useful pointers David ___ 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 If you comment out ONLY_FOR_ARCHS= i386 in /usr/ports/print/pips800/Makefile.pips you can get it to compile. HOWEVER: there are a slew of warnings about 'cast from pointer to integer of different size' that may cause much grief and pain. Most of these appear to be generated in the GTK library, and apparently by the use of a cast to implement the 'offsetof' capability. Good luck... -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: Automating Port Building- Setting options on the command line
On 04/02/11 20:39, Sutra Zhou wrote: What about using /usr/ports/ports-mgmt/portconf/? On Sun, Apr 3, 2011 at 6:21 AM, Patrick Powellpapow...@astart.com wrote: On 03/31/11 23:04, Alberto Villa wrote: On Friday 01 April 2011 02:49:06 Patrick Powell wrote: What I would like to do is pass in a set of default options on the command line such as: cd /usr/ports/lang/php5-extensions make configure THIS=yes THAT=no cd /usr/ports/multimedia/kdenlive make -DWITH_DVD -DWITH_FREI0R -DWITHOUT_LADSPA This did the trick. However, to bombproof it a little: make rmconfig -DWITH_OPTION ... target Once you do this you need to always put the rmconfig target in the make command. This is exactly what I wanted. I have been looking at tinderbox in more detail and it appears to be a better solution. I am planning to migrate to tinderbox in the near future. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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 looks like a dead project - no easily available documentation Ummm... OK. LPRng was last updated 2005... Before you point a finger, remember, three point back at yourself. No man page, etc. etc. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: Automating Port Building- Setting options on the command line
On 03/31/11 23:04, Alberto Villa wrote: On Friday 01 April 2011 02:49:06 Patrick Powell wrote: What I would like to do is pass in a set of default options on the command line such as: cd /usr/ports/lang/php5-extensions make configure THIS=yes THAT=no cd /usr/ports/multimedia/kdenlive make -DWITH_DVD -DWITH_FREI0R -DWITHOUT_LADSPA This did the trick. However, to bombproof it a little: make rmconfig -DWITH_OPTION ... target Once you do this you need to always put the rmconfig target in the make command. This is exactly what I wanted. I have been looking at tinderbox in more detail and it appears to be a better solution. I am planning to migrate to tinderbox in the near future. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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
Automating Port Building- Setting options on the command line
First, before you tell me to do it, I have already RTFM, done a google search, and even looked for examples. Here is what I am trying to do. I have to generate a set of packages for amd64 and i386 systems. I usually have a simple script that does: cd /usr/ports/XXX make make install make package cp generated package /.../repository This served my simple needs well, as most of the time I had gone through the configuration process and set up the default options that I wanted. But this requires me to a) run through this process once by hand b) copy the /var/db/ports/* to a machine with another architecture c) pray that the port options are the same on the i386 and amd64 versions. What I would like to do is pass in a set of default options on the command line such as: cd /usr/ports/lang/php5-extensions make configure THIS=yes THAT=no make make install make package I just know that somebody out there is doing this better, slicker, and with more savvy than I am doing this. OK. How do I do this? And just in case there are some others out there, could you put this information, or a hint to it, in the ports(7) document? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: Automating Port Building- Setting options on the command line
On 03/31/11 17:48, Jason Helfman wrote: On Thu, Mar 31, 2011 at 05:49:06PM -0700, Patrick Powell thus spake: First, before you tell me to do it, I have already RTFM, done a google search, and even looked for examples. Here is what I am trying to do. I have to generate a set of packages for amd64 and i386 systems. I usually have a simple script that does: cd /usr/ports/XXX make make install make package cp generated package /.../repository This served my simple needs well, as most of the time I had gone through the configuration process and set up the default options that I wanted. But this requires me to a) run through this process once by hand b) copy the /var/db/ports/* to a machine with another architecture c) pray that the port options are the same on the i386 and amd64 versions. What I would like to do is pass in a set of default options on the command line such as: cd /usr/ports/lang/php5-extensions make configure THIS=yes THAT=no make make install make package I just know that somebody out there is doing this better, slicker, and with more savvy than I am doing this. OK. How do I do this? And just in case there are some others out there, could you put this information, or a hint to it, in the ports(7) document? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com IMHO it is time you look into the wonders of Tinderbox. http://tinderbox.marcuscom.com/ -jgh OK, I ripped the tinderbox documentation. It is, more than likely, based on my 20 minute reading, going to do EXACTLY what I want. However, I think I might add that there is a bit of a learning curve here - actually, more like a learning 'splat against a brick wall'. Ok, if it needs tinderbox, then I will learn tinderbox. BUT!!! Is there an idiot simple, put this on the command line alternative to this to handle the 3 (three) !@#$!@#$!@#$ ports that require me to hand tune them? Patrick (This is the Brick Wall that we hit during development. And those are the bodies of the developers) Powell -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: mysql-client-5.5.10 fails to install properly, breaking all dependant ports
On 03/20/11 06:39, Robert Huff wrote: For the record: the upgrade wo 5.5.10 went smoothly here, vith both server and client appearing (on very minimal testing) to work as before. Robert Huff ___ 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 did they fix the broken mysql_install_db which has bad values for the various paths? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: mysql-client-5.5.10 fails to install properly, breaking all dependant ports
On 03/20/11 07:33, Jerry wrote: On Sun, 20 Mar 2011 07:19:11 -0700 Patrick Powellpapow...@astart.com articulated: On 03/20/11 06:39, Robert Huff wrote: For the record: the upgrade wo 5.5.10 went smoothly here, vith both server and client appearing (on very minimal testing) to work as before. Robert Huff ___ 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 did they fix the broken mysql_install_db which has bad values for the various paths? Well, if it was broken it must have been fixed since I have not experienced a single problem after updating the system last night. I did need to reboot the system after the initial install since Postfix was complaining. After that, all is working well. Try running mysql_update and mysql_install_db. The last version of these died with error messages indicating they could not find executables. The problem appeared to be that the scripts were generated with either null paths for the executable directories or the path was ./ (./data was one). I suspect that the original script values did not have entries for the paths. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: mysql-client-5.5.10 fails to install properly, breaking all dependant ports
On 03/20/11 13:20, Steven Hartland wrote: - Original Message - From: Patrick Powell papow...@astart.com Try running mysql_update and mysql_install_db. The last version of these died with error messages indicating they could not find executables. The problem appeared to be that the scripts were generated with either null paths for the executable directories or the path was ./ (./data was one). I suspect that the original script values did not have entries for the paths. I just updated here and no problems with mysql_upgrade there is no mysql_update, I assume that was just a typo? Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. My bad. That was mysql_upgrade. Sorry for the confusion. How about mysql_install_db? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: mysql-client-5.5.10 fails to install properly, breaking all dependant ports
On 03/20/11 14:38, Steven Hartland wrote: - Original Message - From: Patrick Powell papow...@astart.com My bad. That was mysql_upgrade. Sorry for the confusion. How about mysql_install_db? Can't test that I'm afraid as the machine is now in production. Might want to make sure the old mysql pkg was removed correctly before the new version was installed. If you want to compare your version with the one we have I've uploaded to: http://www.multiplaygameservers.com/dropzone/mysql_install_db.gz Hope that helps. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. Yep. Still messed up: At the start you have: basedir= builddir= ldata=./data langdir= srcdir= This should be: basedir=/usr/local finds /usr/local/bin builddir= ldata=/var/db/mysql/ set up by some other parts of the configure script but not put into mysql_install_db script langdir= srcdir= I use this quite heavily in some test scripts and installation scripts. Not to mention that it pops up during the MySQL installation. You also might have a peek at the messages put out during installation. They say something like ... start using: /usr/local/etc/rc.d/mysql-server.sh start drop the .sh I would have put in a formal PR but I gave up trying to patch the source code. Perhaps a little edit script in the pre-install part of the make file? -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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: FreeBSD Port: mysql-server-5.5.9
On 03/10/11 11:37, joeb wrote: I have been using mysql since fbsd 7.2 and always just issued the mysql_install_db command on the command line to create mysql's control databases and it always worked fine. But now with fbsd 8.2 I get the following error and have no idea why. I installed using pkg_add -r mysql55-server command. I see that 3 weeks ago you updated the mysql55-server port from mysql 554 to 559. I believe there is an error in your update causing the mysql_install_db command to error out. The error message follows. # /usr/local/binmysql_install_db --user=mysql or #rootmysql_install_db --user=mysql FATAL ERROR: Could not find ./bin/my_print_defaults If you compiled from source, you need to run 'make install' to copy the software into the correct location ready for operation. If you are using a binary release, you must either be at the top level of the extracted archive, or pass the --basedir option pointing to that location. * end of error msg. # /usr/local/binlocate my_print_defaults /usr/local/bin/my_print_defaults As you can see the script the error message says it can not find is really in the same location as the mysql_install_db script, so it should have found it. I ended up pointing to the 8.1 packages with the pkg-add command to install and then the mysql-server5.5.4 mysql_install_db command ran from the command line without any errors. ___ 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 The problem appears to be in the mysql_install_db script # All unrecognized arguments to this script are passed to mysqld. basedir= *Should be /usr/local* builddir= ldata=./data langdir= srcdir= I suspect that when the mysql_install_db script was generated that the source for the mysql_install_db was update/modified/changed: basedir= *mysql-5.5.9/scripts* builddir= ldata=@localstatedir@ langdir= srcdir= I suspect that@bindir@ would be the appropriate value. But if you do this you get: basedir=./bin builddir= ldata=./data langdir= srcdir= I suspect that given the level of complexity of the build process that trying to patch the source files to fix this would be extremely difficult. The other approach is to modify the PORT Makefile and have the mysql_install_db modified before installation with the correct binary directory. -- Patrick Powell Astart Technologies papow...@astart.com1530 Jamacha Road, Suite X, Network and System San Diego, CA 92019 Consulting 858-874-6543 Web Site: www.astart.com ___ 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
