similar to: [LLVMdev] LLVM triple and Apple ld64 behavior

Hi, I just added an external classifier script, and things are not working as I expected to. Trying to read documentation about ext.nodes and searching the archives I couldn''t come up with any useful results. My classifier script outputs: --- YAML --- classes: - geodns::production::backend environment: production name: z01-06-02 parameters: puppet_server:

Hi, Is there any up to date info on the state of lld in darwin mode? I realize it's not being updated much, but does it work for all darwin targets? Are there things that don't work?

I believe it doesn't work. It might work at simple cases. 2018-02-07 10:16 GMT-02:00 Carlo Kok via llvm-dev <llvm-dev at lists.llvm.org>: > Hi, > > Is there any up to date info on the state of lld in darwin mode? I realize > it's not being updated much, but does it work for all darwin targets? Are > there things that don't work? >

Could I use my local laptop as a puppet master, and only start up the puppetmaster when I have a change I want to send over to the nodes? Say I only have 1 server, and I don''t want or even need a puppetmaster running all the time. Is this or something close to this type of setup possible? -- You received this message because you are subscribed to the Google Groups "Puppet

Dear Group, I'm using samba 3 as a pdc. And when I try to syncronize the time from a client I get: net time \\cosimo /set Current time at \\cosimo is 1/13/2006 12:34 AM Local time (GMT +01:00) at \\cosimo is 1/13/2006 9:34 AM The Command completed successfully ? ?? ?? ?? ?? ?? ?? ?? ?? ? Now the right time is the Local time (9:34AM) but the client gets the Current time which is completely

Thanks for your reply. Two questions: 1). Will ld64.lld be fixed in LLVM v11.0 and when is this likely to be? 2). You mention Apple’s linker, by which I assume you mean GNU’s ld. Is it possible to get a binary version of ld (preferably that does not use other things from /usr/bin)? Thanks > On 7 May 2020, at 12:26, James Y Knight <jyknight at google.com> wrote: > > The MachO

James, many thanks. Is there any linker available for Macs that has a freely available binary version? I thought maybe that GNU’s linker might fit the bill? I cannot use Apple’s linker from /usr/bin/ as it is not allowed to make external calls from a sandboxed app. Hence my interest in the LLVM lld. > On 7 May 2020, at 19:21, James Y Knight <jyknight at google.com> wrote: > > On

Dear LLVM community I need some help please. I want to use LLVM's clang and lld within a MacOSX sandboxed app. This is because sandboxing does not allow calls to /usr/bin/clang. The clang binary works fine to compile a file, but ld64.lld comes up with the error "cannot find framework". However similar arguments using /usr/bin/ld instead of ld64.lld works fine. Here are the

Josh, Once more patch. The gcc on Linux PowerPC does not have the -force_cpusubtype_ALL flag. On the Debian man page, that compiler option is listed as being Darwin specific. Erik --- src/libFLAC/Makefile.am 30 Jan 2005 18:44:46 -0000 1.58 +++ src/libFLAC/Makefile.am 31 Jan 2005 02:33:14 -0000 @@ -40,7 +40,7 @@ CPUCFLAGS = -faltivec -force_cpusubtype_ALL -DFLAC__NO_ASM else

Hi Rui, The motivation would be primarily that LLVM/Clang/LLD are community projects such that if I or someone in the community added support for e.g. symbol aliases, then it could be reviewed and potentially merged. ld64 on the other hand does not have a community process for patch submission and code review that I am aware of so its unlikely that if someone from the community came up with a

Hi Folks, I have a question regarding LLD support for ld64 mach-o linker synthesised symbols. I did a quick search of the LLD source and I can not find support for them so before I start trying to use lld I thought I would ask. I have found a couple of cases where they are essential. i.e. where there is no other way to get the required information, such as getting the address of the mach-o

This is also pretty simple. Just a small patch to configure.in to set the right compiler flags and changes to os.h to (a) not have deeply nested ifdefs, making the file needlessly hard to read, (b) break up the sections by functionality and (c) don't assume that every non-Win32 has the floating versions of math library functions. -tim Index: configure.in

Hi, I offered some time ago to do some build cleanup. Today I did so and here's my slew of patches. Basically, they - touch ogg, vorbis, vorbis-tools and theora - fix a bunch of autotools issues - uniformize the use of them across the four - fix compile/link flags - use pkgconfig if it's available to detect flags - for vorbis-tools, generate and use config.h - add -uninstalled .pc stuff

Hi, I offered some time ago to do some build cleanup. Today I did so and here's my slew of patches. Basically, they - touch ogg, vorbis, vorbis-tools and theora - fix a bunch of autotools issues - uniformize the use of them across the four - fix compile/link flags - use pkgconfig if it's available to detect flags - for vorbis-tools, generate and use config.h - add -uninstalled .pc stuff

On Aug 15, 2012, at 11:56 PM, Eli Friedman wrote: > On Wed, Aug 15, 2012 at 10:17 PM, Carl Norum <carl at lytro.com> wrote: >>> -march=mips32r2 >>> -mtune=4kem >>> -msoft-float >>> -EL >>> >>> -Xclang -triple -Xclang mipsel-sde-elf >>> -Xclang -mrelocation-model -Xclang static >>> >>>

Folks; I am having a hell of a time trying to get IceCast 2.0 installed on an Apple XServe running OS X 10.2.3. The problem seems to stem from one of the libraries required by IceCast, specifically libvorbis. When running MAKE in an attempt to install libvorbis I get the following: <p>Making all in examples /bin/sh ../libtool --mode=link gcc -DDARWIN -fno-common

I'm using llvm-2.5 on OS X 10.5 and having a problem getting debug info from my compiler into a resulting executable. My code flow is: LLVM API -> Assembly file .s -> gcc to .dylib I'm using DIFactory to generate the debug info, and my usage seems to match what clang's CGDebugInfo would do. In my resulting assembly file, I see the DWARF sections with apparently valid

Small remark: > diff --git a/src/libFLAC/Makefile.am b/src/libFLAC/Makefile.am > index 13ab593..aa88100 100644 > --- a/src/libFLAC/Makefile.am > +++ b/src/libFLAC/Makefile.am > @@ -34,6 +34,9 @@ noinst_LTLIBRARIES = libFLAC-static.la > if DEBUG > DEBUGCFLAGS = -DFLAC__OVERFLOW_DETECT > endif > + > +# FIXME: The following logic should be part of configure, not of

Besides SPE (FSL e500v? cores) there are other powerpc processors that don't support altivec instructions so only enable them when it's 100% sure that the target has it. Signed-off-by: Gustavo Zacarias <gustavo at zacarias.com.ar> --- src/libFLAC/Makefile.am | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/libFLAC/Makefile.am b/src/libFLAC/Makefile.am index

lvqcl wrote: > FLAC__lpc_restore_signal_asm_ia32_mmx compares 'order' argument with 4 > and if it's greater then it jumps to FLAC__lpc_restore_signal_asm_ia32. > > I wonder why the same wasn't done for PPC/Altivec: why libFLAC compares > 'order' and 8 in C code and not in asm. ...more about PPC ASM: