Sponsored Content
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
LIBC(7) 						     Linux Programmer's Manual							   LIBC(7)

NAME
libc - overview of standard C libraries on Linux DESCRIPTION
The term "libc" is commonly used as a shorthand for the "standard C library", a library of standard functions that can be used by all C programs (and sometimes by programs in other languages). Because of some history (see below), use of the term "libc" to refer to the stan- dard C library is somewhat ambiguous on Linux. glibc By far the most widely used C library on Linux is the GNU C Library <http://www.gnu.org/software/libc/>, often referred to as glibc. This is the C library that is nowadays used in all major Linux distributions. It is also the C library whose details are documented in the rel- evant pages of the man-pages project (primarily in Section 3 of the manual). Documentation of glibc is also available in the glibc manual, available via the command info libc. Release 1.0 of glibc was made in September 1992. (There were earlier 0.x releases.) The next major release of glibc was 2.0, at the beginning of 1997. The pathname /lib/libc.so.6 (or something similar) is normally a symbolic link that points to the location of the glibc library, and exe- cuting this pathname will cause glibc to display various information about the version installed on your system. Linux libc In the early to mid 1990s, there was for a while Linux libc, a fork of glibc 1.x created by Linux developers who felt that glibc develop- ment at the time was not sufficing for the needs of Linux. Often, this library was referred to (ambiguously) as just "libc". Linux libc released major versions 2, 3, 4, and 5 (as well as many minor versions of those releases). For a while, Linux libc was the standard C library in many Linux distributions. However, notwithstanding the original motivations of the Linux libc effort, by the time glibc 2.0 was released, it was clearly superior to Linux libc, and all major Linux distributions that had been using Linux libc soon switched back to glibc. (Since this switch occurred over a decade ago, man-pages no longer takes care to document Linux libc details. Nevertheless, the history is visible in vestiges of information about Linux libc that remain in some manual pages, in particular, references to libc4 and libc5.) Other C libraries There are various other less widely used C libraries for Linux. These libraries are generally smaller than glibc, both in terms of fea- tures and memory footprint, and often intended for building small binaries, perhaps targeted at development for embedded Linux systems. Among such libraries are uClibc (http://www.uclibc.org/) and dietlibc (http://www.fefe.de/dietlibc/). Details of these libraries are gen- erally not covered by the man-pages project. SEE ALSO
syscalls(2), feature_test_macros(7), man-pages(7), standards(7) COLOPHON
This page is part of release 3.55 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2012-08-05 LIBC(7)
All times are GMT -4. The time now is 08:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy