Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Figure out the minimum os version neede to run executable or link library.
Top Forums UNIX for Advanced & Expert Users Figure out the minimum os version neede to run executable or link library. Post 302583057 by Corona688 on Monday 19th of December 2011 12:30:27 PM
Old 12-19-2011
Quote:
Originally Posted by +Yan
Hello and tank you for the fast replay,

Here is some additional information on what I'm trying to do.
I'm trying to achieve the following goal: Automatically name the zip file containing binaries, and libraries compiled on the machines having the above OSes.
Why would you use a zip file to hold UNIX executable files? Permissions may not be preserved properly, which could play havoc. Tarballs are better suited.

Quote:
For Linux "file" command returns the minimum Linux Kernel that was used during the compilation process.
This really isn't relevant. You can often run x86 binaries from 1992 on a modern Linux system if you have old enough libraries, or the new libraries are compatible. The way many basic system calls work hasn't changed much since Linux's inception. The libraries are what's really important.

Use packages that were actually distributed for these various operating systems instead of keeping your own tarballs of randomly packaged binaries, and you'll have programs that're supposed to work and know exactly what their dependencies are.
Last edited by Corona688; 12-19-2011 at 02:19 PM..
 

10 More Discussions You Might Find Interesting

1. Programming

use gcc and link with a library

Hello, J have a problem when I use gcc: This comand works: gcc -shared -fpic -I/usr/include/sys -I/usr/include -L/usr/lib/librt.sl essai1.c mylib.sl but gcc I/usr/include/sys -I/usr/include -L/usr/lib/librt.sl essai2.c -o essai don't work. The first command creates a dynamique... (1 Reply)
Discussion started by: AUBERT
1 Replies

2. Programming

Link against a particular version of libstdc++

Our development machines have libstdc++.so.5 and libstdc++.so.6. When we build our native code, it uses libstdc++.so.6. Is there anyway I can force it to use libstdc++.so.5 instead ? $ ldd try /usr/lib/libcwait.so (0x00655000) libstdc++.so.6 => /usr/lib/libstdc++.so.6... (5 Replies)
Discussion started by: vino
5 Replies

3. UNIX for Dummies Questions & Answers

Cannot run UNIX executable !

I have installed the Darwin Calendar Server on my Mac and got it working. To start the server I open a Finder window on my mac and click the UNIX executable called RUN. In order to start the server automatically on bootup I used LINGON to add a startup Daemon to call "RUN -d". When I reboot... (6 Replies)
Discussion started by: thylacine
6 Replies

4. Solaris

Executable takes indefinite time to search for shared library

Hi, I have an executable that takes indefinitely long time to search for the libsendfile.so in particular solaris machines only. The library is actually in the /lib folder. Where as it works fine on few of the machines, it takes long time in few others. I have checked crle options. Its... (1 Reply)
Discussion started by: kk2202
1 Replies

5. Shell Programming and Scripting

symbolic link to an executable file

I have a script within my home folder and want to be able to execute it without using the sh command. I know that if it was in ~/bin and executable I could do it just by typing the file name, but would rather keep it in the current file structure I tried creating a soft link in ~/bin,... (5 Replies)
Discussion started by: Jaloopa
5 Replies

6. Linux

Size of the Library/Executable is high in LINUX

HI All, We have a 32bit Gui application created using C++. We ported the application from Solaris to Linux. Issue we are facing is the size of the library and executable is very large in LINUX compared to Solaris. Red Hat Enterprise Linux 5.4 is the Linux version we using. Please... (0 Replies)
Discussion started by: sanushchacko
0 Replies

7. Shell Programming and Scripting

[SHELL] Executable? Run it!

I would like to make a script that I can see if the file is executable. If it is executable then it needs to run. Otherwise, if it is not executable the file needs to be edited, and run agian. I hope you understand what i mean. :) Thanks for the netherlands (4 Replies)
Discussion started by: dennisbest85
4 Replies

8. Programming

g++ fails to link to static library when compilation and link in single command

Hello All, I've encountered a strange behaviour from g++ that doesn't make sense to me. Maybe you can shed some light on it: I have a bunch of source files and want to compile them and link them with a static library liba.a located in /usr/local/lib64 into an executable Approach 1 works... (0 Replies)
Discussion started by: magelord
0 Replies

9. UNIX for Advanced & Expert Users

Xserver shared library link is gone

I am administering an Xserver v10.6.8 and I updated the ports using Macports self update. I received this error when calling the program R dyld: Library not loaded: /opt/local/lib/libicuuc.48.dylib Referenced from: /opt/local/lib/R/lib/x86_64/libR.dylib Reason: image not found Trace/BPT... (2 Replies)
Discussion started by: godzilla07
2 Replies

10. Shell Programming and Scripting

Help with change significant figure to normal figure command

Hi, Below is my input file: Long list of significant figure 1.757E-4 7.51E-3 5.634E-5 . . . Desired output file: 0.0001757 0.00751 0.00005634 . . . (10 Replies)
Discussion started by: perl_beginner
10 Replies

LEARN ABOUT NETBSD

compat_netbsd32

COMPAT_NETBSD32(8)					    BSD System Manager's Manual 					COMPAT_NETBSD32(8)

NAME

     compat_netbsd32 -- setup procedure for 32-bit compatibility on 64-bit platforms

DESCRIPTION

     The compat_netbsd32 module allows NetBSD/sparc64 to run NetBSD/sparc executables, and NetBSD/amd64 to run NetBSD/i386 executables.

     To use compat_netbsd32, one must either have COMPAT_NETBSD32 and EXEC_ELF32 in the kernel, or load the compat_netbsd32 and exec_netbsd32 ker-
     nel modules.

     Static executables typically need no additional setup.  Dynamic binaries require the dynamic linker plus shared libraries.  Most of these
     files will need to be placed under /emul/netbsd32.

     The easiest method of installing support for these is via the emulators/netbsd32_compat14, emulators/netbsd32_compat15, and
     emulators/netbsd32_compat16 packages, provided in the NetBSD packages collection.	These install 32-bit a.out and ELF compatibility
     libraries, respectively.  The details of what is actually necessary for correct operation are given below.  This obviously is handled by the
     emulator packages.

     For a.out compatibility, /usr/libexec/ld.so from a 32-bit distribution is required to exist as /emul/netbsd32/usr/libexec/ld.so.  For 32-bit
     ELF compatibility, /usr/libexec/ld.elf_so needs to be in /emul/netbsd32/usr/libexec/ld.elf_so.

     The shared libraries for a.out binaries do not live under the /emul/netbsd32 directory, but under the /emul/aout directory, where the a.out
     dynamic linker will find them.

BUGS

     A list of things which fail to work in compatibility mode should be here.

     IPC is not well supported.

     sysctl(3) is not well supported.

BSD
								  March 11, 2006							       BSD
All times are GMT -4. The time now is 05:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy