search for: external

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

...the symbols of the assignPassManager virtual method from the various subclasses of llvm::Pass. Please advise! // the release version has all the necessary symbols in place before it is installed to /usr/local/bin $ nm -m Release+Asserts/bin/opt | grep assignPass 000000010042b7c0 (__TEXT,__text) external __ZN4llvm10ModulePass17assignPassManagerERNS_7PMStackENS_15PassManagerTypeE 00000001002a27c0 (__TEXT,__text) external __ZN4llvm10RegionPass17assignPassManagerERNS_7PMStackENS_15PassManagerTypeE 000000010042b490 (__TEXT,__text) external __ZN4llvm12FunctionPass17assignPassManagerERNS_7PMStackENS_15Pa...

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

...ke /opt/intel/compilo_9/l_cc_c_9.1.042/bin/icc -c99 -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c rsync.c -o rsync.o icc: Command line remark: option '-W' not supported proto.h(224): remark #310: old-style parameter list (anachronism) void setup_iconv(); ^ rsync.c(33): remark #1419: external declaration in primary source file extern int verbose; ^ rsync.c(34): remark #1419: external declaration in primary source file extern int dry_run; ^ rsync.c(35): remark #1419: external declaration in primary source file extern int preserve_perms; ^ r...

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 only supports the C99 standard. Note that I don't propose to use attribute((nonnull)) in the public API until we...

...ual method from the various > subclasses of llvm::Pass. > > Please advise! > > > // the release version has all the necessary symbols in place before it is > installed to /usr/local/bin > $ nm -m Release+Asserts/bin/opt | grep assignPass > 000000010042b7c0 (__TEXT,__text) external > __ZN4llvm10ModulePass17assignPassManagerERNS_7PMStackENS_15PassManagerTypeE > 00000001002a27c0 (__TEXT,__text) external > __ZN4llvm10RegionPass17assignPassManagerERNS_7PMStackENS_15PassManagerTypeE > 000000010042b490 (__TEXT,__text) external > __ZN4llvm12FunctionPass17assignPassMan...

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 unresolved external symbol _vorbis_comment_add unresolved external symbol _vorbis_comment_init unresolved external symbol _vorbis_info_clear unresolv...

...) 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 : error LNK2001: unresolved external symbol _vorbis_info_clear encoder_example.obj : error LNK2001: unresolved external symbol _vorbis_comment_clear encoder_example.obj : error LNK2001: unresolved external symbol _vorbis_dsp_clear encoder_example.obj : error LNK2001: unresolved external symbol _vorbis_block_clear encoder_example.obj :...

...module (there's also a Rmath module for the math library which I'm not yet concerned about). I'd specifically appreciate information on how to get started using these R API functions. If you're scared about OCaml, simply look at the two declarations below in the following way: external init_r : string array -> int = "init_r" 'external' means that this value is to be fetched by linking C code identified by the '= "init_r"' ending statement. Typically, 'external' values wrap the API functions. So this value is called init_r, and tak...

...module (there's also a Rmath module for the math library which I'm not yet concerned about). I'd specifically appreciate information on how to get started using these R API functions. If you're scared about OCaml, simply look at the two declarations below in the following way: external init_r : string array -> int = "init_r" 'external' means that this value is to be fetched by linking C code identified by the '= "init_r"' ending statement. Typically, 'external' values wrap the API functions. So this value is called init_r, and tak...

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 hidden. This issue exists at least on gcc 4.9 and before. Signed-off-by: Thomas Garnier <thgarnie at google.com> --- arch/x86/boot/boot.h...

...0.0186 > MultiSource/Applications/hbd/hbd.compile 6.34% 1.7050 1.8131 0.0110 > MultiSource/Benchmarks/Prolangs-C/TimberWolfMC/timberwolfmc.compile 6.34% > 8.0582 8.5687 0.0539 > MultiSource/Benchmarks/MiBench/automotive-susan/automotive-susan.compile 6.33% > 1.0136 1.0778 0.0021 > External/SPEC/CINT95/134_perl/134_perl.compile 6.31% 6.3453 6.7457 0.0206 > External/SPEC/CFP2006/433_milc/433_milc.compile 6.29% 3.6706 3.9015 0.0293 > External/SPEC/CINT2006/462_libquantum/462_libquantum.compile 6.26% 0.9149 > 0.9722 0.0070 > MultiSource/Applications/spiff/spiff.compile 6.25%...

...plied. class InlineReport The main class which summarizes the high level information in the inline report, including: (1) The values of the inlining threshold options (2) The "level" of the inlining report, which is a bit vector of feature options. For example, whether to print external functions and intrinsics, whether to print the inlining reasons, etc. (3) A map MF from each Function* to InlineReportFunction* (4) A map MCS from each CallSite* to InlineReportCallSite* In addition, the class InlineCost (from InlineCost.h) is augmented to include the primary reason a call...

...utput/simulator -5.3% MultiSource/Applications/hexxagon/Output/hexxagon -5.2% MultiSource/Applications/SIBsim4/Output/SIBsim4 -4.8% MultiSource/Benchmarks/MallocBench/cfrac/Output/cfrac -4.1% MultiSource/Applications/d/Output/make_dparser -4.0% MultiSource/Applications/JM/ldecod/Output/ldecod -3.9% External/Nurbs/Output/nurbs -3.7% MultiSource/Benchmarks/Ptrdist/bc/Output/bc -3.4% MultiSource/Applications/lemon/Output/lemon -3.4% SingleSource/Benchmarks/Misc-C++/Output/bigfib -3.4% External/SPEC/CFP2000/183.equake/Output/183.equake -3.2% MultiSource/Applications/hbd/Output/hbd -3.1% MultiSource/Applic...

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

...? 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. 3. Are there any llvm functionality that you need exposed to ocaml? Right now I plan to expose: add Union to TypeKind.t external union_type: llcontext -> lltype array -> lltype external union_element_types : lltype -> lltype array external build_indirect_br : llvalue -> int -> llbuilder -> llvalue external add_destination: llvalue -> llbasicblock -> unit external build_nsw_add : llvalue -> llval...