search for: externalization

Hello Samba experts, due to the "SambaCry" issue (CVE-2017-7494), I am trying to update the Samba server installation on my Thecus NAS (dating back to 2011) from version 3.5.16 to the current 4.6.4. So far, I have successfully * created a cross-compiling toolchain for the NAS (i686-nptl-linux-gnu) based on gcc-5.2 * compiled Python and Samba library dependencies for my

Hello again, Samba experts, sorry for being such a pain in your necks, but I really need to get a recent Samba version to compile, and it looks like I definitely need your help with this. In the meantime, I have found that the huge number of "conflicting types" errors for rpc_*_init(...) is due to the fact that the Samba 4.6.4 codebase seems to have for all RPC modules: NTSTATUS

This is #defined as empty at the moment, but it allows the Windows port to define this __declspec(dllexport), which is necessary for symbols to be exported in DLLs. --- include/nbdkit-common.h | 86 ++++++++++++++++++++++++----------------- include/nbdkit-filter.h | 42 +++++++++++++------- include/nbdkit-plugin.h | 6 +-- server/main.c | 2 + 4 files changed, 83 insertions(+), 53

Hi all, This is a problem that occurs for me only on Darwin (MacOS) and not on Linux. When llvm 2.8 (or 2.9) is compiled with ENABLE_OPTIMIZED=1, the "opt" tool fails to load LLVM passes in dynamic libraries (.dylib) files, regardless of how they themselves were built. When opt is built with ENABLE_OPTIMIZED=0, all is well. Here is some informative output. Seems to me the problem is

Annotate some function parameters with attribute((nonnull)). Only do this for internal headers where we are sure that we will be using sufficiently recent GCC or Clang. For the public header files (ie. include/nbdkit-*.h) it may be that people building out of tree plugins are using old GCC which had problems, or even other compilers that don't support this extension at all. Libvirt has an

I got numerous warnings when building rsync on IA64 (Itanium-2) using Intel C/C++ compiler (see attached). Is this expected? Thanks, Michael -------------- next part -------------- Script started on Fri 21 Sep 2007 06:14:05 PM BST ~/src$ ls -alt total 222884 -rw-r--r-- 1 mccssmb2 mcc101 0 Sep 21 18:14 build_rsync drwxr-xr-x 8 mccssmb2 mcc101 4096 Sep 21 18:14 . -rw-r--r-- 1

v1 was here: https://www.redhat.com/archives/libguestfs/2019-January/msg00008.html In v2 I have provided two patches: The first patch extends attribute((nonnull)) to most internal functions, but not to the external API. The second patch uses a macro so that attribute((format)) is only used in the public API on GCC or Clang. At least in theory these headers could be used by a C compiler which

I see now that this clearly to the problem raised elswhere, for example: http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-December/036764.html http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-November/036289.html So clearly a repeating issue on the MacOS platform. Harel On Sun, Dec 12, 2010 at 5:10 PM, Harel Cain <harel.cain at gmail.com> wrote: > Hi all, > > This is a problem

Ok... This is begining to go a bit better.... I have compiled 4 lib's and placed them in my lib path. ogg.lib vorbis.lib vorbisenc.lib vorbisfile.lib When I try and compile oggenc.c I still have link errors.. unresolved external symbol _vorbis_comment_clear unresolved external symbol _optind unresolved external symbol _optarg unresolved external symbol _vorbis_comment_add_tag

Hi, I'm a highschool student, I'm looking for information about converting Wave file (*.wav) into Ogg file (*.ogg) and i found encoder_example.c inside libvorbis's example directory. I try to compile it using Microsoft Visual C++ 6.0 ,but it goes error like this : --------------------Configuration: encoder_example - Win32 Debug-------------------- Linking... encoder_example.obj :

Hello. I've been pulling together a Debian package out of Maxence Guesdon's OCaml bindings for R. Will be available from my website as soon as I get my router to obey me. Here's Maxence's bindings: http://pauillac.inria.fr/~guesdon/ocaml-r.en.html The purpose of this software is to access R from OCaml programs. However, my issue is that after having pulled things to a Debian

Hello. I've been pulling together a Debian package out of Maxence Guesdon's OCaml bindings for R. Will be available from my website as soon as I get my router to obey me. Here's Maxence's bindings: http://pauillac.inria.fr/~guesdon/ocaml-r.en.html The purpose of this software is to access R from OCaml programs. However, my issue is that after having pulled things to a Debian

From: "Richard W.M. Jones" <rjones at redhat.com> --- configure.ac | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/configure.ac b/configure.ac index fa97479..6e42423 100644 --- a/configure.ac +++ b/configure.ac @@ -141,6 +141,10 @@ if test "$gl_gcc_warnings" = yes; then # Work around warning in src/inspect.c. This seems to be a bug in gcc

Provide an option to default visibility to hidden except for key symbols. This option is disabled by default and will be used by x86_64 PIE support to remove errors between compilation units. The default visibility is also enabled for external symbols that are compared as they maybe equals (start/end of sections). In this case, older versions of GCC will remove the comparison if the symbols are

A big compile time regression. Any ideas? Ciao, Duncan. On 22/07/11 19:13, llvm-testresults at cs.uiuc.edu wrote: > > bwilson__llvm-gcc_PROD__i386 nightly tester results > > URL http://llvm.org/perf/db_default/simple/nts/253/ > Nickname bwilson__llvm-gcc_PROD__i386:4 > Name curlew.apple.com > > Run ID Order Start Time End Time > Current 253 0 2011-07-22 16:22:04

RFC: Inlining Report Motivation Making good inlining choices while optimizing an application is often key to achieving optimal performance. While the compiler's default inlining heuristics sometimes provide great out-of-box results, optimal performance is sometimes achieved only after varying the settings of certain compiler options related to inlining or adding "always_inline" or

Perhaps you noticed that LLVM gained a new optimizing register allocator yesterday (r130568). Linear scan is going away, and RAGreedy is the new default for optimizing builds. Hopefully, you noticed because your binaries were suddenly 2% smaller and 10% faster*. Some noticed because LLVM started crashing or miscompiling their code. Greedy replaces a fairly big chunk of the code generator, so

On (05/09/16 11:20), Minchan Kim wrote: [..] > +++ b/include/linux/migrate.h > @@ -32,11 +32,16 @@ extern char *migrate_reason_names[MR_TYPES]; > > #ifdef CONFIG_MIGRATION > > +extern int PageMovable(struct page *page); > +extern void __SetPageMovable(struct page *page, struct address_space *mapping); > +extern void __ClearPageMovable(struct page *page); > extern

On (05/09/16 11:20), Minchan Kim wrote: [..] > +++ b/include/linux/migrate.h > @@ -32,11 +32,16 @@ extern char *migrate_reason_names[MR_TYPES]; > > #ifdef CONFIG_MIGRATION > > +extern int PageMovable(struct page *page); > +extern void __SetPageMovable(struct page *page, struct address_space *mapping); > +extern void __ClearPageMovable(struct page *page); > extern

I'm in the process of finishing up the ocaml llvm bindings, and I had some last minute questions before we code freeze: 1. What version of ocaml is everyone using, and how old of an ocaml version do you need to support? 2. Would it be alright if I renamed some functions? Module providers are being removed for 2.7. I can keep the old functions around, but I'd prefer to keep the API clean.