Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill "annoying port email" Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
misc/amanda-server: Shared object "nss_dns.so.1" not found, required by "amfetchdump"
Hi, Since 2.5.1p1,1 the amfetchdump utility does not work anymore: -- snap -- $ amfetchdump -a -c CONFIG HOST da0s1e 20061108 1 Scanning /home/amanda/hold... 1 tape(s) needed for restoration sh: segmentation fault (core dumped) amfetchdump -a -c CONFIG HOST da0s1e 20061108 1 -- snap -- With strings on the .core file I have found: Shared object "nss_dns.so.1" not found, required by "amfetchdump" This "nss_dns.so.1" seems to be related to FreeBSD specific patches which other ports needed in the past... (google result). But I am not sure if this is the reason for the segmentation fault. Is there anybody out where amfetchdump works in 2.5.1p1,1? Regards, Andy ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade, apache2/apache22, php4/php5
On Nov 13, 2006, at 5:25 PM, Bill Moran wrote: In response to Harlan Stenn <[EMAIL PROTECTED]>: Will this "keep" across a "make update", or do I need to re-do it every time I update /usr/ports? I'm not familiar with using "make update" and I don't see any info on it in man ports. I run "make update" from /usr/src - it updates /usr/src, /usr/ ports, etc. portupgrade updates the information in /var/db/pkg. If make update doesn't change /var/db/pkg, then the two will not affect one another, for better or for worse. What "make update" does is run cvsup for you based on your settings in /etc/make.conf of which SUPFILES to use for updating your system. It has not much to do with portupgrade other than updating the ports tree.
Re: Firefox crashes on startup
James Bailie <[EMAIL PROTECTED]> 2006-11-08 16:25:47 +0200: > Justin Smith wrote: > > > This problem first appeared after upgrading Gnome to 2.16. Oddly, > > another computer seemingly configured exactly the same doesn't have this > > problem. > > There is likely a library mismatch somewhere which was not caught > by the ports system. I recently upgraded to firefox 2.0 and she > crashed on startup, but after invoking "portupgrade -R firefox" to > force an upgrade of dependencies, all was well. So that may be > the first thing to try. I had the same problem. It turned out that three Gnome libraries¹ were for some reason shadowed in /usr/X11R6/lib. "portsclean -Li" solved the problem. Perhaps Justin should try that, too, if Firefox still doesn't want to start. Ilari Laitinen 1 libgtk-12.so.2 libgdk-12.so.2 libgconf-2.so.4 -- Ilari Laitinen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: mpd4-4.0b5
On Sat, Nov 11, 2006 at 02:17:47AM +0100, [EMAIL PROTECTED] wrote: l> this my problem when i try to make mpd l> l> ===> Building for mpd4-4.0b5 l> ===> src l> Warning: Object directory not changed from original l> /usr/ports/net/mpd/work/mpd4-4.0b5/src l> make: don't know how to make mpd4.1. Stop l> *** Error code 2 l> l> Stop in /usr/ports/net/mpd/work/mpd4-4.0b5. l> *** Error code 1 l> l> Stop in /usr/ports/net/mpd. l> l> there is an error What is your FreeBSD version? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [nycbug-talk] creating "local" ports (fwd)
Hallo Charles Sprickman, > I'm finding that there are a number of ports that we need to patch for > some functionality that's unique to our business (qmail, mailfront, etc.). > Currently we just do "make patch" and then apply our patches. This works, > but is a bit of a pain to maintain. > Is there a way to create a "local" category? ie: /usr/ports/LOCAL I like to point out a very easy way: $ mkdir /usr/ports/LOCAL $ echo "PKGCATEGORY?=LOCAL" > /usr/ports/LOCAL/makefile.inc $ echo "PKGNAMESUFFIX?=-local" >> /usr/ports/LOCAL/makefile.inc Copy a port you like to change into this. build and install it from there. You need _no_ modifications on a port. PKGNAMESUFFIX or PKGNAMEPREFIX can be set to make standard and local packages coexists. If the master ports gets updated, you habe to merge the changes. Or you create a slave-port., which referes to the master ports in the normal ports tree. All base tools support this. > We might occasionally look at the real qmail/mailfront/djbdns or other > ports and see if there's anything we want to pull in, but we'd most likely > be doing more work with merging in more of our own patches/software. a) You can still add your own patches in /usr/ports/category/portname/files/ b) You can create in /usr/ports/category/portname/ a Makefile.local that defines additional steps, dependencies ... > Is there some mechanism that I'm missing to deal with a local category? > I've been googling without much luck, and I didn't see this addressed in > the porter's handbook. The minium requierement is: /usr/ports/LOCAL/makefile.inc:PKGCATEGORY=LOCAL > -How does one handle packages that depend on say, qmail, but I now want to > depend on local-qmail? I know portupgrade can be tought this by setting > an alternate pkgdep, but is there any clever way of doing this so that > when you're not using portupgrade the deps are adjusted? My pkg_update tool supports this. For each hostname there is an optional sed_file. $ head /usr/ports/local/update/data/depends.* ==> /usr/ports/local/update/data/depends.k3.dinoex.de <== s=www/lynx$=www/lynx-ssl= s|lang/gcc34|local/gcc34-objc| s|lang/gcc33|local/gcc33-objc| See: http://people.freebsd.org/~dinoex/batch/README http://people.freebsd.org/~dinoex/batch/pkg_update This is an updated version of: http://2004.eurobsdcon.org/talks.html?tx_ptspeechupload_pi1[showUid]=27 http://2004.eurobsdcon.org/uploads/media/EBSD04_27.pdf kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED] http://people.freebsd.org/~dinoex/errorlogs/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [nycbug-talk] creating "local" ports (fwd)
On 11/14/06, Dirk Meyer <[EMAIL PROTECTED]> wrote:
Hallo Charles Sprickman,
> I'm finding that there are a number of ports that we need to patch for
> some functionality that's unique to our business (qmail, mailfront, etc.).
> Currently we just do "make patch" and then apply our patches. This works,
> but is a bit of a pain to maintain.
> Is there a way to create a "local" category? ie: /usr/ports/LOCAL
I like to point out a very easy way:
$ mkdir /usr/ports/LOCAL
$ echo "PKGCATEGORY?=LOCAL" > /usr/ports/LOCAL/makefile.inc
$ echo "PKGNAMESUFFIX?=-local" >> /usr/ports/LOCAL/makefile.inc
I found a way where you don't need to set PKGCATEGORY, and allows your
local ports to be included in a 'make index'.
/usr/ports/Makefile.local
# $FreeBSD$
#
SUBDIR+=local
/usr/ports/local/Makefile
# $FreeBSD$
#
SUBDIR += emulators
SUBDIR += games
SUBDIR += graphics
SUBDIR += net
SUBDIR += security
SUBDIR += textproc
SUBDIR += x11
.include
/usr/ports/local/emulators/Makefile
# $FreeBSD$
#
COMMENT = Local Emulators for other operating systems
SUBDIR += linux-wine
.include
/usr/ports/local/emulators/Makefile.inc
# $FreeBSD$
#
# This file needs to be copied into every local/*/ subdirectory to set
# common variables.
# Used to set the origin of the local port
PKGORIGIN= local/${PKGCATEGORY}/${PORTDIRNAME}
# Used in the local ports tree to set dependencies on other local ports.
LOCALPORTSDIR= ${PORTSDIR}/local
#Uncomment if you want your local packages to have a "-local" suffix.
#PGKNAMESUFFIX?= -local
Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: eGroupWare-1.2_1
1. When will 1.05 be available 2. Egroupware fails to function with php5.2 I get these kinds of error codes, the problem seems to be with the mstring extension.: PHP Fatal error: Cannot redeclare class datetime in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.datetime.inc.php on line 45, referer: http://egroupware.nemo/setup/config.php [Tue Nov 14 15:06:10 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633, referer: http://egroupware.nemo.gov.lc/setup/ [Tue Nov 14 15:06:11 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633, referer: http://egroupware.nemo/setup/ [Tue Nov 14 15:06:11 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633, referer: http://egroupware.nemo/setup/ [Tue Nov 14 15:06:13 2006] [error] [client 10.200.21.12] PHP Notice: Uninitialized string offset: 0 in /usr/local/www/apache22/data/egroupware/setup/check_install.php on line 324, referer: http://egroupware.nemo/setup/index.php [Tue Nov 14 15:06:13 2006] [error] [client 10.200.21.12] PHP Notice: Uninitialized string offset: 0 in /usr/local/www/apache22/data/egroupware/setup/check_install.php on line 324, referer: http://egroupware.nemo/setup/index.php [Tue Nov 14 15:06:13 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/setup/check_install.php on line 324, referer: http://egroupware.nemo/setup/index.php [Tue Nov 14 15:09:44 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633 [Tue Nov 14 15:09:44 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633 [Tue Nov 14 15:09:44 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633 [Tue Nov 14 15:13:06 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633, referer: http://egroupware.nemo/setup/index.php?FormLogout=config [Tue Nov 14 15:13:06 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633, referer: http://egroupware.nemo/setup/index.php?FormLogout=config [Tue Nov 14 15:13:06 2006] [error] [client 10.200.21.12] PHP Warning: mb_strstr() [function.mb-strstr]: Empty haystack in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.egw_db.inc.php on line 1633, referer: http://egroupware.nemo/setup/index.php?FormLogout=config [Tue Nov 14 15:13:06 2006] [error] [client 10.200.21.12] PHP Fatal error: Cannot redeclare class datetime in /usr/local/www/apache22/data/egroupware/phpgwapi/inc/class.datetime.inc.php on line 45, referer: http://egroupware.nemo/setup/index.php?FormLogout=config ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/tiff port
Doug Barton wrote:
First off, you're likely to get a better response if you cc the
maintainer of the port, which I've done for you.
Of course, my apologies.
Second, what were the results of your testing the library built
without libcompat?
graphics/tiff has the following patch applied against it:
diff -u -r1.61 Makefile
--- Makefile8 Apr 2006 20:22:41 - 1.61
+++ Makefile14 Nov 2006 19:12:48 -000
@@ -23,7 +23,6 @@
CONFIGURE_TARGET=
CONFIGURE_ARGS+= --with-jpeg-include-dir=${LOCALBASE}/include \
--with-jpeg-lib-dir=${LOCALBASE}/lib
-LDFLAGS+= -lcompat
CONFIGURE_ENV+=LDFLAGS="${LDFLAGS}"
.if defined(WITH_X11) && !defined(WITHOUT_X11)
graphics/tiff (3.8.2) builds and installs with this patch without any
problems.
Furthermore, I've built and installed the following:
sane-backends-1.0.18
sane-frontends-1.0.14_2
xsane-0.991_1
gimp-2.2.13_1,1
which all depend in some way on graphics/tiff, without any problems.
With this newly built software, I've created and manipulated TIFF files
without problems (e.g. generated using xsane, opened and edited using GIMP).
So for me, everything seems to work fine with the applied diff. For what
it's worth, the system is a FreeBSD 6.1/i386.
Regards,
Daniel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Building Mailman w/ Qmail
76Hi; I went to install the port of Mailman and got presented with a screen asking me to select if I was going to build this with: 1) Sendmail 2) emix3 3) emix4 4) postfix 5) a chinese mailing list 6) htdig integration packages Huh? Where's qmail? TIA, Rachel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building Mailman w/ Qmail
Rachel Florentine wrote: 76Hi; I went to install the port of Mailman and got presented with a screen asking me to select if I was going to build this with: 1) Sendmail 2) emix3 3) emix4 4) postfix 5) a chinese mailing list 6) htdig integration packages Huh? Where's qmail? TIA, Rachel maybe its trying to tell you something! ;) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building Mailman w/ Qmail
Rachel Florentine wrote: 76Hi; I went to install the port of Mailman and got presented with a screen asking me to select if I was going to build this with: 1) Sendmail 2) emix3 3) emix4 4) postfix 5) a chinese mailing list 6) htdig integration packages Huh? Where's qmail? TIA, Rachel There are no further instructions exist at this time on how to integrate the mailman port with Qmail. If you want to do it yourself, take a look at: http://www.gnu.org/software/mailman/mailman-install/qmail-issues.html - Jean ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Still Confused...Building Port w/ Options
9275Hi;
I tried to issue a command to build openldap with env and options and it didn't
work. I tried it broken up in lines as below and as one long line. Please help
me understand what I'm doing wrong:
MAKE_ENV = {
'openldap23-server' => [
'CC=gcc CPPFLAGS="-I/usr/local/include/openssl/" \
LDFLAGS="-L/usr/local/lib/"'
],
}
MAKE_ARGS = {
'openldap23-server' => 'CONFIGURE_ARGS+= \
--localstatedir=/var/run/slapd \
--enable-spasswd \
--enable-modules \
--enable-shared \
--enable-dynamic \
--with-tls \
--with-cyrus-sasl \
--enable-bdb \
--disable-slapd \
--enable-openssl \
--enable-monitor \
--enable-proxycache \
--enable-unique \
--enable-ppolicy \
--enable-accesslog \
--disable-cleartext',
}
TIA,
Rachel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bacula FD with FreeBSD Jails
Hello Bacula Users We run FreeBSD with some Jails, all of them (jails and host system) run Bacula-FD. Our problme now is ... bacula-fd refuses to start on the host system after booting or when called manually by /usr/local/etc/rc.d/bacula-fd.sh with the following error: Local package initialization: bacula_fd already running? (pid=644 820 993 1170 1344 1554 1886 2099). The PIDs it complains about are the ones of the bacula-fd processes already running in the jails. We use the FreeBSD ports version 1.38.11_1 on FreeBSD 6.0-RELEASE-p15 Regrads Alain Wolf ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Security Hole in ports/proftpd
Would one of the commiters please grab ports/105510 and commit the patch. This fixes a serious security problem with this port. Thanks, Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | Alaska Paradise Travel \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgpeK03Vakl4J.pgp Description: PGP signature
Re: Bacula FD with FreeBSD Jails
On 14 Nov 2006 at 21:59, Alain Wolf wrote: > Hello Bacula Users > > We run FreeBSD with some Jails, all of them (jails and host system) run > Bacula-FD. > > Our problme now is ... > > bacula-fd refuses to start on the host system after booting or when > called manually by /usr/local/etc/rc.d/bacula-fd.sh > with the following error: > > Local package initialization: > bacula_fd already running? (pid=644 820 993 1170 1344 1554 1886 2099). > > The PIDs it complains about are the ones of the bacula-fd processes > already running in the jails. > > We use the FreeBSD ports version 1.38.11_1 on FreeBSD 6.0-RELEASE-p15 I would approach this from a conflict point of view. Configure bacula-fd in the host system to listen only on the IP address it should listen to. It sounds like it is trying to listen on all your IP addresses (e.g. aliases). The bacula-fd configuration file can specify the IP address. Hope that helps -- Dan Langille : Software Developer looking for work my resume: http://www.freebsddiary.org/dan_langille.php ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Bus error" and crash with gtk-2.10.6_2
Michael Proto wrote: > Hello, > > I recently upgraded gtk-2 to 2.10.6_2 on my FreeBSD 5.5 box so I could > install an updated firefox (was running gtk-2.6.3 which would cause a > build of firefox-2.0 to fail) and now whenever I try to access the > vertical scroll bar on any GTK2 app, the program crashes with a "Bus > error". If I try to use either the scroll bar or my wheel mouse (to > scroll inside the vertical scroll window), I get the same failure. For the list, I fixed this myself by deinstalling and reinstalling gtk20 (again) and all forward and reverse-dependent ports. Next time I'll check /usr/ports/UPDATING first :) -Proto ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Still Confused...Building Port w/ Options
On Tue, Nov 14, 2006 at 12:47:37PM -0800, Rachel Florentine wrote:
>
> I tried to issue a command to build openldap with env and options and it
> didn't work.
[snip]
> MAKE_ARGS = {
> 'openldap23-server' => 'CONFIGURE_ARGS+= \
> --localstatedir=/var/run/slapd \
> --enable-spasswd \
> --enable-modules \
> --enable-shared \
> --enable-dynamic \
> --with-tls \
> --with-cyrus-sasl \
> --enable-bdb \
> --disable-slapd \
> --enable-openssl \
> --enable-monitor \
> --enable-proxycache \
> --enable-unique \
> --enable-ppolicy \
> --enable-accesslog \
> --disable-cleartext',
> }
Modifiying CONFIGURE_ARGS isn't supported by the ports framework. It may
"work" (to some extent) with some ports, but openldap23-server isn't one
of them. Take a look at the port's Makefile, as many of those variables
have special knobs which you can set instead. If you find one that isn't
handled, poke the maintainer and/or submit a PR requesting that it be
added.
--
Shaun Amott // PGP: 0x6B387A9A
"A foolish consistency is the hobgoblin
of little minds." - Ralph Waldo Emerson
pgpXHBfN8OMBX.pgp
Description: PGP signature
how to keep PORTVERSION from going backwards?
How should I handle this? The software vendor version numbers go like this: 1.0b3 (older release) 1.0 (current release) 1.0.1 (upcoming release) The port currently has PORTVERSION = 1.0.b3, and has not made use of DISTVERSION. What's a good way to set PORTVERSION (and DISTVERSION, if needed) when I update the port to the current and upcoming releases? I don't want the PORTVERSION to go backwards. I assume that's what would happen if I set it to just match the vendor's version numbers, and I assume that's bad. Thanks for any advice! Mike ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to keep PORTVERSION from going backwards?
On Wednesday 15 November 2006 01:25, Mike Brown wrote: > How should I handle this? > > The software vendor version numbers go like this: > 1.0b3 (older release) > 1.0 (current release) > 1.0.1 (upcoming release) > > The port currently has PORTVERSION = 1.0.b3, and has not made use of > DISTVERSION. > > What's a good way to set PORTVERSION (and DISTVERSION, if needed) when > I update the port to the current and upcoming releases? I don't want > the PORTVERSION to go backwards. I assume that's what would happen if I > set it to just match the vendor's version numbers, and I assume that's > bad. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-naming.html#AEN521 -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpLvDCzNKSlT.pgp Description: PGP signature
Re: how to keep PORTVERSION from going backwards?
On 11/15/06, Mike Brown <[EMAIL PROTECTED]> wrote: How should I handle this? The software vendor version numbers go like this: 1.0b3 (older release) 1.0 (current release) 1.0.1 (upcoming release) The port currently has PORTVERSION = 1.0.b3, and has not made use of DISTVERSION. Use PORTEPOCH. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-naming.html#MAKEFILE-NAMING-REVEPOCH Dave. -- "Strange women lying in ponds distributing swords is no basis for a system of government." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
(no subject)
Hi, I've been having some problems with the emulaters/vgba-bin port. Although it downloads and installs correctly, it tells me: $ vgba /libexec/ld-elf.so.1: Shared object "libm.so.2" not found, required by "vgba" What should I do? Jimmy Hartzell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
graphics/xpdf
I am at a loss for what to do, as, trying to compile graphics/xpdf, I got the following results: $ sudo portinstall xpdf ---> Installing 'xpdf-3.01_3' from a port (graphics/xpdf) ---> Building '/usr/ports/graphics/xpdf' ===> Cleaning for freetype2-2.2.1_1 ===> Cleaning for gmake-3.81_1 ===> Cleaning for autoconf-2.59_2 ===> Cleaning for t1lib-5.1.0_1,1 ===> Cleaning for open-motif-2.2.3_2 ===> Cleaning for xorg-libraries-6.9.0 ===> Cleaning for gsfonts-8.11_2 ===> Cleaning for pkg-config-0.21 ===> Cleaning for gettext-0.14.5_2 ===> Cleaning for perl-5.8.8 ===> Cleaning for m4-1.4.4 ===> Cleaning for help2man-1.36.4_1 ===> Cleaning for libtool-1.5.22_2 ===> Cleaning for imake-6.9.0 ===> Cleaning for libdrm-2.0.2 ===> Cleaning for fontconfig-2.3.2_6,1 ===> Cleaning for libiconv-1.9.2_2 ===> Cleaning for p5-gettext-1.05_1 ===> Cleaning for expat-2.0.0_1 ===> Cleaning for xpdf-3.01_3 ===> Vulnerability check disabled, database not found ===> Extracting for xpdf-3.01_3 => MD5 Checksum OK for xpdf-3.01.tar.gz. => SHA256 Checksum OK for xpdf-3.01.tar.gz. => MD5 Checksum OK for xpdf-3.01pl2.patch. => SHA256 Checksum OK for xpdf-3.01pl2.patch. ===> Patching for xpdf-3.01_3 ===> Applying distribution patches for xpdf-3.01_3 ===> Applying FreeBSD patches for xpdf-3.01_3 ===> xpdf-3.01_3 depends on executable in : freetype-config - found ===> xpdf-3.01_3 depends on executable in : gmake - found ===> xpdf-3.01_3 depends on file: /usr/local/bin/autoconf259 - found ===> xpdf-3.01_3 depends on shared library: t1.5 - found ===> xpdf-3.01_3 depends on shared library: freetype.9 - found ===> xpdf-3.01_3 depends on shared library: Xm.3 - found ===> xpdf-3.01_3 depends on shared library: X11.6 - found ===> Configuring for xpdf-3.01_3 checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ANSI C... none needed checking for library containing strerror... none required checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for ranlib... ranlib checking for OS/2 (with EMX)... no checking for DOS (with DJGPP)... no checking how to run the C preprocessor... cc -E checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for gethostbyname... (cached) yes checking select() and fd_set in sys/select.h and sys/bsdtypes.h... not needed checking FD_ZERO and strings.h or bstring.h... not needed checking for rewinddir... yes checking for popen... yes checking for mkstemp... yes checking for mkstemps... yes checking whether select takes fd_set arguments... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for _LARGE_FILES value needed for large files... no checking for _LARGEFILE_SOURCE value needed for large files... no checking for fseeko... yes checking for fseek64... no checking for ftell64... no checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking whether to use Xpm library... maybe checking where to find the Xpm header files... checking X11/xpm.h usability... yes checking X11/xpm.h presence... yes checking for X11/xpm.h... yes checking for XpmCreatePixmapFromData in -lXpm... yes using Xpm library checking whether to use Xext library... maybe checking where to find the Xext header files... checking X11/Xlib.h usability... yes checking X11/Xlib.h presence... yes checking for X11/Xlib.h... yes checking for XextAddDisplay in -lXext... yes using Xext library checking whether to use Xp library... maybe checking where to find the Xp header files... checking X11/extensions/Print.h usability... yes checking X11/extensions/Print.h presence... yes checking for X11/extensions/Print.h... yes checking for XpStartPage in -lXp... yes using Xp library checking whether to use Xt library... maybe checking where to find the Xt header files... checking X11/Intrinsic.h usability... yes checking X11/Intrinsic.h presence... yes checking for X11/Intrinsic.h... yes checking for XtAppInitialize in -lXt... yes
Re: graphics/xpdf
On Wed, Nov 15, 2006 at 01:43:19AM -0500, Jimmy Hartzell wrote: > I am at a loss for what to do, as, trying to compile graphics/xpdf, I got > the following results: > $ sudo portinstall xpdf > ---> Installing 'xpdf-3.01_3' from a port (graphics/xpdf) > ---> Building '/usr/ports/graphics/xpdf' > ===> Cleaning for freetype2-2.2.1_1 > ===> Cleaning for gmake-3.81_1 > ===> Cleaning for autoconf-2.59_2 > ===> Cleaning for t1lib-5.1.0_1,1 > ===> Cleaning for open-motif-2.2.3_2 > ===> Cleaning for xorg-libraries-6.9.0 > ===> Cleaning for gsfonts-8.11_2 > ===> Cleaning for pkg-config-0.21 > ===> Cleaning for gettext-0.14.5_2 > ===> Cleaning for perl-5.8.8 > ===> Cleaning for m4-1.4.4 > ===> Cleaning for help2man-1.36.4_1 > ===> Cleaning for libtool-1.5.22_2 > ===> Cleaning for imake-6.9.0 > ===> Cleaning for libdrm-2.0.2 > ===> Cleaning for fontconfig-2.3.2_6,1 > ===> Cleaning for libiconv-1.9.2_2 > ===> Cleaning for p5-gettext-1.05_1 > ===> Cleaning for expat-2.0.0_1 > ===> Cleaning for xpdf-3.01_3 > ===> Vulnerability check disabled, database not found > ===> Extracting for xpdf-3.01_3 > => MD5 Checksum OK for xpdf-3.01.tar.gz. > => SHA256 Checksum OK for xpdf-3.01.tar.gz. > => MD5 Checksum OK for xpdf-3.01pl2.patch. > => SHA256 Checksum OK for xpdf-3.01pl2.patch. > ===> Patching for xpdf-3.01_3 > ===> Applying distribution patches for xpdf-3.01_3 > ===> Applying FreeBSD patches for xpdf-3.01_3 > ===> xpdf-3.01_3 depends on executable in : freetype-config - found > ===> xpdf-3.01_3 depends on executable in : gmake - found > ===> xpdf-3.01_3 depends on file: /usr/local/bin/autoconf259 - found > ===> xpdf-3.01_3 depends on shared library: t1.5 - found > ===> xpdf-3.01_3 depends on shared library: freetype.9 - found > ===> xpdf-3.01_3 depends on shared library: Xm.3 - found > ===> xpdf-3.01_3 depends on shared library: X11.6 - found > ===> Configuring for xpdf-3.01_3 > checking for gcc... cc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether cc accepts -g... yes > checking for cc option to accept ANSI C... none needed > checking for library containing strerror... none required > checking whether we are using the GNU C++ compiler... yes > checking whether c++ accepts -g... yes > checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel > checking for ranlib... ranlib > checking for OS/2 (with EMX)... no > checking for DOS (with DJGPP)... no > checking how to run the C preprocessor... cc -E > checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include > checking for gethostbyname... yes > checking for connect... yes > checking for remove... yes > checking for shmat... yes > checking for IceConnectionNumber in -lICE... yes > checking for dirent.h that defines DIR... yes > checking for library containing opendir... none required > checking for gethostbyname... (cached) yes > checking select() and fd_set in sys/select.h and sys/bsdtypes.h... not needed > checking FD_ZERO and strings.h or bstring.h... not needed > checking for rewinddir... yes > checking for popen... yes > checking for mkstemp... yes > checking for mkstemps... yes > checking whether select takes fd_set arguments... yes > checking for special C compiler options needed for large files... no > checking for _FILE_OFFSET_BITS value needed for large files... no > checking for _LARGE_FILES value needed for large files... no > checking for _LARGEFILE_SOURCE value needed for large files... no > checking for fseeko... yes > checking for fseek64... no > checking for ftell64... no > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking whether to use Xpm library... maybe > checking where to find the Xpm header files... > checking X11/xpm.h usability... yes > checking X11/xpm.h presence... yes > checking for X11/xpm.h... yes > checking for XpmCreatePixmapFromData in -lXpm... yes > using Xpm library > checking whether to use Xext library... maybe > checking where to find the Xext header files... > checking X11/Xlib.h usability... yes > checking X11/Xlib.h presence... yes > checking for X11/Xlib.h... yes > checking for XextAddDisplay in -lXext... yes > using Xext library > checking whether to use Xp library... maybe > checking where to find the Xp header files... > checking X11/extensions/Print.h usability... yes > checking X11/extensions/Print.h presence... yes > checking for X11/extensions/Print.h... yes > checking for XpStart
