8 More Discussions You Might Find Interesting
1. AIX
Hi, I need to look at a recent copy of /usr/include/errno.h from AIX 7.2 to check some symbols. In particular, I'm curious if it defines EOWNERDEAD and ENOTRECOVERABLE. Can someone who has access to 7.2 please check for me? Thanks! (1 Reply)
Discussion started by: topcat
1 Replies
2. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
3. Programming
I'm writing a program which uses curl to be run on Linux PCs which will be used by a number of different users. I cannot make the users all install curl on their individual machines, so I have tried to link curl in statically, rather than using libcurl.so. I downloaded the source and created a... (8 Replies)
Discussion started by: BrandonShw
8 Replies
4. Linux
I have some static library(libxxx.a libyyy.a).
And I want to generate my library(libzzz.a), libzzz.a will use libxxx.a and libyyy.a
I wan't my application only use libzzz.a, (means libzzz.a had include libxxx.a, libyyy.a), how can I do that? Thank you.
example:
I have zzz.c.
I do ... (4 Replies)
Discussion started by: freemagic
4 Replies
5. Solaris
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies
6. IP Networking
hello, i need help on setting my coyote linux, i've working on this for last 5 days, can't get it to work. I've been posting this message to coyote forum, and other linux forum, but haven't get any answer yet. Hope someone here can help me...... please see my attached picture first.
... (0 Replies)
Discussion started by: dlwoaud
0 Replies
7. AIX
Hello experts ,
i have some strange problem,
i wanted to create a shared object in AIX 5.3 for which i have compiled all my .cxx to .o which worked fine and then i created the .so from them , but when i do
nm -Bo sample.so ,
i have many unresolved symbol, including printf... (0 Replies)
Discussion started by: vin_pll
0 Replies
8. SuSE
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies
NMEDIT(1) General Commands Manual NMEDIT(1)
NAME
nmedit - change global symbols to local symbols
SYNOPSIS
nmedit -s list_file [-R list_file] [-p] [-A] [-] [[-arch arch_type] ...] object_file ... [-o output]
DESCRIPTION
Nmedit changes the global symbols not listed in the list_file file of the -s list_file option to static symbols. Undefined symbols and
common symbols are not affected and shouldn't be listed in list_file. For dynamic libraries symbols are turned into private extern symbols
that are no longer external (rather than static symbols). This is done so that the references between modules of a dynamic library are
resolved to the symbols in the dynamic library. Nmedit differs from strip(1) in that it also changes the symbolic debugging information
(produce by the -g option to cc(1)) for the global symbols it changes to static symbols so that the resulting object can still be used with
the debugger.
Nmedit like strip(1) is useful to limit the symbols for use with later linking. This allows control of the interface that the executable
wants to provide to the objects that it will dynamically load, and it will not have to publish symbols that are not part of its interface.
For example an executable that wishes to allow only a subset of its global symbols but all of the shared libraries globals to be used would
have its symbol table edited with:
% nmedit -s interface_symbols -A executable
where the file interface_symbols would contain only those symbols from the executable that it wishes the objects loaded at runtime to have
access to. Another example is an object that is made up of a number of other objects that will be loaded into an executable would built
and then have its symbol table edited with:
% ld -o relocatable.o -r a.o b.o c.o
% nmedit -s interface_symbols relocatable.o
which would leave only the symbols listed in the file interface_symbols (and the undefined and common symbols) as global symbols in the
object file.
The one or more of the following options is required to nmedit(1) is:
-s filename
Leave the symbol table entries for the global symbols listed in filename global but turn all other global symbols (except undefined
and common symbols) into static symbols. The symbol names listed in filename must be one per line. Leading and trailing white space
are not part of the symbol name. Lines starting with # are ignored, as are lines with only white space.
-R filename
Change the symbol table entries for the global symbols listed in filename into static symbols. This file has the same format as the
-s filename option above. If the -R filename option is specified without the -s filename option, then all symbols not listed in the
-R filename option's filename are left as globals. If both a -R filename and a -s filename are given the symbols listed in the -R
filename are basically ignored and only those symbols listed in the -s filename are saved.
-p Change symbols to private externs instead of static. This is allowed as the only option to change all defined global symbols to
private externs.
The options to nmedit(1) are:
-A Leave all global absolute symbols except those with a value of zero, and save objective-C class symbols as globals. This is
intended for use of programs that load code at runtime and want the loaded code to use symbols from the shared libraries.
- Treat all remaining arguments as file names and not options.
-arch arch_type
Specifies the architecture, arch_type, of the file for nmedit(1) to process when the file is a universal file (see arch(3) for the
currently know arch_types). The arch_type can be all to process all architectures in the file. The default is to process all
architectures that are contained in the file.
-o output
Write the result into the file output.
SEE ALSO
strip(1), ld(1), arch(3)
BUGS
The changing of the symbolic debugging information by nmedit is not known to be totally correct and could cause the debugger to crash, get
confused or produce incorrect information.
Apple Inc. May 29, 2007 NMEDIT(1)