search for: reloctable

Hi. I am running the as.ltraj () function in adehabitat (v 1.4 under R 2.2.1) but can't seem to correctly specify the burst argument. i.e., the ltraj object returned consists of only one component, when in fact my data consist of more than one burst of reloctions per animal. i've set up the data (xy, date, id, burst) in list form following the example given in ?as.ltraj. to simplify,

...be rendered) - Tags (the known webgen tags system) The tags content processor has slightly been updated. It allows now to specify a body that can be processed. So it is possible to wrap some source code in a (to be written) highlight tag and it gets highlighted. * Implemented tags: - Reloctable - Metainfo (the default tag which provides access to metainformation) - Menu The main webgen command is not very sophisticated, it just can build a website. But partial site generation works throughout the entire codebase. Everything is unit tested and current code coverage is around 92%. Any...

Hi hpa & others. Following is a list of issues that I hope to be addressed soon so we are in even better shape for -mm inclusion. 1) rebuild initramfs when content changes. > It is a simple matter of copying in usr/Makefile from the latest > -linus kernel and replace the 10 first lines with the content from > klibc Kbuild file. 2) havesyscalls.h is not deleted after make

...- -.PHONY: $(subdir-y) $(user-dirs) -$(subdir-y) $(user-dirs): - $(Q)$(MAKE) $(klibc)=$@ - -# Add FORCE to the prequisites of a target to force it to be always rebuilt. -# --------------------------------------------------------------------------- - -.PHONY: FORCE - -FORCE: - -# Linking -# Create a reloctable composite object file -# --------------------------------------------------------------------------- -quiet_cmd_userld = USERLD $@ - cmd_userld = $(USERLD) -r $(USERLDFLAGS) \ - $(EXTRA_USERLDFLAGS) $(USERLDFLAGS_$(@F)) \ - $(filte...

...bj)/socketcalls.mk +endif # Composite object containing all .o file always := socketcalls.o @@ -17,7 +19,7 @@ klibc-dir := $(srctree)/usr/klibc targets := socketcalls.o targets += socketcalls.mk targets += $(socketcall-objs) -clean-files += *.o +clean-files += *.S *.o # Create reloctable composite object file $(obj)/socketcalls.o: $(call objectify,$(socketcall-objs)) FORCE diff --git a/klibc/syscalls/Kbuild b/klibc/syscalls/Kbuild --- a/klibc/syscalls/Kbuild +++ b/klibc/syscalls/Kbuild @@ -4,7 +4,9 @@ # Include automatically generated Makefile fragment. # It contains definitio...

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.

...nternally in order to rearrange (aside >> - there's some interesting crossover with ideas I've been considering >> regarding the Fragmented DWARF topic discussed elsewhere). I'm still learning the internals but would expect that mixed DWARF32/DWARF64 is a problem for LTO. A reloctable link (-r) can combine DWARF32/DWARF64 object files and potentially nullify the aforementioned relocation based approach (we probably just want to check the first relocation to save time; if we link DWARF64 before DWARF32 we may create a .debug_info which looks like DWARF64 but is actually restricte...

...+.PHONY: $(subdir-y) $(klibc-dirs) +$(subdir-y) $(klibc-dirs): + $(Q)$(MAKE) $(klibc)=$@ + +# Add FORCE to the prequisites of a target to force it to be always rebuilt. +# --------------------------------------------------------------------------- + +.PHONY: FORCE + +FORCE: + +# Linking +# Create a reloctable composite object file +# --------------------------------------------------------------------------- +quiet_cmd_klibcld = KLIBCLD $@ + cmd_klibcld = $(KLIBCLD) -r $(KLIBCLDFLAGS) \ + $(EXTRA_KLIBCLDFLAGS) $(KLIBCLDFLAGS_$(@F)) \ + $...

...nternally in order to rearrange (aside >> - there's some interesting crossover with ideas I've been considering >> regarding the Fragmented DWARF topic discussed elsewhere). I'm still learning the internals but would expect that mixed DWARF32/DWARF64 is a problem for LTO. A reloctable link (-r) can combine DWARF32/DWARF64 object files and potentially nullify the aforementioned relocation based approach (we probably just want to check the first relocation to save time; if we link DWARF64 before DWARF32 we may create a .debug_info which looks like DWARF64 but is actually restricte...

On Wed, Nov 11, 2020 at 12:55 AM James Henderson <jh7370.2008 at my.bristol.ac.uk> wrote: > > > > On Wed, 11 Nov 2020 at 05:41, David Blaikie <dblaikie at gmail.com> wrote: >> >> +James for context too (always good to include the folks from the >> original threads for continuity) >> >> Yeah, my general attitude there was just twofold, one that

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at: