similar to: [PATCH] Dont bypass compiler driver for Dependency generation options

> On Sep 13, 2015, at 11:04 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > On Thu, Sep 10, 2015 at 1:55 AM, Khem Raj via Syslinux > <syslinux at zytor.com> wrote: >> We can let compiler driver pass the right options to preprocessor after >> processing -Mxy options, right now its bypassing the gcc driver and >> handing them straight to cpp >>

On Mon, Sep 14, 2015 at 1:36 AM, Khem Raj <raj.khem at gmail.com> wrote: > >> On Sep 13, 2015, at 11:04 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Thu, Sep 10, 2015 at 1:55 AM, Khem Raj via Syslinux >> <syslinux at zytor.com> wrote: >>> We can let compiler driver pass the right options to preprocessor after >>> processing

On Thu, Sep 10, 2015 at 1:55 AM, Khem Raj via Syslinux <syslinux at zytor.com> wrote: > We can let compiler driver pass the right options to preprocessor after > processing -Mxy options, right now its bypassing the gcc driver and > handing them straight to cpp > > This also helps in other compilers processing these options correctly > for their preprocessors consumption

Why will this simple statement not work? I think I am following the documentation for if(cond) statements, and I have tried wrapping the cons.expr and alt.expr in {}, I get the same error. There is no example in the help file, and this is not covered in the Introduction to R, SimpleR or other tutorials I have looked into. mxx=max(cpx_list$nMV); mxy=max(trend_list$nMV); if (mxx>mxy) mxy=mxx

Jan suggested a couple of cleanups based upon my "xen: allow architecture to choose whether to compress installed xen binary" patch. So this series now consists of: xen: allow architecture to choose how/whether to compress installed xen binary xen: x86: drop the ".gz" suffix when installing xen: Use $(T) and $(D) aliases in install target This is based

From: Ian Campbell <ian.campbell@citrix.com> The zImage compatible binary is the useful one on real hardware. The relocated ELF thing is only really useful when booting directly on Fast Models. The customary suffix for that case is .axf so provide that as a target. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Wookey <wookey@linaro.org> --- xen/arch/arm/Makefile |

Hi Khem, On Fri, Mar 10, 2017 at 1:03 PM, Khem Raj via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Fri, Mar 10, 2017 at 7:01 AM, Renato Golin via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> ARM and AArch64 looking good, uploaded. >> > > This is not particularly related to this RC but in general with 4.0.0 > I am seeing a failure quite common

# HG changeset patch # User Matt Wilson <msw@amazon.com> # Date 1342481836 0 # Branch efi # Node ID dd1ab0cae2c870942c2e1b6bc3a507b1a40dae16 # Parent 9950f2dc2ee6dfd172258a5a4ee29809b0ff8263 x86/EFI: define and use EFI_DIR make variable, defaulting to /usr/lib64/efi After commit 25594:ad08cd8e7097, EFI Xen binaries were installed to /efi instead of /usr/lib64/efi. This patch restores the

On Mon, Mar 13, 2017 at 10:09 PM, Khem Raj <raj.khem at gmail.com> wrote: > Hi Hans > > On 3/10/17 1:10 PM, Hans Wennborg wrote: >> Hi Khem, >> >> On Fri, Mar 10, 2017 at 1:03 PM, Khem Raj via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> On Fri, Mar 10, 2017 at 7:01 AM, Renato Golin via llvm-dev >>> <llvm-dev at

Hi together, this is the second version of my cross-compilation patch serie. I'm sending it in the hope to get an honest review, and possibly see the patches integrated upstream. Those patches allow to build syslinux using a toolchain different from the host one by explicitely using the host toolchain for the utilities that are required at build-time / on the build machine. I am using the

Hello all, Past few days I was working on porting the isohybrid perl script to c. (-> https://fedorahosted.org/fedora-engineering-services/ticket/15) The first patch towards the same is attached with this mail. And the same could also be accessed from: http://pjp.dgplug.org/tools/syslinux-3.86-isohybrid.patch I would really appreciate it if somebody could have a look at it and let me know

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

Good summer, all! This patch enables ENABLE_SHARED=1 to build DLL based LLVM toolchain. I have checked this on Cygwin-1.5, Cygwin-1.7, mingw(msysgit) and mingw-cross-fedora12. I can separate this patch into some parts; cleanups, adding definitions and adding rules. Any feedbacks are welcome. Have fun! ...Takumi * Pros - reduction of linking time of toolchain. - capability of -load

If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've written a function in R which takes a symmetrical matrix as input and processes all triplicate combinations of values from the matrix. The function looks something like: my_fun <- function(m) { if( nrow(mat) != ncol(mat) ) { stop("'m' must be a square matrix") } size <- nrow(m) for(x in 1:(size -2)) {

In https://gitlab.com/nbdkit/nbdkit/-/merge_requests/30, Khem reports that in a cross-compilation environment, nbdkit embeds the absolute name of the cross-compiler into the resulting cc plugin, even though running the plugin should be favoring the bare name 'cc'. This in turn leads to non-reproducible builds. As the goal of cross-compiling nbdkit is to produce a binary that behaves

ARM and AArch64 looking good, uploaded. 4e62f3d5dcc95189eaec2d950950876a423f8a8c clang+llvm-4.0.0-aarch64-linux-gnu.tar.xz 1b031f16683e3bcd779f50e6d47d0d1f3f265e9f clang+llvm-4.0.0-armv7a-linux-gnueabihf.tar.xz On 10 March 2017 at 12:14, Ben Pope via cfe-dev <cfe-dev at lists.llvm.org> wrote: > On 09/03/17 00:52, Hans Wennborg via cfe-dev wrote: >> >> Dear testers, >>

On Fri, Aug 18, 2023 at 08:27:45AM -0500, Eric Blake wrote: > In https://gitlab.com/nbdkit/nbdkit/-/merge_requests/30, Khem reports > that in a cross-compilation environment, nbdkit embeds the absolute > name of the cross-compiler into the resulting cc plugin, even though > running the plugin should be favoring the bare name 'cc'. This in > turn leads to non-reproducible

Dear James, Thank you for being quick to help. Yes, I could see all of them: # vgs # lvs # pvs Regards, Khem On Sat, February 28, 2015 7:37 am, James A. Peltier wrote: > > > ----- Original Message ----- > | Dear All, > | > | I am in desperate need for LVM data rescue for my server. > | I have an VG call vg_hosting consisting of 4 PVs each contained in a > | separate

Anybody having success building an LLVM.dll in this configuration? It's failing for me, in tools/llvm-shlib, with an error suggesting that the gcc ld doesn't understand the format of the exports map being generated. (plain configure && make works just fine, it's just this shared option that fails; google shows support for --enable-shared was added around 2.7 timeframe and