12-20-2002
Either way that line of code is garbage. My guess is that the programmer meant to use memset instead of memcpy. But that is only a guess.
8 More Discussions You Might Find Interesting
1. Solaris
Hi,
We are porting our application from 32bit to 64bit.
We tried -xarch=v9, -xarc=v9a and -xport64=full options so that compiler to issue 64bit porting warnings.
But we are not getting any porting warninings
WE are using CC 5.5 compiler on sparc-solaris m/c.
Please tell us some powerful... (0 Replies)
Discussion started by: shobhah
0 Replies
2. Programming
Hi i have a C program that i need to port from solaris to BSD
The flags i pass on CC in solaris are -lsocket -lnsl
I use sockets and threads anyone know flags for BSD (1 Reply)
Discussion started by: yngwie
1 Replies
3. AIX
Hi,
When we tried to port our Pro*C programs from sun solaris to AIX,
We get following error messages:
The following library is not available... This library file is required for Pro*C Object Linking and Bin creation.
/usr/lib/libnsl.so.1.
Can anybody help us on this ?
Regards
rbs100 (1 Reply)
Discussion started by: rbs100
1 Replies
4. Solaris
Hi,
I am trying to convert 32-bit code to 64-bit.
I have defined function
int main()
{
int* l;
size_t len1;
fun(len1);
return 0;
}
void fun(int* ptr)
{
cout<<"\nsizeof(ptr)"<<sizeof(ptr);
}
However while compiling getting error as :
Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies
5. Solaris
Hi all,
Has anyone experience with proting a Linux driver (C-code) to Solaris 10?
I have a Sunix SATA card with a inicio1622 chipset, but no driver available. From the website of inicio I downloaded the drivercode for Linux 2.4.
Having done some investigation I found a Solaris driver... (4 Replies)
Discussion started by: longwave
4 Replies
6. Shell Programming and Scripting
Can any one please help the use of "cu command in Solaris" and as well as in Linux :confused: (1 Reply)
Discussion started by: sabee.prakash
1 Replies
7. Solaris
I don't expect any quick answers, but if people have links to resources I can investigate I'd be extremely appreciative. Here is what we have today:
The "application" is a multi-process train control system that uses the Unix desktop, currently CDE, several motif-based applications and sound,... (8 Replies)
Discussion started by: paz9
8 Replies
8. Shell Programming and Scripting
I have a script which has commands that are located in different paths on my Linux o/s than on Solaris. For example, to make uname work, I need to do it this way in Solaris:
my $host= `/usr/bin/uname -n` But in Linux it is:
my $host = `/bin/uname -n`I have this issue with at least 5... (8 Replies)
Discussion started by: newbie2010
8 Replies
LEARN ABOUT LINUX
config.guess
CONFIG.GUESS(1) User Commands CONFIG.GUESS(1)
NAME
config.guess - guess the build system triplet
SYNOPSIS
config.guess [OPTION]
DESCRIPTION
The GNU build system distinguishes three types of machines, the `build' machine on which the compilers are run, the `host' machine on which
the package being built will run, and, exclusively when you build a compiler, assembler etc., the `target' machine, for which the compiler
being built will produce code.
This script will guess the type of the `build' machine.
Output the configuration name of the system `config.guess' is run on.
Operation modes:
-h, --help
print this help, then exit
-t, --time-stamp
print date of last modification, then exit
-v, --version
print version number, then exit
ENVIRONMENT VARIABLES
config.guess might need to compile and run C code, hence it needs a compiler for the `build' machine: use the environment variable
`CC_FOR_BUILD' to specify the compiler for the build machine. If `CC_FOR_BUILD' is not specified, `CC' will be used. Be sure to specify
`CC_FOR_BUILD' is `CC' is a cross-compiler to the `host' machine.
CC_FOR_BUILD a native C compiler, defaults to `cc'
CC a native C compiler, the previous variable is preferred
REPORTING BUGS
Report bugs and patches to <config-patches@gnu.org>.
Originally written by Per Bothner. Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO
autoconf(1), automake(1), autoreconf(1), autoupdate(1), autoheader(1), autoscan(1), config.guess(1), config.sub(1), ifnames(1), libtool(1).
config.guess (2005-09-19) September 2005 CONFIG.GUESS(1)