Linux "make" command questions.

[ARCHIVED THREAD] - Linux "make" command questions.

Posted: 8/27/2005 7:34:12 PM EDT

I'm trying to get a USB phone adapter working in linux. I'm fairly new at this so be patient.

I downloaded all the files and began following the installation instructions. I ran the ./configure command with no problems. The next command says to type in "make" but when I do this I get the following error

[root@localhost usbb2k-api]# make
make: *** No rule to make target `../configure.in', needed by `Makefile.in'. Stop.

Anyone have any clue what this means?

Posted: 8/27/2005 7:34:44 PM EDT

[#1]

linux is the devil

Posted: 8/27/2005 7:44:45 PM EDT

[#2]

Quoted:
linux is the devil

I'm quickly finding that out :) At least now I'm not buying from the devil :)

Posted: 8/27/2005 8:06:34 PM EDT

[#3]

I just learned about the "make" and "make install" commands the other night, so I might not be the greatest help.

When you use MAKE are you in the directoyr of the files you want to install? Thats the problem I had

Posted: 8/27/2005 8:10:43 PM EDT

[#4]

I am in the directory of the files that I am trying to install.

Make install will be my next command after make.

Posted: 8/27/2005 8:10:50 PM EDT

[#5]

Do you have the lastest GCC and GNU Make installed ?

Does the program require autoconf or any libraries, etc according to the README, CONFIG, INSTALL files ?

Posted: 8/27/2005 8:10:51 PM EDT

[#6]

All 'make' does is execute the contents
of the 'makefile' file that is located in the
current directory. You need to do an 'ls'
and verify that there is a 'makefile' in the
current directory.

eta: I'm retarded. Of course there is a
makefile there, it is bitching about a
missing target. I guess that the better
question is: are you executing the top-
level 'makefile' (e.g. are you is one of
the subdirectories)?

Posted: 8/27/2005 8:17:55 PM EDT

[#7]

make dep && make clean && make install

Posted: 8/27/2005 8:23:59 PM EDT

[#8]

You need to run the following commands:

1. Change directory to the directory where you untarred the source.
2. type './configure' (minus quotes)
3. then, type 'make'
4. then type 'make install'

The configure script is necessary to generate a file for make to use

Posted: 8/27/2005 8:28:48 PM EDT

[#9]

It looks like either there is a bug in their configuration script or you need to include an argument with the make command to tell it what you want to make.

-Foxxz

Posted: 8/27/2005 8:29:43 PM EDT

[#10]

Quoted:
make dep && make clean && make install

+1

Posted: 8/27/2005 8:31:17 PM EDT

[#11]

Tag

Posted: 8/27/2005 8:37:02 PM EDT

[#12]

Quoted:
make dep && make clean && make install

[root@localhost usbb2k-api]# make dep
make: *** No rule to make target `dep'. Stop.
[root@localhost usbb2k-api]# make clean
make: *** No rule to make target `clean'. Stop.
[root@localhost usbb2k-api]# make install
make: *** No rule to make target `install'. Stop.
[root@localhost usbb2k-api]#

Posted: 8/27/2005 8:38:33 PM EDT

[#13]

are you logged in as root? did you do a su?

Posted: 8/27/2005 8:40:20 PM EDT

[#14]

Quoted:
You need to run the following commands:

1. Change directory to the directory where you untarred the source.
2. type './configure' (minus quotes)
3. then, type 'make'
4. then type 'make install'

The configure script is necessary to generate a file for make to use

[root@localhost usbb2k-api]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for usb_init in -lusb... yes
Usb lib found
checking for pthread_create in -lpthread... yes
pthread lib found
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: error: cannot find input file: Makefile.in
[root@localhost usbb2k-api]#

Posted: 8/27/2005 8:40:55 PM EDT

[#15]

Quoted:
are you logged in as root? did you do a su?

I did do a SU

Posted: 8/27/2005 8:41:51 PM EDT

[#16]

Did configure finish with zero errors or warnings?
Are you in the top level directory? I ask because it says ../configure.in
Did you read all of the instrustions that came with the package? README, INSTALL, etc.?

eta; oops.. beat me....
you are missing Makefile.in

eta2; furthermore, you should login as root when doing system things.
ppl will tell you to avoid root, but it is a pain trying to do things as a user...
ps, ls, netstat, ifconfig, and such all do not work well to figure out root problems as a user.
furthermore, your path is all screwed up if you try to play root as a user.
su is not equal to logging in as root. it is some sort of phony environment, and some programs will act odd, and things you try to do will not work quite right since you are more or less still a user only with root privledges. Even 'su -' is not good enough.

Posted: 8/27/2005 8:44:56 PM EDT

[#17]

The readme is short and didnt do me any good.

Here are the contents

#
# Make
1. ./autoconf.sh
2. make

# Test API

1. in a Consol:
src/usbb2k_api

2. in a other Consol:
tools/api_connect /tmp/usbb2k.sock

#Commande for api_connect:
SWITCH USB/PSTN
RING 0 (stop ringing)
RING 1 (ring mode 1)
RING 2 (ring mode 2)

#Msg from api_connect:
HANDSET ON/OFF (pickup/off handset)
KEY 01..09 (keyphone pressed)

I am in the top level DIR

Posted: 8/27/2005 8:45:38 PM EDT

[#18]

Quoted:
Did configure finish with zero errors or warnings?
Are you in the top level directory? I ask because it says ../configure.in
Did you read all of the instrustions that came with the package? README, INSTALL, etc.?

eta; oops.. beat me....
you are missing Makefile.in

Hrmmm, I'll have to see what happened to it

Posted: 8/27/2005 8:52:43 PM EDT

[#19]

try re-uncompressing the archive.

You can look for it with the universal-just-tell-my-where-the-eff-it-is command;
find . | grep Makefile.in

Posted: 8/27/2005 9:03:47 PM EDT

[#20]

I think it would probably be easiest to start again from the vary beginning. Here is what I type to get the files.

export CVS_RSH="ssh"
cvs -z3 -d:ext:[email protected]:/cvsroot/usbb2k-api co usbb2k-api

then I get the following

[schapman43@localhost ~]$ cvs -z3 -d:ext:[email protected]:/webcvs/usbb2k-api co usbb2k-api
cvs server: Updating usbb2k-api
U usbb2k-api/index.html
[schapman43@localhost ~]$ cvs -z3 -d:ext:[email protected]:/cvsroot/usbb2k-api co usbb2k-api
cvs server: Updating usbb2k-api
U usbb2k-api/AUTHORS
U usbb2k-api/ChangeLog
U usbb2k-api/Makefile.am
U usbb2k-api/NEWS
U usbb2k-api/README
U usbb2k-api/TODO
U usbb2k-api/autoconf.sh
U usbb2k-api/config.h.in
U usbb2k-api/configure.in
cvs server: usbb2k-api/index.html is no longer in the repository
cvs server: Updating usbb2k-api/connector
cvs server: Updating usbb2k-api/connector/gnomemeeting_connector
U usbb2k-api/connector/gnomemeeting_connector/gnomemeeting_dbus.py
cvs server: Updating usbb2k-api/src
U usbb2k-api/src/Makefile
U usbb2k-api/src/Makefile.am
U usbb2k-api/src/usbb2k-api.h
U usbb2k-api/src/usbb2k-main.c
cvs server: Updating usbb2k-api/tools
U usbb2k-api/tools/Makefile
U usbb2k-api/tools/Makefile.am
U usbb2k-api/tools/api_connect.c
U usbb2k-api/tools/test_usbb2k.py

Then I do a SU

Then I try to follow the readme file

#
# Make
1. ./autoconf.sh
2. make

# Test API

1. in a Consol:
src/usbb2k_api

2. in a other Consol:
tools/api_connect /tmp/usbb2k.sock

#Commande for api_connect:
SWITCH USB/PSTN
RING 0 (stop ringing)
RING 1 (ring mode 1)
RING 2 (ring mode 2)

#Msg from api_connect:
HANDSET ON/OFF (pickup/off handset)
KEY 01..09 (keyphone pressed)

Posted: 8/27/2005 9:07:56 PM EDT

[#21]

After the su I type ./autoconf.sh and get the following

[root@localhost usbb2k-api]# ./autoconf.sh
bash: ./autoconf.sh: Permission denied
[root@localhost usbb2k-api]#

So then I do a chmod -c 7777 *.* which then allows me to run the ./autoconf command

[root@localhost usbb2k-api]# ./autoconf.sh
configure.in: installing `./install-sh'
configure.in: installing `./missing'
src/Makefile.am:2: CFLAGS was already defined in condition TRUE, which includes condition DEBUG ...
configure.in:10: ... `CFLAGS' previously defined here
src/Makefile.am: installing `./depcomp'
src/Makefile.am:2: `CFLAGS' is a user variable, you should not override it;
src/Makefile.am:2: use `AM_CFLAGS' instead.
tools/Makefile.am:5: blank line following trailing backslash
Makefile.am: installing `./INSTALL'
Makefile.am: installing `./COPYING'
[root@localhost usbb2k-api]#

Posted: 8/27/2005 9:10:53 PM EDT

[#22]

after running the ./autoconf.sh command I get a INSTALL file. Here is the contents

Installation Instructions
*************************

Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.

This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.

Basic Installation
==================

These are generic installation instructions.

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').

It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)

If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.

The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.

Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Optionally, type `make check' to run any self-tests that come with
the package.

4. Type `make install' to install the programs and any data files and
documentation.

5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.

Compilers and Options
=====================

Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.

You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:

./configure CC=c89 CFLAGS=-O2 LIBS=-lposix

*Note Defining Variables::, for more details.

Compiling For Multiple Architectures
====================================

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.

Installation Names
==================

By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PREFIX'.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PREFIX', the package will
use PREFIX as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:

CPU-COMPANY-SYSTEM

where SYSTEM can have one of these forms:

OS KERNEL-OS

See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.

If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.

If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.

Sharing Defaults
================

If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Defining Variables
==================

Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:

./configure CC=/usr/local2/bin/gcc

causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script). Here is a another example:

/bin/bash ./configure CONFIG_SHELL=/bin/bash

Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.

`configure' Invocation
======================

`configure' recognizes the following options to control how it operates.

`--help'
`-h'
Print a summary of the options to `configure', and exit.

`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.

`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.

`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.

`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).

`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.

`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.

Posted: 8/27/2005 9:12:33 PM EDT

[#23]

thats when I run the ./configure command and get

root@localhost usbb2k-api]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for usb_init in -lusb... yes
Usb lib found
checking for pthread_create in -lpthread... yes
pthread lib found
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: error: cannot find input file: Makefile.in
[root@localhost usbb2k-api]#

Posted: 8/27/2005 9:21:42 PM EDT

[#24]

Did I confuse everyone? :)

Posted: 8/27/2005 9:26:41 PM EDT

[#25]

Oh, you're compiling from CVS, not a tarball (.tar.gz), that's a somewhat different animal.

Just to repeat myself. do not use 'su', just login as root!
that is probably why automake.sh is giving you the permission denied error.

Try that and see what happenes, if it still does not work, then continue below.

Like you did before, start over from scratch with a fresh download of the source tree then do something along the lines of this...
run autoconf, then automake, then ./configure, then make
autoconf and automake are not exact commands, it may be .sh or such.
You can type autoc then hit the TAB key and it will auto complete if possible, same goes for autom.
It has been a while since I did this kind of thing, you may have to run automake then autoconf.

Posted: 8/27/2005 9:37:02 PM EDT

[#26]

Quoted:
Oh, you're compiling from CVS, not a tarball (.tar.gz), that's a somewhat different animal.

Just to repeat myself. do not use 'su', just login as root!
that is probably why automake.sh is giving you the permission denied error.

Try that and see what happenes, if it still does not work, then continue below.

Like you did before, start over from scratch with a fresh download of the source tree then do something along the lines of this...
run autoconf, then automake, then ./configure, then make
autoconf and automake are not exact commands, it may be .sh or such.
You can type autoc then hit the TAB key and it will auto complete if possible, same goes for autom.
It has been a while since I did this kind of thing, you may have to run automake then autoconf.

I still get the Permission Denied error when logged in as root

I will continue with your next suggestion and see what happens

Posted: 8/27/2005 9:40:33 PM EDT

[#27]

after ./autoconf.sh I am unable to perform a ./automake because its not there.

Posted: 8/27/2005 9:51:38 PM EDT

[#28]

what about straight 'automake', no './'?

Posted: 8/27/2005 10:00:06 PM EDT

[#29]

Quoted:
what about straight 'automake', no './'?

That worked, I got the following

[root@localhost usbb2k-api]# automake
src/Makefile.am:2: CFLAGS was already defined in condition TRUE, which includes condition DEBUG ...
configure.in:10: ... `CFLAGS' previously defined here
src/Makefile.am:2: `CFLAGS' is a user variable, you should not override it;
src/Makefile.am:2: use `AM_CFLAGS' instead.
tools/Makefile.am:5: blank line following trailing backslash
[root@localhost usbb2k-api]#

Posted: 8/27/2005 10:09:58 PM EDT

[#30]

Can you proceed?

If not, try going back, not chmod'ding the autooconf.sh, and just running autoconf all by itself (no ./)

Posted: 8/27/2005 10:20:47 PM EDT

[#31]

Quoted:
Can you proceed?

If not, try going back, not chmod'ding the autooconf.sh, and just running autoconf all by itself (no ./)

thanks again for working with me on this. I really appreciate it.

I downloaded a fresh copy again and ran autoconf by itself and get the following.

[schapman43@localhost ~]$ autoconf
autoconf: no input file

Posted: 8/27/2005 10:31:35 PM EDT

[#32]

hrmmmm, I was just looking at the contents of the autoconf.sh file and found the following

#!/bin/sh

aclocal
autoconf
automake --add-missing

I wonder what hte --add missing thing is all about.

Posted: 8/27/2005 10:35:09 PM EDT

[#33]

You should try JCL sometime..... I hate MVS.

Posted: 8/27/2005 10:46:22 PM EDT

[#34]

You have IM

Posted: 8/27/2005 10:55:36 PM EDT

[#35]

Quoted:
hrmmmm, I was just looking at the contents of the autoconf.sh file and found the following

#!/bin/sh

aclocal
autoconf
automake --add-missing

I wonder what hte --add missing thing is all about.

from `man automake`
--add-missing
Automake requires certain common files to exist in certain situ-
ations; for instance config.guess is required if configure.in
runs AC_CANONICAL_HOST. Automake is distributed with several of
these files; this option will cause the missing ones to be auto-
matically added to the package, whenever possible. In general
if Automake tells you a file is missing, try using this option.
By default Automake tries to make a symbolic link pointing to
its own copy of the missing file; this can be changed with
--copy.