Make Install

> Normally what you would do is this:
>
> # whereis fontconfig
> fontconfig: /usr/ports/x11-fonts/fontconfig

OK now what if /usr/ports/whatever doesn't already exist on my system?
Suppose it is something I just downloaded to my little directory somewhere?
I would think whereis is going to return with whereaint.

Through my own little trial-and-error system I was able to get make install
to do something. Unfortunately now the system is aware of the existence of
fontconfig but the package that depends on it is not. I tried to uninstall
and reinstall fontconfig but was unable to due to something about the lack
of a prefix.

I am composing this message on my Macintosh after killing an entire day
trying to resolve dependencies for one little app that I wanted to install.
An operating system that's this much of a headache probably isn't something
I want to deal with anyway, and it's just going to drive me and millions of
others back to Windows. At least that's my line of thinking after killing an
entire day on this with no joy. I could have taken a nice day trip to San
Diego instead.
 >> Stay informed about: Make Install 

In article , Chris Clementson wrote:
>> Normally what you would do is this:
>>
>> # whereis fontconfig
>> fontconfig: /usr/ports/x11-fonts/fontconfig
>
> OK now what if /usr/ports/whatever doesn't already exist on my system?
> Suppose it is something I just downloaded to my little directory somewhere?
> I would think whereis is going to return with whereaint.

If you have no ports on your system, you either fix that (cvsup) or install
the package instead:
pkg_add -r fontconfig
If there is no port availible, you're pretty much on your own...
<snip>
> others back to Windows. At least that's my line of thinking after killing an
> entire day on this with no joy. I could have taken a nice day trip to San
> Diego instead.

Making it easy is what ports is all about. If you refuse to use them, things
will be tricky. Compare it to installing MS Office without using the installer
in Windows. I'll bet it's possible, but you'll kill a day or two...

--
Erik Nygren
e r i k { a t } s w i p { d o t } n e t
Linux - If you hate Microsoft, FreeBSD - If you love Unix
 >> Stay informed about: Make Install 

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.

> You need to back up a couple of steps and decide whether you want the
> port (to compile from source) or the package (precompiled object code).

There is no decision to make. Fontconfig comes in one flavor: port. I was
able to get 12 packages installed without problem.

> Open a terminal, cd to the directory where your downloaded file is.
>
> type: tar xvf fontconfig.tar
>
> this'll give you a new subfolder containing the files for fontconfig.
>
> in this subfolder, type: ./configure --prefix=/usr/local
> then type: make
> then, as root, type: make install

This is similar to my trial and error approach: First, copy the downloaded
tar.gz to /usr/ports/distfiles. Then, using Konqueror I right clicked on the
downloaded file (not the copy in /usr/ports/distfiles) and chose "Extract
here". It made the subdirectory you refer to. Using the terminal I went to
the new subdirectory and typed "make". I then got a blur of output in the
terminal. When finished I typed "make install" and got another blur of
output. Fontconfig seems to be installed but it's a version the other
package doesn't want.

> Compare it to installing MS Office without using the installer
> in Windows. I'll bet it's possible, but you'll kill a day or two...

I have the ports system fully installed and am not intentionally trying to
circumvent it. The FreeBSD Handbook is nigh worthless so forget about RTFB.
This leaves me on my own with the help of the kind souls on Usenet. I can't
remember ever having a Windows program fail to install and run by executing
the installer, or having to fetch a file from an outside source.
 >> Stay informed about: Make Install 

chris319 wrote:
> I have downloaded fontconfig.tar.gz from the Internet.

Is it a package or a port?

> I put it in its own
> directory. Using Konqueror I double click on the .tar.gz file and another
> pane appears with files, distinfo, Makefile, pkg-descr and pkg-plist. In
> the console I cd to the fontconfig directory and type "make". I get the
> response "make: no target to make.". I then type "make fontconfig.tar.gz"
> and get "'fontconfig.tar.gz' is up to date." I type "make install" and get
> "make: don't know how to make install. Stop".

Make works on Makefiles. If you haven't untarred the archive, no
Makefile is present.

> I type "gzip -d fontconfig.tar.gz" and go through the above steps with
> same results. I re-read the FreeBSD Handbook which provides no
> insight.

You need to back up a couple of steps and decide whether you want the
port (to compile from source) or the package (precompiled object code).

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Make Install 

Chris Clementson wrote:

> OK now what if /usr/ports/whatever doesn't already exist on my system?
> Suppose it is something I just downloaded to my little directory somewhere?
> I would think whereis is going to return with whereaint.

Of course. If you don't have the ports system, you can't use the ports
system.

You should look at 'man pkg_add'.

> I am composing this message on my Macintosh after killing an entire day
> trying to resolve dependencies for one little app that I wanted to install.
> An operating system that's this much of a headache probably isn't something
> I want to deal with anyway, and it's just going to drive me and millions of
> others back to Windows.

You are circumventing the system (two systems, actually) which is there
to help you with dependencies. If you want to make it a headache, you
picked the right way.

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Make Install 

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

>> OK now what if /usr/ports/whatever doesn't already exist on my system?
>> Suppose it is something I just downloaded to my little directory somewhere?
>> I would think whereis is going to return with whereaint.
>
> Of course. If you don't have the ports system, you can't use the ports
> system.

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?

> You are circumventing the system (two systems, actually) which is there
> to help you with dependencies. If you want to make it a headache, you
> picked the right way.

Spare me the lecture. What am I to do when the documentation is of no use?
 >> Stay informed about: Make Install 

In article ,
Chris Clementson wrote:
>> Normally what you would do is this:
>>
>> # whereis fontconfig
>> fontconfig: /usr/ports/x11-fonts/fontconfig
>
>OK now what if /usr/ports/whatever doesn't already exist on my system?
>Suppose it is something I just downloaded to my little directory somewhere?
>I would think whereis is going to return with whereaint.

>Through my own little trial-and-error system I was able to get
>make install to do something. Unfortunately now the system
>is aware of the existence of fontconfig but the package that
>depends on it is not. I tried to uninstall and reinstall
>fontconfig but was unable to due to something about the lack of
>a prefix.

>I am composing this message on my Macintosh after killing an
>entire day trying to resolve dependencies for one little app
>that I wanted to install. An operating system that's this much
>of a headache probably isn't something I want to deal with
>anyway, and it's just going to drive me and millions of others
>back to Windows. At least that's my line of thinking after
>killing an entire day on this with no joy. I could have taken a
>nice day trip to San Diego instead.

It sounds like perhaps you didn't take the typical defaults when
you installed FreeBSD. There is a question asking about installing
the ports tree and it is flagged as recommended.

Default installs and then the following updates are quite easy.
It surely beats windows installs IMO.

Did you take the defaults - or try to change things without
understanding what you were changing. Without a description of how
you installed it we are all just going to be guessing.



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

quoting words of Bill Vermillion:
> In article ,
> Chris Clementson wrote:

>>I am composing this message on my Macintosh after killing an entire
>>day trying to resolve dependencies for one little app that I wanted to
>>install. An operating system that's this much of a headache probably
>>isn't something I want to deal with anyway, and it's just going to
>>drive me and millions of others back to Windows.

You SHOULD have read and DO what was adviced.
You do NOT download and find out dependencies yourself.
There is no need too. You install the ports collection, portupgrade and
all'll be taken care off. Blaming the OS for your own lack of attention
is not right imho.

>>At least that's my line of thinking after killing an entire day on
>>this with no joy. I could have taken a nice day trip to San Diego
>>instead.

You could have. And while doing so, yoy could also have read some info
on FreeBSD concerning installation. It really bothers me the way you
blame the OS, while it's all you're onw fault, really.

> It sounds like perhaps you didn't take the typical defaults when you
> installed FreeBSD. There is a question asking about installing the
> ports tree and it is flagged as recommended.
>
> It surely beats windows installs IMO.
>
> Did you take the defaults - or try to change things without
> understanding what you were changing.

I left some wise words of Bill, who is much more "understanding" than
me. Maybe you -(Chris Clementson)- can find some help in them.

--
dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.8 ++ Debian GNU/Linux (Woody)
 >> Stay informed about: Make Install 

"chris319" wrote in message

> I have downloaded fontconfig.tar.gz from the Internet. I put it in its own
> directory. Using Konqueror I double click on the .tar.gz file and another
> pane appears with files, distinfo, Makefile, pkg-descr and pkg-plist. In
> the console I cd to the fontconfig directory and type "make". I get the
> response "make: no target to make.". I then type "make fontconfig.tar.gz"
> and get "'fontconfig.tar.gz' is up to date." I type "make install" and get
> "make: don't know how to make install. Stop". I type "gzip -d
> fontconfig.tar.gz" and go through the above steps with same results. I
> re-read the FreeBSD Handbook which provides no insight.
>
> ???

Open a terminal, cd to the directory where your downloaded file is.

type: tar xvf fontconfig.tar

this'll give you a new subfolder containing the files for fontconfig.

in this subfolder, type: ./configure --prefix=/usr/local
then type: make
then, as root, type: make install

That should do the trick most of the time, but you're MUCH better off using
the ports system or packages. You can get the ports system at install time,
or you can cvsup it later but for that you'd need the cvsup package.
The installer is available at /stand/sysinstall so you can easily install
the cvsup package with which to download a fresh ports collection. Go to the
'configure' menu, then 'packages', 'devel' and check cvsup.

To update your ports:
Go to /usr/share/examples/cvsup and edit ports-supfile so that the
cvs-server it looks for is a mirror close to you. I personally use
cvsup.nl.freebsd.org since I'm from the Netherlands. The instructions on how
to do this are at the start of the file.

Once that's done, assuming you're running from an X session, you can fire up
the process as follows:

cvsup ports-supfile

from your terminal. Do make sure you're root (su to root, you are in the
'wheel' group, right?) for this step though!

You'll get a window that's mostly pink with a green 'play' button in the
lower left. Hit that, sit back and wait for the process to finish.

Now you have a fresh ports tree in /usr/ports from where you can install
many apps and system components simply by moving into the directory of your
choice from a terminal (as root) and doing the following:

make
make install
make clean

And that's all there is to it. Ports figures out dependencies and
cooperation with other ports on your system for you. Only if an app is not
in Ports should you try to install it manually but most popular apps are
already in Ports.

Considering your remark about driving people back to Windows: BSD isn't
there to take over the world or topple Windows, it's a rock-solid UNIX
(sorry SCO) for x86 that's only trying to get better at being a UNIX.
Nothing more nothing less. I'll admit it's daunting if you're coming from a
Mac, but that's the price you pay for complete openness. Once you learn your
way around it, it makes a great OS for many purposes.. even as a desktop.
Forgetting what you know about MacOS or Windows was the hardest part for me
when I started with FreeBSD. Now I have 5 x86 computers of which only 1 runs
Windows anymore, the rest is on FreeBSD.

hope this helps,

Bas
 >> Stay informed about: Make Install 

"Chris Clementson" wrote in message

>
> 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?
>
Right here is where you screwed up. If you have the port directory already,
just go to the directory and type:
% make

If you don't have the directory in your ports collection, then it's not up
to date. Use /stand/sysinstall or cvsup to update your ports collection.
(See the URL below for precise instructions.)

If you don't have the port or **any** of its dependencies, it will download
those, make and install those and then make your port. You're trying to do
manually what's been already automated for you.

> > You are circumventing the system (two systems, actually) which is there
> > to help you with dependencies. If you want to make it a headache, you
> > picked the right way.
>
> Spare me the lecture. What am I to do when the documentation is of no use?
>
What documentation is of no use? This?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html

FreeBSD has the *best* documentation I've ever seen for Unix. If you think
*this* is frustrating, try learning Solaris or AIX. If you're brand new to
Unix, you're going to struggle for a while. It comes with the territory.
If you're not prepared for that, or don't want to deal with it, then you're
going to be frustrated forever.

You can get all the help you need right here, but don't start by dissing the
OS or its documentation until you're *sure* the problem isn't *you*.

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

in article IgFLa.949$Jp6.371906669@newssvr12.news.prodigy.com, Paul Schmehl
at pschmehl.DeleteThis@sbcglobal.net wrote on 6/29/03 10:23 AM:

> What documentation is of no use? This?
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html

The printed version of that. Section 4.5.1 Obtaining the Ports Collection is
missing altogether from the printed version (now in its second edition) and
is instead Installing Ports, which has been renumbered to section 4.5.2 in
the online version.

There was a whole series of "gotchas" which were omitted from the manual and
which are involved in installing FreeBSD, running KDE and getting online
which I have kept as a series of notes and may post some time. Without those
notes one does NOT run KDE or get on line.

Thanks Paul and Bas for your clarifications.
 >> Stay informed about: Make Install 

Chris Clementson wrote:
> in article slrnbftqr7.2efv.wblock.RemoveThis@w0nkity.wonkity.com, Warren Block at
> wblock.RemoveThis@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.

>> You are circumventing the system (two systems, actually) which is there
>> to help you with dependencies. If you want to make it a headache, you
>> picked the right way.
>
> Spare me the lecture. What am I to do when the documentation is of no use?

The first paragraph of 'man ports' is pretty clear:

The FreeBSD Ports Collection offers a simple way for users and
administrators to install applications. Each port contains any
patches necessary to make the original application source code
compile and run on BSD. Compiling an application is as simple as
typing make build in the port directory! The Makefile automatically
fetches the application source code, either from a local disk or
via FTP, unpacks it on your system, applies the patches, and
compiles it. If all goes well, simply type make install to install
the application.

The Handbook is more detailed on this, but the procedure is the same.
And it works, if you follow it.

--
Warren Block * Rapid City, South Dakota * USA
 >> Stay informed about: Make Install 

> This is similar to my trial and error approach: First, copy the downloaded
> tar.gz to /usr/ports/distfiles. Then, using Konqueror I right clicked on
the
> downloaded file (not the copy in /usr/ports/distfiles) and chose "Extract
> here". It made the subdirectory you refer to. Using the terminal I went to
> the new subdirectory and typed "make". I then got a blur of output in the
> terminal. When finished I typed "make install" and got another blur of
> output. Fontconfig seems to be installed but it's a version the other
> package doesn't want.

Similar but not identical. Follow my procedure from your homedir, it'll most
likely work. Fontconfig uses an installation procedure that first needs to
configure the makefile for your particular machine, then make, then install.
If your forget to run ./configure --prefix=/usr/local for your downloaded
tarball, it won't work no matter what you do but it will give you said blur
of output. You MUST use these commands in order:

../configure --prefix=/usr/local
make
(become root if you're not already)
make install

The order of these commands is of paramount importance. On the other hand,
fontconfig 2.2.0 is probably available in the packages tree of an older
FreeBSD release. I'll sift through my various CD's to see if I can find it
for you later today. Such a package should simply work by using pkg_add. You
can delete the wrong version using pkg_delete <package name>, and the
package name can be gleaned from the output of pkg_info and if that screen
gets too long: pkg_info | grep fontconfig will probably give you the exact
name of the package you need. There's a single caveat: you probably can't
use older packages with FreeBSD's from the 5.x branches due to updated
compiler and broken ABI compatibility because of that.

Bas
 >> Stay informed about: Make Install