similar to: wasteful cmake defaults

Yeah, that's one I'd be in favor of fixing, if it's still the case. On Tue, Nov 17, 2020 at 5:38 PM Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I'm curious how much of this is due to not using LLD? Last I checked, using ld.bfd instead of LLD (or gold) was one of my major build time issues, and somehow our default configuration would use ld.bfd. >

Just trying to understand: Are you suggesting a way to have a “-O0” build without all the debug information? -Min > On Nov 17, 2020, at 10:25 AM, Luke Drummond via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all > > I wanted to do a quick build of a clean branch yesterday and noticed > something surprising in the configure log: > >> -- No build type

I'm curious how much of this is due to not using LLD? Last I checked, using ld.bfd instead of LLD (or gold) was one of my major build time issues, and somehow our default configuration would use ld.bfd. -- Sean Silva On Tue, Nov 17, 2020 at 10:25 AM Luke Drummond via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi all > > I wanted to do a quick build of a clean branch

On Tue, Nov 17, 2020 at 10:25 AM Luke Drummond via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all > > I wanted to do a quick build of a clean branch yesterday and noticed > something surprising in the configure log: > > > -- No build type selected, default to Debug > > It appears that llvm's configuration forces Debug builds if the user > does

On Tue Nov 17, 2020 at 10:35 PM GMT, Michael Kruse wrote: > Am Di., 17. Nov. 2020 um 12:46 Uhr schrieb Luke Drummond via llvm-dev > <llvm-dev at lists.llvm.org>: > > > > On Tue Nov 17, 2020 at 6:37 PM GMT, Min-Yih Hsu wrote: > > > > > Just trying to understand: Are you suggesting a way to have a “-O0” > > > build without all the debug information?

Hi all I wanted to do a quick build of a clean branch yesterday and noticed something surprising in the configure log: > -- No build type selected, default to Debug It appears that llvm's configuration forces Debug builds if the user does not specify the build type. https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60

On 17/11/2020 18:25, Luke Drummond via llvm-dev wrote: >> -- No build type selected, default to Debug > It appears that llvm's configuration forces Debug builds if the user > does not specify the build type. > > https://github.com/llvm/llvm-project/blob/9218ff50f93085d0a16a974db28ca8f14bc66f64/llvm/CMakeLists.txt#L57-L60 > > I've just done a build of llvm and

On Tue Nov 17, 2020 at 6:37 PM GMT, Min-Yih Hsu wrote: > Just trying to understand: Are you suggesting a way to have a “-O0” > build without all the debug information? > Exactly.

Am Di., 17. Nov. 2020 um 12:46 Uhr schrieb Luke Drummond via llvm-dev <llvm-dev at lists.llvm.org>: > > On Tue Nov 17, 2020 at 6:37 PM GMT, Min-Yih Hsu wrote: > > > Just trying to understand: Are you suggesting a way to have a “-O0” > > build without all the debug information? > > > Exactly. What is such a build useful for the average user? If changing the

Sorry my example wasn't helpful. I did take a quick look at rust -- though I didn't download or try to build it -- and they seem to allow you to use an installed or prebuilt version in addition to building it in-tree. However, even when they build it in-tree, they build the whole thing -- see mk/llvm.mk. Good luck... On Mon, Oct 10, 2016 at 1:33 AM, Timo Janssen via llvm-dev <

Hi Timo: You need to find LLVMConfig.cmake in the binary or install directory tree, not the source tree. Although I don't embed clang/llvm, my config might help you figure it -- clang/llvm installed under (could have used build directory) ~/usr : $ cd /Users/dhinton/projects/cover/build/ && rm -rf * && CC=~/usr/bin/clang CXX=~/usr/bin/clang++ LLVM_DIR=~/usr/lib/cmake/llvm

Hi Christian Adam, Thanks for pointing this out, I made the necessary changes to account for this. So the behavior is as follows: * If no CMAKE_BUILD_TYPE is set and no CFLAGS are set it will default to Release. i.e ( cmake .. ) * If a developer want full control then use export CFLAGS in leave CMAKE_BUILD_TYPE empty. * If a developer want to test CFLAGS in combination with

Hi all. Running 2.0.4b on a (now) solaris 2.6 box. Since the upgrade the smbd & nmbd daemons won't start. I tried starting smbd by hand, running it through truss. Here's the last few lines: getuid() = 0 [0] fstat(3, 0xEFFFF858) = 0 write(3, " [", 1) = 1 write(3, " 1 9 9 9 / 0

Am Mi., 18. Nov. 2020 um 05:32 Uhr schrieb David Chisnall via llvm-dev <llvm-dev at lists.llvm.org>: > In terms of the most useful build configuration to be the default, I > think there are a bunch of users that we need to consider: > > - Developers of LLVM > - Developers of downstream projects that use LLVM > - Package builders > - CI admins. This is missing

On 18/11/2020 18:03, Michael Kruse wrote: > This is missing the probably largest group: Users of clang who compile > clang themselves (e.g. because their OS does not come with a package > for clang, or is too old) I think our target for this group should be that it is size 0. Windows, macOS, and *BSD all have up-to-date packages of the latest version, as do many Linux distros. We

On 18/11/2020 18:40, Michael Kruse wrote: > First, it is not rare that you are working on an LTS release, but need > a newer compiler. I myself am still working on a remote machine using > Red Hat EL7 with gcc 4.8 and no clang pre-installed. We build nightly packages for Ubuntu LTS releases, what do we need to do to add the same support for Red Hat? > Since I am not > the admin

I get the following errors on the console of my newly installed 2.0.4b server on a Sun E4000: nmbd/nmbd_packets.c: (1412) find_subnet_for_nmb_packet: response record not found for response id <num>. nmbd/nmbd_responserecordsdb.c: (240) find_response_record: response packet id <num> received with no matching record I don't know the internals well enough to decipher these, can

Hi, I did this: $ cmake -DCMAKE_INSTALL_PREFIX=~/llvm-2.8 -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 .. $ make $ make install Still didn't install the headers. $ cd ~/llvm-2.8/include/ $ ls -la total 0 drwxr-xr-x 2 samuel staff 68 1 Oct 12:47 . drwxr-xr-x 6 samuel staff 204 1 Oct 12:47 .. Libraries and binaries installed fine: $ cd ../lib/ $ ls -la total 44600

Hi, I have a dynamically loaded llvm pass built in-tree with ninja (generated with cmake, basically a copy of the hallo pass plugin, linux, llvm/clang version 6.0.1). It uses the ExecutionEngine. Building it without linking against LLVMExecutionEngine library results in an undefined symbol to the vtable of the EngineBuilder when loaded to opt. Linking the plugin with LLVMExecutionEngine results in

Hi all. Is it possible to have a generic share like [homes] that hides all user home dir shares by default by appending a "$" to them? I'd search the archives but they have not yet been tx'd. I realise there is "browse vs nobrowse" but I specifically need to have end users map to \\srv\user$ rather than \\srv\user. -- Mark