Sponsored Content
Full Discussion: Porting tools
Top Forums Programming Porting tools Post 91778 by linuxpenguin on Monday 5th of December 2005 01:45:14 PM
Old 12-05-2005
Hi,
I am not sure what you mean by "Porting Tools"
Are there any specific tools you are talking about. Where are you porting them from. You are porting them to Unix, but from where. I think the question is quite subjective.
Can you clarify with a few examples.

--
 

8 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. 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

5. 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

6. HP-UX

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 \ ... (1 Reply)
Discussion started by: angeloberardi
1 Replies

7. 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

8. 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
INTRO(1)						    BSD General Commands Manual 						  INTRO(1)

NAME
intro -- introduction to general commands (tools and utilities) DESCRIPTION
Section one of the manual contains most of the commands which comprise the BSD user environment. Some of the commands included in section one are text editors, command shell interpreters, searching and sorting tools, file manipulation commands, system status commands, remote file copy commands, mail commands, compilers and compiler tools, formatted output tools, and line printer commands. All commands set a status value upon exit which may be tested to see if the command completed normally. Traditionally, the value 0 signifies successful completion of the command, while a value >0 indicates an error. Some commands attempt to describe the nature of the failure by using exit codes as defined in sysexits(3), while others simply set the status to an arbitrary value >0 (typically 1). SEE ALSO
apropos(1), man(1), intro(2), intro(3), sysexits(3), intro(4), intro(5), intro(6), intro(7), security(7), intro(8), intro(9) Tutorials in the UNIX User's Manual Supplementary Documents. HISTORY
The intro manual page appeared in Version 6 AT&T UNIX. BSD
October 21, 2001 BSD
All times are GMT -4. The time now is 05:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy