search for: solib

...ink programs that consist of more than one .o file multi-deps = $($(subst $(obj)/,,$@-y)) link-multi-deps = $(addprefix $(obj)/, \ $(patsubst %/, %/built-in.o, $(multi-deps))) diff --git a/klibc/Kbuild b/klibc/Kbuild --- a/klibc/Kbuild +++ b/klibc/Kbuild @@ -119,6 +119,7 @@ $(SOLIB): $(CRT0) $(call objectify,__sha # Build sha1 hash values targets += klibc.so libc.so.hash hostprogs-y := sha1hash +clean-files += klibc-???????????????????????????.so quiet_cmd_solibhash = HASH $@ cmd_solibhash = $(USERNM) $< | egrep '^[0-9a-fA-F]+ [ADRTW] ' | \ @@ -...

...bc-0.173/klibc/Makefile klibc/klibc/Makefile --- klibc-0.173/klibc/Makefile 2004-08-26 15:33:41.000000000 +0930 +++ klibc/klibc/Makefile 2004-09-15 11:54:06.301925693 +0930 @@ -57,6 +57,8 @@ SOHASH = klibc.so CRT0 = crt0.o LIB = libc.a +INTERP_O = interp.o + all: tests $(CRT0) $(LIB) $(SOLIB) klibc.so # Add any architecture-specific rules @@ -109,7 +111,7 @@ $(SOHASH): $(SOLIB) $(SOLIB).hash rm -f klibc-??????????????????????.so ln -f $@ klibc-`cat $(SOLIB).hash`.so -interp.o: interp.S $(SOLIB).hash +$(INTERP_O): interp.S $(SOLIB).hash $(CC) $(CFLAGS) -D__ASSEMBLY__ -DLIBDIR...

...ared-y) +else +install-y := $(static-y) +endif diff --git a/usr/klibc/Kbuild b/usr/klibc/Kbuild index b19f3ab..9efbb4e 100644 --- a/usr/klibc/Kbuild +++ b/usr/klibc/Kbuild @@ -91,7 +91,10 @@ SOHASH := klibc.so CRT0 := arch/$(KLIBCARCHDIR)/crt0.o INTERP_O := interp.o -always := $(LIBC) $(SOLIB) $(SOHASH) $(INTERP_O) +always := $(LIBC) +ifdef KLIBCSHAREDFLAGS +always += $(SOLIB) $(SOHASH) $(INTERP_O) +endif LIBC := $(call objectify,$(LIBC)) SOLIB := $(call objectify,$(SOLIB)) SOHASH := $(call objectify,$(SOHASH)) @@ -181,10 +184,15 @@ $(INTERP_O): $(obj)/interp.S $(SOLIB)....

...+= -DDYNAMIC_CRC_TABLE +klib-$(CONFIG_KLIBC_ZLIB) += zlib/ +# arch specific .o files +klib-y += arch/$(KLIBCARCHDIR)/ ##### # Add any architecture-specific rules @@ -72,14 +68,14 @@ include $(obj)/arch/$(KLIBCARCHDIR)/Make ##### # Shared definitions -LIB := libc.a +LIBC := libc.a SOLIB := libc.so SOHASH := klibc.so CRT0 := arch/$(KLIBCARCHDIR)/crt0.o INTERP_O := interp.o -always := $(CRT0) $(LIB) $(SOLIB) $(SOHASH) $(INTERP_O) -LIB := $(call objectify,$(LIB)) +always := $(LIBC) $(SOLIB) $(SOHASH) $(INTERP_O) +LIBC := $(call objectify,$(LIBC)) SOLIB...

...akefile +++ ash/Makefile 2003/11/27 15:04:02 @@ -36,7 +36,7 @@ $(STRIP) $(PROG) $(PROG).shared: $(OBJS) $(LIBS) - $(LD) $(LDFLAGS) -o $(PROG).shared -e main $(KLIBSRC)/interp.o $(OBJS) -R $(KLIBSRC)/libc.so $(LIBGCC) + $(LD) $(LDFLAGS) -o $(PROG).shared -e main $(KLIBSRC)/interp.o $(OBJS) $(LD_SOLIB_FLAGS) $(KLIBSRC)/libc.so $(LIBGCC) $(STRIP) $(PROG).shared $(CRT0) $(LIBS): --- klibc/Makefile +++ klibc/Makefile 2003/11/27 15:03:50 @@ -62,7 +62,7 @@ $(STRIP) $@.stripped tests/%.shared : tests/%.o interp.o $(SOLIB) - $(LD) $(LDFLAGS) -o $@ -e main interp.o tests/$*.o -R $(SOLIB) $(LIB...

...in the debugging symbols that gdb can later print fields of structs. Theoretically you can use gdb to ptype all the relevant types and reproduce all the headers for another pass of compilation. cint: a C/C++ interpreter that interpret the .h.cxx files directly but also able to call funcs in native solibs. HOWEVER, to interpret code that refs funcs in the precompiled solibs, cint has to parse the relevant headers used by the precompiled solibs and cint has many limitations compared to gcc/g++ parser. Given that llvm bytecode might become a viable distribution format _ideally_ i would like to see a...

...list: ata_piix processor thermal fan jbd ext3 edd (xennet xenblk) Kernel image: /boot/vmlinuz-2.6.16.29-xen Initrd image: /boot/initrd-2.6.16.29-xen Shared libs: lib/ld-2.4.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libblkid.so.1.0 lib/libc-2.4.so lib/libcom_err.so.2.1 lib/libdl-2.4.solib/libext2fs.so.2.4 lib/libhistory.so.5.1 lib/libncurses.so.5.5 lib/libpthread-2.4.so lib/libreadline.so.5.1 lib/librt-2.4.solib/libuuid.so.1.2 Cannot determine dependencies of module edd. Is modules.dep up to date? Cannot determine dependencies of module edd. Is modules.dep up to date? Cannot determ...

...cc.in 2005-03-07 23:44:49.000000000 +0200 diff -ur orig/klibc-1.0.8/klibc/Makefile klibc-1.0.8/klibc/Makefile --- orig/klibc-1.0.8/klibc/Makefile 2005-04-11 18:35:20.000000000 +0300 +++ klibc-1.0.8/klibc/Makefile 2005-05-17 19:30:09.000000000 +0300 @@ -185,7 +185,7 @@ $(INSTALL_EXEC) klibc-`cat $(SOLIB).hash`.so \ $(INSTALLROOT)$(INSTALLDIR)/$(CROSS)lib $(INSTALL_EXEC) klibc-`cat $(SOLIB).hash`.so \ - $(INSTALLROOT)/$(SHLIBDIR) + $(INSTALLROOT)/$(INSTALLDIR)/$(SHLIBDIR) ifneq ($(wildcard $(DIR).*.d),) include $(wildcard $(DIR).*.d)

If you are trying to debug a core dump from a different machine, how do you tell gdb where to look for the debug info files to match the shared libs that you have in a non-standard location? It finds the shared libs themselves with a 'set solib-absolute-path' directive, but it doesn't look for the corresponding (relative) usr/lib/debug/... file that you get if you extract the debuginfo rpm in the same place. And if I set debug-file-directory to the top of the tree, it wants to also add the solib-absolute-path to that. Is there so...

...-Wno-missing-field-initializers -Wpointer-arith -Wwrite-strings -Wdeclaration-after-statement -Werror-implicit-function-declaration XCFLAGS = -include ruby/config.h -include ruby/missing.h -fvisibility=hidden -DRUBY_EXPORT CPPFLAGS = -I. -I.ext/include/x86_64-linux -I./include -I. DLDFLAGS = SOLIBS = compiling parse.c cc1: out of memory allocating 1904232 bytes after a total of 32403456 bytes make: *** [parse.o] Error 1 root@vps [~/ruby-1.9.3-p0]# free total used free shared buffers cached Mem: 524288 368436 155852 0 0...

...r bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/local/libexec/dovecot/imap...done. (gdb) r Starting program: /usr/local/libexec/dovecot/imap warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? process 21455 is executing new program: /usr/local/bin/doveconf warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? process 21455 is executing new program: /usr/lo...

...9;m happy to help but I appreciate this list might not be the best > place to get a tutorial on using gdb on Windows. Essentially, the steps are: build with DEBUG=T (to have debug symbols), possibly updating EOPTS in MkRules.local to disable optimizations, then run gdb loading RGui, "set solib-search-path", run RGui from gdb. Then you can break to debugger from RGui menu, or just run the code that segfaults, and you get to gdb and can print the stacktrace, etc. You can find some information in rw-FAQ (R for Windows FAQ), but yes, it is harder than on Linux. We can take care of t...

Hi, I am trying to do a very minimal install of Slackware to run Asterisk on. Can anyone give me a list of what packages I need to install as I don't want X an all the associated bloat? Thanks in advance. Chris -- -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Peter & others. Here are three patches that does the following: #1 - Update kbuild part of klibc so make clean works Adds gzip including a sample kbuild file #2 - Factor out definition of usr/ to two variables #3 - Move kbuild files to reflect location in the kernel As requested in earlier mail I need a bit of guidiance of what you expect from the kernel integrated parts of klibc.

...te this list might not be the best >>> place to get a tutorial on using gdb on Windows. >> Essentially, the steps are: build with DEBUG=T (to have debug symbols), >> possibly updating EOPTS in MkRules.local to disable optimizations, then >> run gdb loading RGui, "set solib-search-path", run RGui from gdb. Then >> you can break to debugger from RGui menu, or just run the code that >> segfaults, and you get to gdb and can print the stacktrace, etc. You can >> find some information in rw-FAQ (R for Windows FAQ), but yes, it is >> harder than...

.../documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/libexec/dovecot/imap...done. [New LWP 20929] warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/imap'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f186087693a in fts_user_...

...n the Asterisk website I checked out the CVS source and started compiling... Zaptel and libpri combiled no problems, but when I got to Asterisk it ended up with the error cut out below. I'm guessing I've missed a dependency somewhere? I checked that I have the readline, openssl and openssl-solibs, along with the full kernel source installed. Can someone please point me in the right direction on how to get around this and get Asterisk to compile? Thanks in advance, Chris Lee =====CUT===== In file included from /usr/include/gtk-1.2/gtk/gtkarg.h:31, from /usr/include/gtk-...

...9;m happy to help but I appreciate this list might not be the best > place to get a tutorial on using gdb on Windows. Essentially, the steps are: build with DEBUG=T (to have debug symbols), possibly updating EOPTS in MkRules.local to disable optimizations, then run gdb loading RGui, "set solib-search-path", run RGui from gdb. Then you can break to debugger from RGui menu, or just run the code that segfaults, and you get to gdb and can print the stacktrace, etc. You can find some information in rw-FAQ (R for Windows FAQ), but yes, it is harder than on Linux. We can take care of t...

On Thu, Jun 26, 2014 at 3:39 PM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: > The main motivation for turning it off is that no known consumer (debugger) > took advantage of it. > > Turning it on does more than slightly increase the object file size, it can > cause the same source line to be listed multiple times in the .debug_line > table (with different

...st might not be >> the best place to get a tutorial on using gdb on Windows. > Essentially, the steps are: build with DEBUG=T (to have > debug symbols), possibly updating EOPTS in MkRules.local > to disable optimizations, then run gdb loading RGui, "set > solib-search-path", run RGui from gdb. Then you can break > to debugger from RGui menu, or just run the code that > segfaults, and you get to gdb and can print the > stacktrace, etc. You can find some information in rw-FAQ > (R for Windows FAQ), but yes, it is harder than...