My understanding is that you want to run a command if any of the targets are out of date, but only once, not once for each target.
Yep, entirely correct.
Indeed, an interesting idea to touch the config file and turn the dependencies around.
BUT:
a) It will only work when updating an existing set of files, not with creating them initially ("No rule to make target 'a.txt' needed by 'abcd.conf'")
b) It will not produce correct results in my case, as the same config file is used by several different scripts to generate targets (sometimes only one, sometimes 256 in one go)
I found a solution. Not nice, but I have to generate the makefile anyway...
Looks like GNU make re-evaluates all targets after each run of a rule. Lets see how it copes with all ~8500 rules of the project...
Hi,
I am getting the following error while building on Solaris 64 , while I am trying to build.
Error Snippet :-
----------------------
Makefile:57: *** multiple target patterns. Stop.
make: Leaving directory `/work1/patch/vds6053sun64o/vobs/jvi'
make: *** Error 2
make: Leaving directory... (0 Replies)
Hi All
I need to parse the target
something like:
ifeq '$@' 'first'
echo 1 $@
endif
ifeq '$@' 'second'
echo 2 $@
endif
The thing is to be able compare the target string to any string and then do the commands
Thanks a lot
ziv (0 Replies)
Greetings!
I'm fairly new to the unix world and I hope someone here can help me with my question. I'm using a Makefile to run a few programs and the final output is several .eps files. However I need them to be .pdf files, so I want to use epstopdf to convert the files.
Since I'm already... (6 Replies)
Hi All
I am creating a makefile and I want to do a clean section.
In the clean section I would like to check if the file exists and then delete it.
I always have an error 'unexpected end of file'
What's wrong in it?
Thanks
msntn
firstCpp: first.cpp
g++ -o first first.cpp
clean:
... (1 Reply)
Hi,
As part of our project, we need to load historical data for a year before our system is live. We have the data feed files that we need to load. However, I need to make sure that the file structure (number of fields separated by a comma) on the field is same for all the files of the same... (1 Reply)
I have the following part of a makefile and want to simplify it
using rules rather than having to code the same two blocks
when I need ti build another program.
An having difficulty doing it
all: 1dvel2 1dvel 2dvel
... (8 Replies)
I am trying to create executables for the following files
Currently, I am making 9 different directories for for each. I would like to make 1 directory but everytime I try it does not work.
CROSS_COMPILE?=
# CROSS_COMPILE used to = arm-arago-linux-gnueabi... (1 Reply)
Hello,
I want to merge multiple files (under hundreds folders) side by side. File name are the same but folder are different.
like
folder1/same_name.txt
folder2/same_name.txt
folder3/same_name.txt
......Normally it can be done as
paste /different_path*/same_name.txt > merged_file.txtbut... (2 Replies)
Hi,
I have a question related to makefile. I'm new to makefile and I'm in the process of writing a makefile for my RBT build. I have multiple source files and when I compile them I will get multiple object files (one object file for each source file). I'm having problem in creating a target for... (1 Reply)
Discussion started by: Anand Venkatesa
1 Replies
LEARN ABOUT OPENSOLARIS
dat.conf
dat.conf(4) File Formats dat.conf(4)NAME
dat.conf - DAT static registry
SYNOPSIS
/etc/dat/dat.conf
DESCRIPTION
The DAT static registry, /etc/dat/dat.conf is a system-wide data resource maintained by the system administrative command datadm(1M).
/etc/dat/dat.conf contains a list of interface adapters supported by uDAPL service providers. An interface adapter on Infiniband (IB) cor-
responds to an IPoIB device instance, for example, ibd0. An IPoIB device name represents an IP interface plumbed by ifconfig(1M) on an IB
partition/Host Channel Adapter port combination.
Each entry in the DAT static registry is a single line that contains eight fields. Fields are separated by a SPACE. Lines that begin with a
pound sign (#) are considered comments. All characters that follow the # are ignored. Enclose Solaris specific strings (Solaris_spe-
cific_string) and service provider's instance data (service _provider_instance_data) in quotes.
The following shows the order of the fields in a dat.conf entry:
"interface_adapter_name" "API_version" "threadsafe | nonthreadsafe"
"default | nondefault" "service_provider_library_pathname"
"service_provider_version" "service _provider_instance_data"
"Solaris_specific_string"
The fields are defined as follows:
interface_adapter_name
Specifies the Interface Adapter (IA) name. In IB, this is the IPoIB device instance name, for example, ibd0. This represents an IP
interface plumbed on an IB partition/port combination of the HCA.
API_version
Specifies the API version of the service provide library: For example, "u"major.minor is u1.2.
threadsafe | nonthreadsafe
Specifies a threadsafe or non-threadsafe library.
default | nondefault
Specifies a default or non-default version of library. A service provider can offer several versions of the library. If so, one version
is designated as default with the rest as nondefault.
service_provider_library_pathname
Specifies the pathname of the library image.
service_provider_version
Specifies the version of the service provider. By convention, specify the company stock symbol as the service provider, followed by
major and minor version numbers, for example, SUNW1.0.
service _provider_instance_data
Specifies the service provider instance data.
Solaris_specific_string
Specifies a platform specific string, for example, the device name in the service_provider.conf file.
EXAMPLES
Example 1 Sample dat.conf File
The following dat.conf file shows a uDAPL 1.2 service provider for tavor, udapl_tavor.so.1 supporting two interfaces, ibd0 and ibd1:
#
# dat.conf for uDAPL 1.2
#
ibd0 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
"driver_name=tavor"
ibd1 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
"driver_name=tavor"
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWudaplr |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO datadm(1M), ifconfig(1M), libdat(3LIB), service_provider.conf(4), attributes(5)NOTES
An empty dat.conf is created during the package SUNWudaplr installation if no file is present beforehand. Entries in the file are added or
removed by running datadm(1M).
The content of the platform specific string does not constitute an API. It is generated by datadm(1M) and might have a different content or
interpretation in a future release.
SunOS 5.11 18 Jun 2004 dat.conf(4)