Sponsored Content
Top Forums Programming Incompatiblity of the code due to CC compiler version mismatch. Post 302743339 by achenle on Wednesday 12th of December 2012 01:30:08 PM
Old 12-12-2012
Seems as if this is more complex than just a machine architecture issue. But there's a simple test you can do quickly.

Offhand, I'd think the code compiled with "xtarget=ultra2" should work fine on a SPARC T4 machine. Can you compile a simple "Hello world" binary on the Ultra 2 box with that "xtarget=ultra2" or even just the simple "-fast" option and see how it runs on the SPARC T4 servers?

If that doesn't work, try "xtarget=generic" on the Ultra 2 server.

And FWIW, the "xtarget" option has to come after the "-fast" on the command line. Basically, when you use "-fast" and a bunch of other options to compile, always put "-fast" first because if you don't it will override a lot of other command line options.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

gcc compiler version?

How do you determine which version of the GNU gcc compiler is on your system? (1 Reply)
Discussion started by: Ben070371
1 Replies

2. Solaris

X Keyboard Extension version mismatch

I want to use calls from the X Keyboard Extension, but get "library version mismatch" error. First one is XkbLibraryVersion(..). This one already returns false. Then I call XkbOpenDisplay(...) which does not return a valid display; return value is XkbOD_NonXkbServer. If I open the display with... (0 Replies)
Discussion started by: hiker04
0 Replies

3. UNIX for Dummies Questions & Answers

What version is the compiler?

Hi ! we have a intel fortran compiler on our computer. How do i find out what version it is ? Thank you, dsmv. (1 Reply)
Discussion started by: dsmv
1 Replies

4. AIX

how to find out the compiler version and OS from binary file

Command to get the Compiler version(xlc/gcc) from the binary on AIX platform. I m searching for the Command, to get the Compiler(xlc/gcc) used to build the binary on AIX. I got two commands used on Linux Platform: - readelf -a <lib> | grep comment - hexdump -C -s 0x49e7b -n 1812 <lib> ... (1 Reply)
Discussion started by: Prajakta
1 Replies

5. AIX

install two different compiler version

Hi all. I have a simple question. There's a way to install under AIX system (5.3) two different compiler version, i.e. ibm xlf fortran 11 and 12? Seems that smitty doesn't allows user to change the default installation path; it only allows you to save the replaced files of the superseded... (1 Reply)
Discussion started by: poldo000
1 Replies

6. Solaris

java version mismatch for normal user and root user

:confused: I installed latest version of java ( jre 1.6) on Solaris Machine ......when I run java -version as root, shows the latest version but when I run java -version as normal user, shows the old / previous version What should I do to fix this ...should show the latest version... (3 Replies)
Discussion started by: frintocf
3 Replies

7. Programming

Choose compiler version

Hi, I'm new, here, and I'm searching for a simple solution for a simple problem. I'm working on RedHat 4.4.6-4 through a CentOS Virtual Machine and due to some reasons I must compile my C++ codes with these two different g++ versions: 4.4.6 and 4.2.2. The fact is that I should be able to... (4 Replies)
Discussion started by: Marcuss
4 Replies

8. AIX

Checking xlc compiler version

Hi, Below is output of lslpp command. bash-3.00# lslpp -L | grep xlC xlC.aix50.rte 11.1.0.1 C F XL C/C++ Runtime for AIX 5.3 xlC.cpp 9.0.0.0 C F C for AIX Preprocessor xlC.msg.en_US.cpp 9.0.0.0 C F C for AIX... (2 Replies)
Discussion started by: manoj.solaris
2 Replies

9. Linux

Linking issue due to so version number

Hi all, currently I'm facing a issue in linking a .so file. In my build machine, I've libcrypto.so.6 and there is a softlink as libcrypto.so. In my make file I'm trying to link to the lib using -L -lcrypto and it is success and created my test.exe. When I copy this test.exe to other... (4 Replies)
Discussion started by: vijkrr
4 Replies

10. Shell Programming and Scripting

Need fix for rsync Error due to version mismatch

rsync --delay-updates -F --compress --archive --rsh='/usr/bin/ssh -t -a -x' /web/admin/Transfer/data/ user1@destserver1:/tmp/testf rsync version on sender server is:3.0.9 rsync version on sender server is:3.0.6 Linux sourceserver1 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST... (1 Reply)
Discussion started by: mohtashims
1 Replies
FS_CHECKSERVERS(1)					       AFS Command Reference						FS_CHECKSERVERS(1)

NAME
fs_checkservers - Displays the status of server machines SYNOPSIS
fs checkservers [-cell <cell to check>] [-all] [-fast] [-interval <seconds between probes>] [-help] fs checks [-c <cell to check>] [-a] [-f] [-i <seconds between probes>] [-h] DESCRIPTION
The fs checkservers command reports whether certain AFS server machines are accessible from the local client machine. The machines belong to one of two classes, and the Cache Manager maintains a list of them in kernel memory: o The database server machines for every cell listed in the local /etc/openafs/CellServDB file, plus any machines added to the memory list by the fs newcell command since the last reboot. o All file server machines the Cache Manager has recently contacted, and which it probably needs to contact again soon. In most cases, the Cache Manager holds a callback on a file or volume fetched from the machine. If the Cache Manager is unable to contact the vlserver process on a database server machine or the fileserver process on a file server machine, it marks the machine as inaccessible. (Actually, if a file server machine is multihomed, the Cache Manager attempts to contact all of the machine's interfaces, and only marks the machine as down if the fileserver fails to reply via any of them.) The Cache Manager then periodically (by default, every three minutes) sends a probe to each marked machine, to see if it is still inaccessible. If a previously inaccessible machine responds, the Cache Manager marks it as accessible and no longer sends the periodic probes to it. The fs checkservers command updates the list of inaccessible machines by having the Cache Manager probe a specified set of them: o By default, only machines that are marked inaccessible and belong to the local cell (the cell listed in the local /etc/openafs/ThisCell file). o If the -cell argument is included, only machines that are marked inaccessible and belong to the specified cell. o If the -all flag is included, all machines marked inaccessible. If the -fast flag is included, the Cache Manager does not probe any machines, but instead reports the results of the most recent previous probe. To set the interval between probes rather than produce a list of inaccessible machines, use the -interval argument. The non-default setting persists until the machine reboots; to preserve it across reboots, put the appropriate fs checkservers command in the machine's AFS initialization files. CAUTIONS
The command can take quite a while to complete, if a number of machines do not respond to the Cache Manager's probe. The Cache Manager probes machines sequentially and waits a standard timeout period before marking the machine as unresponsive, to allow for slow network communication. To make the command shell prompt return quickly, put the command in the background. It is harmless to interrupt the command by typing Ctrl-C or another interrupt signal. Note that the Cache Manager probes only server machines marked inaccessible in its memory list. A server machine's absence from the output does not necessarily mean that it is functioning, because it possibly is not included in the memory list at all (if, for example, the Cache Manager has not contacted it recently). For the same reason, the output is likely to vary on different client machines. Unlike most fs commands, the fs checkservers command does not refer to the AFSCELL environment variable. OPTIONS
-cell <cell to check> Names each cell in which to probe server machines marked as inaccessible. Provide the fully qualified domain name, or a shortened form that disambiguates it from the other cells listed in the local /etc/openafs/CellServDB file. Combine this argument with the -fast flag if desired, but not with the -all flag. Omit both this argument and the -all flag to probe machines in the local cell only. -all Probes all machines in the Cache Manager's memory list that are marked inaccessible. Combine this argument with the -fast flag if desired, but not with the -cell argument. Omit both this flag and the -cell argument to probe machines in the local cell only. -fast Displays the Cache Manager's current list of machines that are inaccessible, rather than sending new probes. The output can as old as the current setting of the probe interval (by default three minutes, and maximum ten minutes). -interval <seconds between probes> Sets or reports the number of seconds between the Cache Manager's probes to machines in the memory list that are marked inaccessible: o To set the interval, specify a value from the range between 1 and 600 (10 minutes); the default is 180 (three minutes). The issuer must be logged in as the local superuser "root". The altered setting persists until again changed with this command, or until the machine reboots, at which time the setting returns to the default. o Provide a value of 0 (zero) to display the current interval setting. No privilege is required. Do not combine this argument with any other. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
If there are no machines marked as inaccessible, or if all of them now respond to the Cache Manager's probe, the output is: All servers are running. Note that this message does not mean that all server machines in each relevant cell are running. The output indicates the status of only those machines that the Cache Manager probes. If a machine fails to respond to the probe within the timeout period, the output begins with the string These servers unavailable due to network or server problems: and lists the hostname of each machine on its own line. The Cache Manager stores machine records by Internet address, so the format of each hostname (uppercase or lowercase letters, or an Internet address in dotted decimal format) depends on how the local cell's name service translates it at the time the command is issued. If a server machine is multihomed, the output lists only one of its interfaces (usually, the currently most preferred one). If the -interval argument is provided with a value between 1 and 600, there is no output. If the value is 0, the output reports the probe interval as follows: The current down server probe interval is <interval> secs EXAMPLES
The following command displays the Cache Manager's current list of unresponsive machines in the local cell, rather than probing them again. The output indicates that if there were any machines marked inaccessible, they all responded to the previous probe. % fs checkservers -fast All servers are running. The following example probes machines in the Cache Manager's memory list that belong to the "stateu.edu" cell: % fs checkservers -cell stateu.edu All servers are running. The following example probes all server machines in the Cache Manager's memory list. It reports that two machines did not respond to the probe. % fs checkservers -all These servers unavailable due to network or server problems: fs1.abc.com SV3.STATE.EDU. PRIVILEGE REQUIRED
To set the probe interval, the issuer must be logged in as the local superuser "root". Otherwise, no privilege is required. SEE ALSO
CellServDB(5), ThisCell(5), fs_newcell(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FS_CHECKSERVERS(1)
All times are GMT -4. The time now is 11:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy