|
FreeBSD Ports and Packages Installation and upgrading of ports and packages on FreeBSD. |
|
Thread Tools | Display Modes |
|
|||
package questions
I know it's vacation seasons so this is a shout-out to the first person who knows what's going on here. I just got use to pkg_add a few weeks ago when I was using plain old FreeBSD at the command-line but for the pass few weeks this set-up is all about making a real effort to use PcBSD and now I see that files are everywhere compared to the tiny FreeBSD, i miss it already. I tried to install GNOME but dependencies needed dependencies, so I drop the ball on that one, but I did learn how to use pkg_add well but not to oblivion. Just trying to give you a clearer picture.
My question is what do GNOME want and where do he want me to put it? Also is bonnie++-1.03e installed correctly? One more thing, I found this at FreeBSD download, is this the same kind of program "bonnie++1.96_1.tbz"? ... I can't find it at the official ZCAV site. Should I install this one since it got a higher version number? Sorry for being such a noob but I'm in it for good now and I want to complete this process and record those numbers. I found my PRIMARY now I want to know the slices, and than I'm optimize after I optimize. Any way if some one could explain this to me I will never forget. I don't know why it say this when the directory already got the file name in it: /Programs/Gnome/lib/liblzma.so.5: ... this dir has a liblzma.so.5 already And what is XZ_5.0 and of what? /usr/lib/libarchive.so.5 ... libarchive.so.5 is in here already ........ ........ ........ This is what I got when I tried to install gnuplot-4.4.3.tar.gz: bash-4.1# tar -zxvf /var/AAA/gnuplot-4.4.3.tar.gz -C /usr/tools/gnuplot /libexec/ld-elf.so.1: /Programs/Gnome/lib/liblzma.so.5: version XZ_5.0 required by /usr/lib/libarchive.so.5 not defined bash-4.1# I installed bonnie++-1.03e.tgz first, and this is what I got: bash-4.1# ./configure checking for g++... g++ 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 g++ accepts -g... yes checking how to run the C++ preprocessor... g++ -E checking for a BSD-compatible install... /usr/bin/install -c checking for an ANSI C-conforming const... yes checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/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 for size_t... yes checking vector.h usability... yes checking vector.h presence... yes checking for vector.h... yes checking vector usability... yes checking vector presence... yes checking for vector... yes checking algorithm usability... yes checking algorithm presence... yes checking for algorithm... yes checking algo.h usability... yes checking algo.h presence... yes checking for algo.h... yes checking algo usability... no checking algo presence... no checking for algo... no configure: creating ./config.status config.status: creating Makefile config.status: WARNING: Makefile.in seems to ignore the --datarootdir setting config.status: creating bonnie.h config.status: creating port.h config.status: creating bonnie++.spec config.status: creating bon_csv2html config.status: creating bon_csv2txt config.status: creating sun/pkginfo config.status: creating conf.h config.status: conf.h is unchanged bash-4.1# |
|
|||
Your message has been split from its original thread because the questions posed here are exclusively pertaining to packages/third-party applications & not related to dd(1) or disk performance.
The majority of our site members use the search facility to find related (old) threads. Mixing topics within a single thread makes searching more difficult. |
|
|||
That's fine! It makes good since to me. Sorry about that ocicat. Anyway, your chosen title along tells me to google and study how the package system work. I never thought about that until now. I do it for everything else. One thing I learn about BSD, every tiny step can be a major learning process. By time we get to the good part it be history with a whole new set of rules (technologies) to start from scratch all over again.. I hope I don't crack.
Thanks |
|
|||
I move this to a new thead...
Last edited by sharris; 4th July 2011 at 06:30 PM. Reason: PS: |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
What came first: the port or the package? | rpindy | General software and network | 4 | 27th June 2010 11:15 PM |
NetBSD package searching ? | mgreen | NetBSD General | 5 | 30th January 2010 11:27 AM |
tcpdump package | bsdnewbie999 | OpenBSD Packages and Ports | 6 | 30th March 2009 05:24 PM |
What Open Source package shall I run? | satimis | Off-Topic | 2 | 2nd June 2008 12:43 PM |
OpenJDK package | aleunix | OpenBSD Packages and Ports | 2 | 2nd June 2008 07:54 AM |