Date: Thu, 13 Feb 2014 19:22:25 -0800 (PST) From: Robert English <drakcap@pacbell.net> To: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Cc: Randy Pratt <bsd-unix@embarqmail.com> Subject: Re: Update for graphics/libopenraw failed Message-ID: <1392348145.8286.YahooMailNeo@web181105.mail.ne1.yahoo.com>
next in thread | raw e-mail | index | archive | help
Had a similar problem on my 8.4-Release system. After looking at the "config.log" file, figured out it was looking for "libboost_unit_test_framework_gcc42.so" so I made a soft link in the "usr/local/lib" directory with that name pointing to the "libboost_unit_test_framework.so.1.55.0" file. Libopenraw compiled fine after that. Putting this on the server in case someone else has this problem also. Bob On Feb 10, Randy Pratt wrote: >The system is an 8.4-STABLE/i386. > >Excerpt from the entire http://myfreebsd.homeunix.net/libopenraw-0.0.8_5.log : >---------------------------------------------------- >checking boost/test/unit_test.hpp presence... yes >checking for boost/test/unit_test.hpp... yes >checking for the Boost unit_test_framework library... no >configure: error: Could not find the flags to link with Boost unit_test_framework >===> Script "configure" failed unexpectedly. >----------------------------------------------------- > >The libs seem to be there and were were updated: >/usr/local/lib/libboost_unit_test_framework.a >/usr/local/lib/libboost_unit_test_framework.so -> libboost_unit_test_framework.so.1.55.0 >/usr/local/lib/libboost_unit_test_framework.so.1.55.0 >/usr/local/lib/libboost_unit_test_framework.so.5 -> libboost_unit_test_framework.so.1.55.0 > >The entire update log URL is: >http://myfreebsd.homeunix.net/updates/ports/ports-2014.02.09.0606.log > > 8==snipped From owner-freebsd-ports@FreeBSD.ORG Fri Feb 14 04:29:04 2014 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F342638 for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 04:29:04 +0000 (UTC) Received: from mail1.bur200.uecomm.net.au (mail1.bur200.uecomm.net.au [218.185.0.70]) by mx1.freebsd.org (Postfix) with ESMTP id 0B22A1B45 for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 04:29:03 +0000 (UTC) Received: from mail.fdrive.com.au (unknown [115.186.196.106]) by mail1.bur200.uecomm.net.au (Postfix) with ESMTP id D5950D4F1 for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 15:10:41 +1100 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.fdrive.com.au (Postfix) with ESMTP id 757EBE5E0F for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 15:11:32 +1100 (EST) X-Virus-Scanned: amavisd-new at fdrive.com.au Received: from mail.fdrive.com.au ([127.0.0.1]) by localhost (mail.fdrive.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8C3VO7ru6z4w for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 15:11:29 +1100 (EST) Received: from PetersBigBox (ws-pross.vv.fda [192.168.50.199]) by mail.fdrive.com.au (Postfix) with ESMTPS id 74603E62CF for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 15:11:29 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by PetersBigBox (Postfix) with ESMTP id DE383192037F for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 15:10:08 +1100 (EST) Date: Fri, 14 Feb 2014 15:10:08 +1100 (EST) From: Peter Ross <Peter.Ross@alumni.tu-berlin.de> X-X-Sender: petros@PetersBigBox To: freebsd-ports@freebsd.org Subject: Pkg install from release CD using FreeBSD provided repo Message-ID: <alpine.DEB.2.02.1402141424190.10005@PetersBigBox> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 14 Feb 2014 04:29:04 -0000 Hi, after having a +1 from a German mailing list and the suggestion to send it to the appropriate mailing list (I think freebsd-ports is the one?) a suggestion for the installation from CD 1. Include a local binary way to install pkg 2. Ask for a proxy server when setting up a new FreeBSD machine (write it in the environment section of pkg.conf as well as setting the http_proxy environment variable) 3. Ask whether you want to use binary packages and write a FreeBSD.conf for the appropriate repository to download from 4. Download the content from the repo at the first pkg command so commands as "pkg search" work immediately. Point 2, 3 and 4 sound quite "trivial", I think, it is more of whether it is the right way to do. For step 1 I provide a "minimal ports tree" with all what's needed to compile pkg. See below for details. I suggest it after my own install experience for FreeBSD 10.0. I am a sysadmin who is using the ports collection for our servers, whoever, this time I wanted to try a binary install for a desktop, I found it too cumbersome, as a novice I would have given up.. Sitting in the office (and behind a firewall and having a proxy) I wanted to setup a new desktop. Shiny new pkg tools - better than apt.. cool! Yes, it works well, much better than the old stuff. Thanks! Okay, do I need ports? No (I think - I want binaries). I just use pkg afterwards. Good. Problem 1: pkg is just the stub.. and wants to get it from a FreeBSD server.. well - stuck (the firewall) Well, I guess "http_proxy=..; export http_proxy" may help - yes, it does. (But I am a sysadmin - what if I do not have this knowledge?) Problem 2: "pkg search perl" - nothing. Google, google.. okay, the announcement and writing a repository configuration. Problem 3: ""pkg search perl" - still no output. pkg repo/upgrade/update/updating.. all: no. Looking at the repo website: Yes, it's there. "pkg install 0verkill" (the first package I see - magic, it downloads the repository content and more, and now "pkg search" and others work! Thay are all problems you can solve. But I do not think they should be the first FreeBSD experience. Another mailing list member had a similar disappointing start with FreeBSD 10. Hence the suggestion above. What do you think? Sorry if I am stirring the pot again.. I found some "mails related to the pkg stub but I did not find something similar to my suggestion. I am happy for any other way that may prevent an experience as I just had. Here my workaround to bootstrap ppkg locally (tested for FreeBSD 9): 1. create_pkg_bootstrap.sh # Creates bootstrap package used by add_packages.sh # Assumes succesful pkg build in ports tree # Parameter: pkg name (pkg-${version}) if [ "X${1}" = "X" ]; then echo "Please specify pkg name (pkg-version)" exit 1 fi cd /usr/ports rm -f /usr/ports/ports-mgmt/pkg/work/.install_done.pkg._usr_local tar -czf /usr/ports/packages/$1.tgz ports-mgmt/pkg Mk \ Templates/BSD.local.dist Tools/scripts/security-check.awk 2. Use the pkg tar ball to install pkg bootstrap_pkg() { echo "Bootstrap pkg" tmp_ports_dir=`mktemp -d /tmp/${APP}.ports.XXXXXX` cd ${tmp_ports_dir} tar -xzvf /usr/ports/packages/pkg*.tgz cd ports-mgmt/pkg make install PORTSDIR=${tmp_ports_dir} echo "Packages installed: " pkg info -a rm -rf ${tmp_ports_dir} } I am pretty sure that may need some polish before it can grace an official installation CD (or there is something better).. but it may be a starting point. Regards Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1392348145.8286.YahooMailNeo>