The following:
says that the file gq.o needs to be brought up-to-date if any of the four files:
in the current working directory are newer than gq.o or if any of those files do not exist. Neither of the last two files in that list exist in the current directory, and you have not supplied any rules that tell make how to build those files. The third file in that list looks like it might be an option to gcc to tell it how to find bb.h while it is compiling gq.cc to build gq.o, but it does not tell make how to find bb.h. (But the pathname you specified for bb.h [/home/turing/z1755294/assign1/assign1/includes] does not seem to be what is specified by -I/asign1/includes.)
If you are sitting in the directory /home/turing/z1755294/assign1/assign1 when you run make and the files gq.cc and ac.h are in that directory, what pathnames (absolute or relative) can be used to enable make to find the file bb.h?
hello!
i want to create a Makefile on the freebsd 4.5,so i vi the hello.c
#include
int main(int argc, char** argv)
{
printf(''Hello, GNU!\n'');
return 0;
}
#autoscan
#cp configure.scan configure.in
#vi configure.in
modify:AC_OUTPUT AC_OUTPUT(Makefile)
#aclocal
#autoconf... (0 Replies)
Hi ,
While trying to compile a PRO*C code on unix using makefile i get the following errors. i am now working on a 10g migration (from 8i) ...
these makefile perfectly work in previous version.
ld: fatal: file... (7 Replies)
I am mirroring a single partition drive with raidctl. The source partition was mounted when I created the mirror with raidctl -c c1t1d0 c1t3d0. The source disk was defined with s2 and s6 only.
I didn't think to umount it first.
Is there a problem with that? (2 Replies)
Hi all,
I have a requirement to create a "superset" file out of a number of different sources with some different and some same columns.
We intend to have a manually updateable SuperSetCols.csv which would look like
"ColA","ColB","ColC","ColD","ColE","ColF","ColG"
so someday we may add... (3 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
hi all,
I have written a simple C program hello.c and a Makefile.ac but when i try to run automake it does not create Makefile.in hence I am not able to run ./configure command in my directory. Following are the containts of my prog.
hello.c
--------
Code:
#include<stdio.h>
main()
{... (0 Replies)
Hello,
i'm having a problem here with FreeBSD 9.2 . I've created a directory and downloaded the latest ntp-4.2.8p1-beta2 from ntp.org. Untar then into the directory and then
./configure all went OK. Then i had to modify some parameters in the config.h created with ./configure . Then
make... (2 Replies)
Hello,
My makefiles are set up to generate an environment specific build directory based on the local configuration and some values passed to make. It generally looks like,
# compilers, may be passed to make
CC++ = g++
FCOMP = gfortran
# version of program, may be passed to make
ver =... (4 Replies)
Discussion started by: LMHmedchem
4 Replies
LEARN ABOUT DEBIAN
dh_auto_install
DH_AUTO_INSTALL(1) Debhelper DH_AUTO_INSTALL(1)NAME
dh_auto_install - automatically runs make install or similar
SYNOPSIS
dh_auto_install [buildsystemoptions] [debhelperoptions] [--params]
DESCRIPTION
dh_auto_install is a debhelper program that tries to automatically install built files. It does so by running the appropriate command for
the build system it detects the package uses. For example, if there's a Makefile and it contains a install target, then this is done by
running make (or MAKE, if the environment variable is set). If there is a setup.py or Build.PL, it is used. Note that the Ant build system
does not support installation, so dh_auto_install will not install files built using Ant.
Unless --destdir option is specified, the files are installed into debian/package/ if there is only one binary package. In the multiple
binary package case, the files are instead installed into debian/tmp/, and should be moved from there to the appropriate package build
directory using dh_install(1).
DESTDIR is used to tell make where to install the files. If the Makefile was generated by MakeMaker from a Makefile.PL, it will
automatically set PREFIX=/usr too, since such Makefiles need that.
This is intended to work for about 90% of packages. If it doesn't work, or tries to use the wrong install target, you're encouraged to skip
using dh_auto_install at all, and just run make install manually.
OPTIONS
See "BUILD SYSTEM OPTIONS" in debhelper(7) for a list of common build system selection and control options.
--destdir=directory
Install files into the specified directory. If this option is not specified, destination directory is determined automatically as
described in the "DESCRIPTION" section.
-- params
Pass params to the program that is run, after the parameters that dh_auto_install usually passes.
SEE ALSO debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
9.20120909 2011-10-19 DH_AUTO_INSTALL(1)