Make Install

Bas v.d. Wiel wrote:

> just move into the /usr/ports/xxx/xxx
> directory of your choice and type:
>
> make
> make install
> make clean
>
> there.. that's all there is to it. No downloading anything, no
> extracting.. no nothing.

Tried all this with cvsup itself. Got the port from CD, typed make, etc.,
various files were downloaded and there was a flurry of activity on the
console. When it was finished I entered the command "cvsup" and got the
response "Command not found."
 >> Stay informed about: Make Install 

<SNIP>
> That makes it very clear -- thank you, Bas. This is the overview that is
> missing from the (printed) manual. Question: if the ports system is so
> wonderful, why are there packages?

Ports will download source code and compile the app on your machine locally.
This is ok for smaller apps, but for things like KDE it could take literally
forever on a slower computer. That's what packages are for. They contain not
the source, but precompiled binaries plus information on where these
binaries should go and how to configure them. This then happens
automatically without lengthy compiles.
The advantage of the ports system is that it's usually more up to date than
packages, and you can insert compile-time optimizations or options. In the
file /etc/make.conf you can define your CPU-type so that the compiler will
take into account special features of your CPU such as MMX or SSE(2) and it
probably also compiles the binary so that it takes into account different
types and amounts of cache but I'm no expert on this so I could be wrong.
Another advantage of ports are tunable variables. I remember the instant
messenger Gaim comes with options to turn on and off support for a
spell-checker and audio by setting variables. The port will let you know
about such options first thing when you type 'make' in its directory, also
you can find it in the pkg-descr or pkg-message files that are present in
every port's directory. pkg-message isn't always there, but -descr sure is.
It offers a more detailed description of the port you're looking at.

Also a word of warning about Java (and maybe some other ports with
lincensing problems), since you seem new to FreeBSD and probably will be
installing Java for your web browser sometime in the future. There are Java
ports in the ports tree, but those involve some work because of licensing
constraints by Sun Microsystems. It involves registering at Sun's website,
downloading two large files and a third smaller file.. which is a hassle.
But once those files are in /usr/ports/distfiles you can just type 'make' in
/usr/ports/java/jdk13 and things will work fine. I emphatically advise you
not to try and install Java on FreeBSD on your own.. the hassle you have to
go through with this port is absolutely nothing compared with the pool of
problems you'll land in when you go about it on your own.

Bas
 >> Stay informed about: Make Install 

"chris319" wrote in message

> Bas v.d. Wiel wrote:
>
> Tried all this with cvsup itself. Got the port from CD, typed make, etc.,
> various files were downloaded and there was a flurry of activity on the
> console. When it was finished I entered the command "cvsup" and got the
> response "Command not found."
>
You know, it occurs to me that you're so new to FreeBSD that you probably
don't know how to find things easily. There is an utility in FreeBDS named
"locate". You can use it to find things by typing part or all of their
name. When you install something new, you can update the locate database by
typing:
% /usr/libexec/locate.updatedb
(You have to be root to do this)

Then you can type:
%locate foo and find what you're looking for.

Sometimes the list will be real long, so you might have to use "less",
another utiltity that allows you to view one page at a time. You also have
to use the "pipe" command, to send the output of the first command through
the second one. You type this:
% locate foo | less

To page up and down, hit Ctrl-F or Ctrl-B (for forward and backward
respectively).

Also, you can use "which" to find programs that are in your path. Like
this:
$ which locate

As Bas pointed out, you have to logout and back in to update your path when
you install something new - or type the absolute patch to it.


--
Paul Schmehl
pschmehl DeleteThis @sbcglobal.net
http://www.utdallas.edu/~pauls/
 >> Stay informed about: Make Install 

Paul Schmehl wrote:

> You know, it occurs to me that you're so new to FreeBSD that you probably
> don't know how to find things easily.

Some of us were born without that FreeBSD gene

Thanks for your help.
 >> Stay informed about: Make Install 

"chris319" wrote in message

> Bas v.d. Wiel wrote:
>
> > just move into the /usr/ports/xxx/xxx
> > directory of your choice and type:
> >
> > make
> > make install
> > make clean
> >
> > there.. that's all there is to it. No downloading anything, no
> > extracting.. no nothing.
>
> Tried all this with cvsup itself. Got the port from CD, typed make, etc.,
> various files were downloaded and there was a flurry of activity on the
> console. When it was finished I entered the command "cvsup" and got the
> response "Command not found."
>

oh sorry.. login again, or type 'rehash' as root to refresh the search path.
You'll get cvsup. There were no error messages of any kind?

Bas
 >> Stay informed about: Make Install 

Usage: cvsup [options] supfile [destDir]

What do I give as a supfile?

Bas v.d. Wiel wrote:

>
> "chris319" wrote in message
>
>> Bas v.d. Wiel wrote:
>>
>> > just move into the /usr/ports/xxx/xxx
>> > directory of your choice and type:
>> >
>> > make
>> > make install
>> > make clean
>> >
>> > there.. that's all there is to it. No downloading anything, no
>> > extracting.. no nothing.
>>
>> Tried all this with cvsup itself. Got the port from CD, typed make, etc.,
>> various files were downloaded and there was a flurry of activity on the
>> console. When it was finished I entered the command "cvsup" and got the
>> response "Command not found."
>>
>
> oh sorry.. login again, or type 'rehash' as root to refresh the search
> path. You'll get cvsup. There were no error messages of any kind?
>
> Bas
 >> Stay informed about: Make Install 

"chris319" wrote in message

> Usage: cvsup [options] supfile [destDir]
>
> What do I give as a supfile?

Mine is in /etc/cvsupfile. It maintains cvs uptodate with Release 4 and
ports and docs to current:

*default host=cvsup15.FreeBSD.org
*default tag=RELENG_4
*default base=/usr
*default prefix=/usr
*default release=cvs delete use-rel-suffix

src-all
ports-all tag=.
doc-all tag=.

Read the Handbook on cvsup. It's very good:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html


--
Paul Schmehl
pschmehl DeleteThis @sbcglobal.net
http://www.utdallas.edu/~pauls/
 >> Stay informed about: Make Install 

Paul Schmehl wrote:

> Mine is in /etc/cvsupfile. It maintains cvs uptodate with Release 4 and
> ports and docs to current:
>
> *default host=cvsup15.FreeBSD.org
> *default tag=RELENG_4
> *default base=/usr
> *default prefix=/usr
> *default release=cvs delete use-rel-suffix
>
> src-all
> ports-all tag=.
> doc-all tag=.

# cvsup /usr/supfile
Cannot get IP address of my own host -- is its hostname correct?
#
 >> Stay informed about: Make Install 

In article , Chris
Clementson wrote:

>Here is the epilogue to this story: the package that requires
>fontconfig as a dependency is looking for fontconfig-2.2.0.
>The version of fontconfig I managed to install after a day's
>efforts is version 2.2.1. I have no idea how to deal with this
>dilemma, or why this package won't play with a later version of
>fontconfig.

First thing to do is make sure your ports tree is uptodate.
That might fix the disrepancy.

Then you might try pkgdb -F to fix dependancies you may have
morked up along the way.

--
Bill Vermillion - bv @ wjv . com
 >> Stay informed about: Make Install 

In article ,
Paul Schmehl wrote:
>"chris319" wrote in message
>
>> Bas v.d. Wiel wrote:

>> Tried all this with cvsup itself. Got the port from CD, typed
>> make, etc., various files were downloaded and there was a
>> flurry of activity on the console. When it was finished I
>> entered the command "cvsup" and got the response "Command not
>> found."

>You know, it occurs to me that you're so new to FreeBSD that
>you probably don't know how to find things easily. There is an
>utility in FreeBDS named "locate". You can use it to find things
>by typing part or all of their name. When you install something
>new, you can update the locate database by typing:

>% /usr/libexec/locate.updatedb
>(You have to be root to do this)

>Then you can type:
>%locate foo and find what you're looking for.

>Sometimes the list will be real long, so you might have to use
>"less", another utiltity that allows you to view one page at
>a time. You also have to use the "pipe" command, to send the
>output of the first command through the second one. You type
>this:

>% locate foo | less

I just made a small script [but you can make an alias] that
called locate with the -i and then pipes it to less with the -e
option.

The -i says for located to ignore case - and this can be quite
helpful if you aren't sure of the caps in the name.

So make the alias/script like this:

locate -i @ | less -e



--
Bill Vermillion - bv @ wjv . com
 >> Stay informed about: Make Install 

In article ,
Warren Block wrote:
>Chris Clementson wrote:
>> in article slrnbftqr7.2efv.wblock.DeleteThis@w0nkity.wonkity.com, Warren Block at
>> wblock.DeleteThis@wonkity.com wrote on 6/29/03 6:36 AM:

>> You misunderstand my hypothetical. I download a port "schmozkapop". Suppose
>> there is no directory /usr/ports/schmozkapop, or can this never happen if
>> the ports system is kept up to date in which case it would have to know
>> about every port in existence?

>It does know about every port in existence, about seven or eight
>thousand of them. Keeping the ports system up to date brings in new
>ports and updates old ones.

As of last count there are 8866 in the current tree. Heading for
9000 RSN.

Bill
--
Bill Vermillion - bv @ wjv . com
 >> Stay informed about: Make Install 

I ran the sample script Paul posted and the result is:

# cvsup /usr/supfile
Cannot get IP address of my own host -- is its hostname correct?
#
 >> Stay informed about: Make Install 

"chris319" wrote in message

> I ran the sample script Paul posted and the result is:
>
> # cvsup /usr/supfile
> Cannot get IP address of my own host -- is its hostname correct?
> #
>
You have *got* to start reading the documentation.

First of all, you run cvsup from the commandline like this:
/usr/local/bin/cvsup -g -L 2 /usr/supfile

Now, if you're going to run the same supfile I posted, I *hope* you are
running FreeBSD 4.x RELEASE. Otherwise that file is wrong and will get the
wrong sources for your box.

Secondly, if the machine can't resolve its own IP, you're not going to get
very far.

What do you have in the following files (please copy and paste them here.
Type "grep -v "#" <filename> to get the contents without comments):
/etc/hosts
/etc/rc.conf

--
Paul Schmehl
pschmehl RemoveThis @sbcglobal.net
http://www.utdallas.edu/~pauls/
 >> Stay informed about: Make Install