Sponsored Content
Full Discussion: Makfile porting
Operating Systems HP-UX Makfile porting Post 302252402 by angeloberardi on Wednesday 29th of October 2008 10:48:36 AM
Old 10-29-2008
Makfile porting

I am trying to port to HP-UX 11i v3 system an application in C++ language written for a Tru64 Unix V5.
I am trying to execute on HP-UX 11i v3 a Makefile written for
Tru64 Unix V5 with this code:

$(TARGET_MORE): $(DEPEND_FILE) $(SOURCE_MORE.cc) $(LIBS)
@for i in $(TARGET_MORE); do \
$(LINK_MORE); \
done

The for instruction and the instrutions under have a tab on the front.
When I execute make I have a syntax error on the line of the for instruction. This code works properly on Tru64 Unix V5
I tested the code changing it this way

$(TARGET_MORE): $(DEPEND_FILE) $(SOURCE_MORE.cc) $(LIBS)
for var in one two three ; do
echo $var
done

and I still have a syntax error on the line of the for code.
In the second example the for cycle works properly if I execute it on the shell out of the Makefile.

In all the Makefile this is the first point where there is the for instruction.
It seems that it dosen't recognize the for instruction.
In the HP-UX 11i v3 I am using the make in /usr/bin/make. I have used the the gcc compiler, the korn shell, the posix shell and the problem didn't change. Which setting must I do so this Makefile works on HP-UX 11i v3.

I thank you in advance.
Angelo Berardi
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Porting Scripts.

Hi all, Figured this would be a good a place (well more apropriate) to ask this ... What considerations are necesary to port a script from one system to another? The below link is a script that I'm currently working on at work. The work system is a SCO box and I'm slowly becoming familar... (1 Reply)
Discussion started by: Cameron
1 Replies

2. Programming

Porting to solaris

I have ported a c program to solaris. When I run , it gives me segmentation fault error at line :- memcpy ((char *)a_string ,(char *)0, MAX_READ ) ; originally this was in reliant unix as :- memcpy ( a_string , 0 , MAX_READ ) ; Can somebody help me about this ? (1 Reply)
Discussion started by: suds19
1 Replies

3. UNIX for Dummies Questions & Answers

HP-UX to linux porting

Hi all, i wanted to port some HP-UX code to linux. can anybody point to some documents or resources that would help me in doing the porting.. thanks in advance Arun Prakash (0 Replies)
Discussion started by: arunprakash
0 Replies

4. Programming

Porting tools

I m sorry if this is the wrong place to post this. I m going to do a project on porting tools in unix platform. Can any one give me further suggestions and resources for this topic "Porting tools". Thanks in advance (5 Replies)
Discussion started by: veeru554
5 Replies

5. Shell Programming and Scripting

how to capture compilation errors with Makfile

Hello I have big compilation project when I run the top make file I have problem to find the errors that acres in the sub directories because the make file keeps Running the compilation. is there any way to perform summry of the errors when the Top makefile done running ? thanks (2 Replies)
Discussion started by: umen
2 Replies

6. UNIX for Advanced & Expert Users

porting

I want to know what are the design considerations to be taken into account. when porting a socket project from Unix platform to another ...... (10 Replies)
Discussion started by: areef4u
10 Replies

7. Linux

when porting from HP-UX to Linux

helo, i m porting HP-UX socket application to Linux SSL-socket application. I have use htonl() in HP-UX. so when i use it in Linux, data transf is not done and application become soem time crashed. now when i remove htonl() in linux, then i got data but it will not proper order or some data may... (1 Reply)
Discussion started by: amitpansuria
1 Replies

8. AIX

Porting from HP-UX to AIX

I am orignally a VC++ programmer, this is the my post in UNIX form. I have an existing source code, that was developed in old HP-UX system, the objective is to make it work on new AIX system. It does'nt appear that AIX has the necessary libraries or even run the application if its... (0 Replies)
Discussion started by: maverick786us
0 Replies

9. Solaris

Porting to new hardware - best way?

Same version of Solaris etc. Moving to new hardware. The application that runs on this server is easy enough to re-install but Im concerned about things like:- 1. Users/passwords/home directories 2. Cron jobs 3. Static routes Is there ANY way to either export this sort of thing so that I... (6 Replies)
Discussion started by: psychocandy
6 Replies
logger(1)						      General Commands Manual							 logger(1)

NAME
logger - Makes entries in the system log SYNOPSIS
/usr/bin/logger [-f file] [-i] [-p[facility.]priority] [-t tag] [message...] logger [-b] [message...] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: logger: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
[Tru64 UNIX] Logs the informational message to the binary event logger instead of the syslog() subroutine and enters information in the binary event log file. The uerf command with the -r 250 option reports the informational messages that are in the binary event log file, which is used for system maintenance and troubleshooting. The -b option cannot be used with any other options. [Tru64 UNIX] Logs all lines in file. [Tru64 UNIX] Logs the process ID (PID) of the logger process with each line. [Tru64 UNIX] Enters the message with the specified priority and, if specified, from the specified facility. [Tru64 UNIX] You can specify priority as either an alphabetic string or its integer equivalent. You can specify the following val- ues for the priority variable: [Tru64 UNIX] (0) [Tru64 UNIX] The system is unusable. (0) [Tru64 UNIX] Action must be taken imme- diately. (1) [Tru64 UNIX] Critical conditions. (2) [Tru64 UNIX] Error conditions. (3) [Tru64 UNIX] (3) [Tru64 UNIX] (4) [Tru64 UNIX] Warning conditions. (4) [Tru64 UNIX] Normal but significant condition. (5) [Tru64 UNIX] Informational. (6) [Tru64 UNIX] Debug-level messages. (7) [Tru64 UNIX] You can also specify a value for the facility variable, which indicates the source of the event. You can specify facility as either an alphabetic string or its integer equivalent. The integer values appear in parentheses. You can specify the following values for the facility variable: [Tru64 UNIX] Kernel messages. (0) [Tru64 UNIX] Random user-level messages. (8) [Tru64 UNIX] Mail system. (16) [Tru64 UNIX] System daemons. (24) [Tru64 UNIX] Security/authorization messages. (32) [Tru64 UNIX] (32) [Tru64 UNIX] Messages syslogd generates internally. (40) [Tru64 UNIX] Line printer subsystem. (48) [Tru64 UNIX] Network news subsystem. (56) [Tru64 UNIX] UUCP subsystem. (64) [Tru64 UNIX] Clock daemon. (72) [Tru64 UNIX] (128) [Tru64 UNIX] (136) [Tru64 UNIX] (144) [Tru64 UNIX] (152) [Tru64 UNIX] (160) [Tru64 UNIX] (168) [Tru64 UNIX] (176) [Tru64 UNIX] (184) [Tru64 UNIX] Precedes each entry in the log with tag. OPERANDS
You can specify the message to be used for entries on the command line or with the -f file option, which specifies that each line in file be logged as an entry. If you do not specify message or -f, logger reads standard input. DESCRIPTION
The logger command makes the specified entries in the system log file. The logger command provides a program and shell script interface to the syslog() subroutine. The file in which entries are made depends on the current system log configuration; see syslog and syslogd for more information. NOTES
The effects of the environment variable LC_MESSAGES apply only to diagnostic messages generated by logger, and not to any messages written by the use of the command. EXIT STATUS
The following exit values are returned: Successful completion. An error occurred. EXAMPLES
To log the system reboot, including the process ID of the process running logger, enter: logger -i System rebooted To log each line in the file build.events with the tag trial build preceding them, enter: logger -f build.events -t "trial build" The following commands are equiv- alent and enter events of warning priority to the log: logger -p warning logger -p 4 The following commands are equivalent and enter events from the daemon facility of warning priority: logger -p daemon.warning logger -p 24.4 To specify the debug priority with a priority name, enter: logger -p debug my message To specify the debug priority with a priority number, enter: logger -p 7 my message To specify both debug priority and the user facility, enter: logger -p user.debug my message To specify the same facility/priority pair using numeric values, enter: logger -p 8.7 my message You can also combine alphabetic and numeric specifications: logger -p user.7 my message logger -p 8.debug my message ENVIRONMENT VARIABLES
The following environment variables affect the execution of logger: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments). Determines the locale for the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: binlogd(8), syslogd(8), uerf(8) Functions: syslog(3) Standards: standards(5) logger(1)
All times are GMT -4. The time now is 11:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy