Re: FreeBSD ports: 2 unfetchable distfiles: devel/freebase, irc/ircg
Hi Bill, devel/freebase is a repocopy of devel/freeride and doesn't describe any own distfiles or distfile sources. So how it's possible that -- freebase cvs tree / pkg-descr URL from pkg-descr: http://freeride.rubyforge.org/wiki/wiki.pl ok File: freeride-0.9.6.tar.gz has 4 possible URLs: 0 OK, 4 bad, 0 skipped Port maintainer: [EMAIL PROTECTED] http://rubyforge.rubyuser.de/freebase/freeride-0.9.6.tar.gz: 404 Not Found (Last OK result NEVER [checked 10 times since Sat Aug 12 09:47:40 2006 UTC, last time was Sat Sep 2 18:48:55 2006 UTC]) http://rubyforge.iasi.roedu.net/files/freebase/freeride-0.9.6.tar.gz: 404 Not Found (Last OK result NEVER [checked 10 times since Fri Aug 11 10:28:39 2006 UTC, last time was Sat Sep 2 02:12:37 2006 UTC]) http://rubyforge.halostatue.info/freebase/freeride-0.9.6.tar.gz: 404 Not Found (Last OK result NEVER [checked 10 times since Sat Aug 12 17:13:27 2006 UTC, last time was Sun Sep 3 05:27:02 2006 UTC]) http://files.rubyforge.vm.bytemark.co.uk/freebase/freeride-0.9.6.tar.gz: 404 Not Found (Last OK result NEVER [checked 10 times since Fri Aug 11 23:15:59 2006 UTC, last time was Sat Sep 2 11:40:23 2006 UTC]) Summary 0 files fetchable out of 1 --- freeride cvs tree / pkg-descr URL from pkg-descr: http://freeride.rubyforge.org/wiki/wiki.pl ok File: freeride-0.9.6.tar.gz has 4 possible URLs: All OK! Summary 1 files fetchable out of 1 ? Probably you've got some local network problems when tried to fetch from freebase, and they gone to the freeride time? WBR, Alexander Novitsky freebase/freeride port maintainer >Dear [EMAIL PROTECTED], > > You are listed as the FreeBSD port maintainer for 2 ports >whose distfiles are not fetchable from their MASTER_SITES. Could >you please visit > >http://people.freebsd.org/~fenner/portsurvey/[EMAIL PROTECTED] > >and correct the problems listed there? The individual ports with >problems are devel/freebase,irc/ircg. > > If you have already corrected the problems and submitted a >PR, please accept my thanks and apologies for the delay in getting >the fixes into the tree. This reminder is created automatically >and does not (yet) have a way to know if a PR fixing the problem >has been submitted. Please do *NOT* send your response to me >directly; I do not necessarily have time to commit your fix; please >instead submit a PR via 'send-pr' so it doesn't get lost. > > Problems are usually of two types: >1. The software package has been upgraded and the version in the >port has been removed. The best solution to this problem is to >upgrade the port to the most current version of the software package. >If you are a FreeBSD committer, then you can just upgrade the port >directly. If not, you should create the updated port on your own machine, >test it (and maybe even run "portlint" on it), and then use "send-pr" >to submit a "diff -uNr old-port updated-port". If you added or deleted >any files, please make an explicit note of it. > >2. The mirror site being used no longer contains the software package >in question, or no longer exists. Solutions include: > a) If there are other mirror sites, just remove the bad site > from the list. (Make sure that what appears to be a bad site > isn't actually a problem of type 1, upgrade) > b) If the README or other support files in the software > documentation mention where to get the software package, > use one of those sites. > c) Use a search engine to find another place to get the original > DISTFILES. Make sure that you don't pick a FreeBSD distfiles > mirror -- if you can't find any other places where the file > exists, it can be a LOCAL_PORT or you can simply comment out > the MASTER_SITES= line, with a comment explaining why. >Once you have a solution, use "send-pr" to submit a "diff -u" of the >Makefile. > > Note that this isn't an urgent issue, as people who try to >build the port now will just fall back to the FreeBSD distfiles mirror. >Please just put it on your list to do and get to it when you have time. >These messages will continue to arrive twice a month until the fix is >committed, as a reminder. > >Thanks, > Bill "distfiles" Fenner. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: jboss-4.0.4.GA,1
Hi Mister, I installed jboss on freebsd but want to know: The application server's "root directory" Is that /usr/local/jboss4/server directory? For a application I need to install something to a directory that is a sibling of the application server's "root directory. Thanks Brgds signature.asc Description: This is a digitally signed message part
"make: don't know how to make clean." in math/wxmaxima
This is kind of strange:
/usr/ports/math/wxMaxima> sudo make clean
===> Cleaning for pkg-config-0.20_3
===> Cleaning for wxgtk2-unicode-2.6.3
===> Cleaning for gettext-0.14.5_2
===> Cleaning for libxml2-2.6.26
===> Cleaning for maxima-5.9.3
===> Cleaning for gmake-3.81_1
===> Cleaning for gstreamer-plugins80-0.8.12_3
===> Cleaning for intltool-0.35.0
===> Cleaning for png-1.2.12_1
===> Cleaning for jpeg-6b_4
===> Cleaning for tiff-3.8.2
===> Cleaning for expat-2.0.0_1
===> Cleaning for libmspack-0.0.20040308_3
===> Cleaning for libiconv-1.9.2_2
===> Cleaning for atk-1.11.4_1
===> Cleaning for glib-2.10.3
===> Cleaning for gtk-2.8.20
===> Cleaning for pango-1.12.3
===> Cleaning for xorg-libraries-6.9.0
===> Cleaning for wxgtk2-common-2.6.3
===> Cleaning for libtool-1.5.22_2
===> Cleaning for automake-1.9.6
===> Cleaning for autoconf-2.59_2
===> Cleaning for tk-8.4.13,2
make: don't know how to make clean. Stop
*** Error code 2
Stop in /usr/ports/math/wxMaxima.
*** Error code 1
Stop in /usr/ports/math/wxMaxima.
I never experienced this before.
P.S. The port should also be fixed to use
USE_WX= 2.6
WX_UNICODE= yes
instead of defining
WXGTK_CONFIG?=${X11BASE}/bin/wxgtk2u-2.6-config
manually
--jona
___
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: jboss-4.0.4.GA,1
On Sun, Sep 03, 2006 at 06:12:12PM +0200, Robert Gilaard wrote: > Hi Mister, > > I installed jboss on freebsd but want to know: > > The application server's "root directory" > > Is that /usr/local/jboss4/server directory? That would be /usr/local/jboss4/server/default, assuming that your application is deployed in the default server. Cheers. -- Jonathan Chen <[EMAIL PROTECTED]> -- "You can get farther with a kind word and a gun than you can with a kind word alone" - Al Capone ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
issues with acroread7 and pango
on Sat Jan 7 20:58:35 PST 2006 Brandon Fosdick reported than he can't acroread7 port to work because it try to use the native pango library. Does this problem solved? I can't found another post about this. -- regis [ Sorry the thread don't work from web interface it was In reply to: Message-ID: <[EMAIL PROTECTED]> ] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fam configure error
Hi, Upgrading to the latest fam (devel/fam) konks out in configure. checking whether cc accepts -g... yes checking for cc option to accept ANSI C... none needed checking dependency style of cc... none checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes ./ltconfig: Can't open ./ltconfig: No such file or directory configure: error: libtool configure failed ===> Script "configure" failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the "/usr/ports/devel/fam/work/fam-2.6.10/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/devel/fam. I've attached the whole build output and the config.log file. Anyone else see this problem? -lee fam_build_failure Description: Binary data This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.59. Invocation command line was $ ./configure --prefix=/usr/local --build=i386-portbld-freebsd5.4 ## - ## ## Platform. ## ## - ## hostname = spock.dilkie.com uname -m = i386 uname -r = 5.4-RELEASE-p16 uname -s = FreeBSD uname -v = FreeBSD 5.4-RELEASE-p16 #0: Wed Jun 21 21:56:19 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SPOCK /usr/bin/uname -p = i386 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/libexec/automake19 PATH: /usr/local/libexec/autoconf259 PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/games PATH: /usr/local/bin PATH: /usr/local/sbin PATH: /usr/X11R6/bin PATH: /root/bin ## --- ## ## Core tests. ## ## --- ## configure:1361: checking for a BSD-compatible install configure:1416: result: /usr/bin/install -c -o root -g wheel configure:1427: checking whether build environment is sane configure:1470: result: yes configure:1494: WARNING: `missing' script is too old or missing configure:1535: checking for gawk configure:1564: result: no configure:1535: checking for mawk configure:1564: result: no configure:1535: checking for nawk configure:1551: found /usr/bin/nawk configure:1561: result: nawk configure:1571: checking whether gmake sets $(MAKE) configure:1591: result: yes configure:1835: checking build system type configure:1853: result: i386-portbld-freebsd5.4 configure:1861: checking host system type configure:1875: result: i386-portbld-freebsd5.4 configure:1924: checking for ranlib configure:1940: found /usr/bin/ranlib configure:1951: result: ranlib configure:1975: checking for style of include used by gmake configure:2003: result: GNU configure:2074: checking for gcc configure:2100: result: cc configure:2344: checking for C compiler version configure:2347: cc --version &5 cc (GCC) 3.4.2 [FreeBSD] 20040728 Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:2350: $? = 0 configure:2352: cc -v &5 Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.4.2 [FreeBSD] 20040728 configure:2355: $? = 0 configure:2357: cc -V &5 cc: `-V' option must have argument configure:2360: $? = 1 configure:2383: checking for C compiler default output file name configure:2386: cc -O -pipe -Wno-deprecated conftest.c >&5 cc1: warning: command line option "-Wno-deprecated" is valid for C++/ObjC++ but not for C configure:2389: $? = 0 configure:2435: result: a.out configure:2440: checking whether the C compiler works configure:2446: ./a.out configure:2449: $? = 0 configure:2466: result: yes configure:2473: checking whether we are cross compiling configure:2475: result: no configure:2478: checking for suffix of executables configure:2480: cc -o conftest -O -pipe -Wno-deprecated conftest.c >&5 cc1: warning: command line option "-Wno-deprecated" is valid for C++/ObjC++ but not for C configure:2483: $? = 0 configure:2508: result: configure:2514: checking for suffix of object files configure:2535: cc -c -O -pipe -Wno-deprecated conftest.c >&5 cc1: warning: command line option "-Wno-deprecated" is valid for C++/ObjC++ but not for C configure:2538: $? = 0 configure:2560: result: o configure:2564: checking whether we are using the GNU C compiler configure:2588: cc -c -O -pipe -Wno-deprecated conftest.c >&5 cc1: warning: command line option "-Wno-deprecated" is valid for C++/ObjC++ but not for C configure:2594: $
Re: fam configure error
On Sun, 03 Sep 2006 17:42:42 -0400 Lee Dilkie <[EMAIL PROTECTED]> mentioned: > Hi, > > Upgrading to the latest fam (devel/fam) konks out in configure. > > checking whether cc accepts -g... yes > checking for cc option to accept ANSI C... none needed > checking dependency style of cc... none > checking for ld used by GCC... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD-compatible nm... /usr/bin/nm -B > checking whether ln -s works... yes > ./ltconfig: Can't open ./ltconfig: No such file or directory > configure: error: libtool configure failed > ===> Script "configure" failed unexpectedly. > Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the > "/usr/ports/devel/fam/work/fam-2.6.10/config.log" including the output > of the > failure of your make command. Also, it might be a good idea to provide an > overview of all packages installed on your system (e.g. an `ls > /var/db/pkg`). > *** Error code 1 > > Stop in /usr/ports/devel/fam. > > I've attached the whole build output and the config.log file. > > Anyone else see this problem? > > -lee Thats because of the stale file left by old libtool13 port. You should remove /usr/local/share/aclocal/libtool13.m4 and probably, reinstall devel/libtool15 port. -- Stanislav Sedov MBSD labs, Inc. <[EMAIL PROTECTED]> Россия, Москва http://mbsd.msk.ru If the facts don't fit the theory, change the facts. -- A. Einstein PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 signature.asc Description: PGP signature
Re: issues with acroread7 and pango
On Sun, 3 Sep 2006 23:37:48 +0200 regisr wrote: > on Sat Jan 7 20:58:35 PST 2006 > Brandon Fosdick reported than he can't acroread7 port to work because > it try to use the native pango library. > Does this problem solved? I can't found another post about this. Firts of, consider reading /usr/ports/UPDATING "20060616: AFFECTS users of emulation/linux_base-*". If none of suggestions help you than write your results here. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Building a port for an X11 hardware driver
I've recently bought a a VIA K8M890-based motherboard. This chip set has onboard VGA, but it's not supported by X.org or XFree86 (well, the vesa driver recognizes it, but that's not saying much). On the other hand, VIA has X.org drivers for it in source form, which for some reason X.org has not incorporated into the distribution. So it makes sense to port them. Problem: how do I do that? The most obvious approach is to extract x11-servers/xorg-server and replace the via driver with the VIA code. But that sounds tacky. My understanding of the Ports Collection is not really up to this task. If somebody wants to take over the project, feel free. Otherwise I'd be grateful for some hand-holding. The source tarball is at http://www.viaarena.com/Driver/k8m800_890-p4m890xf41068-kernel-src_20060707.tgz (and yes, though the name suggests that the drivers are for XFree86, the accompanying documentation (src/ReleaseNotes.txt) talks of X.org). There's also another, less powerful package at http://www.viaarena.com/Driver/k8m890xf40069-kernel-src_20060620.tgz. See also http://www.viaarena.com/default.aspx?PageID=420&OSID=25&CatID=2580&SubCatID=164 for some minimal documentation. Greg -- See complete headers for address and phone numbers. pgpnAG9Y0sfSl.pgp Description: PGP signature
