Displaying 20 results from an estimated 2000 matches similar to: "Gcc-4.9.0 trunk revision 208516 cannot compile openssh package with -flto"
2013 Jun 10
1
[LLVMdev] gcc-4.8.1 -flto, error for visibility of LLVMX86CompilationCallback2?
I tried to compile LLVM with gcc-4.8.1 -flto. I got the following error, when linking lli, llc, opt, or libLTO.so:
`LLVMX86CompilationCallback2' referenced in section `.text' of /tmp/cclv7BYB.ltrans0.ltrans.o: defined in discarded section `.text' of X86JITInfo.o (symbol from plugin)
collect2: error: ld returned 1 exit status
Removing the LLVM_LIBRARY_VISIBILITY attribute for
2013 Jun 12
2
[LLVMdev] [PATCH] gcc-4.8.1 -flto, error for visibility of LLVMX86CompilationCallback2?
Thanks, now it links.
If nobody objects, I will commit the following patch:
diff --git a/lib/Target/X86/X86JITInfo.cpp b/lib/Target/X86/X86JITInfo.cpp
index 44d8cce..8acc220 100644
--- a/lib/Target/X86/X86JITInfo.cpp
+++ b/lib/Target/X86/X86JITInfo.cpp
@@ -339,6 +339,8 @@ extern "C" {
/// must locate the start of the stub or call site and pass it into the JIT
/// compiler function.
2023 Nov 12
1
Segmentation fault early in compilation of revision 85514
When trying to compile R on Windows 10 64-bit using LTO as I always do, I
encountered a segmentation fault early in the compilation. I am uncertain
as to what it means (please see below for error extract). I am using the
most recent version of Rtools43 (5863) and updated its libraries prior to
starting the build. My EOPTS is " -march=native -pipe -mno-rtm" and my
2017 May 31
1
[Dovecot-news] v2.2.30.1 released
Am 31.05.2017 um 15:24 schrieb Timo Sirainen:
> https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz
> https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig
>
> Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another
2017 May 31
2
[Dovecot-news] v2.2.30.1 released
Am 31.05.2017 um 16:35 schrieb Timo Sirainen:
> On 31 May 2017, at 16.53, Reindl Harald <h.reindl at thelounge.net
> <mailto:h.reindl at thelounge.net>> wrote:
>>
>> LTO build is as broken as 2.2.30
>>
>> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s
>> "../lib10_quota_plugin.la"
2017 May 31
0
[Dovecot-news] v2.2.30.1 released
On 31 May 2017, at 16.53, Reindl Harald <h.reindl at thelounge.net> wrote:
>
> LTO build is as broken as 2.2.30
>
> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s "../lib10_quota_plugin.la" "lib10_quota_plugin.la" )
> /tmp/ccGO7JSw.ltrans4.ltrans.o:<artificial>:function
2017 May 31
0
[Dovecot-news] v2.2.30.1 released
On 31 May 2017, at 18.03, Reindl Harald <h.reindl at thelounge.net> wrote:
>
>>> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s "../lib10_quota_plugin.la" "lib10_quota_plugin.la" )
>>> /tmp/ccGO7JSw.ltrans4.ltrans.o:<artificial>:function imapc_quota_refresh.lto_priv.22: error: undefined
2013 Jun 12
2
[LLVMdev] "anchor" method policy, request for clarification
I tried to build LLVM with 'gcc-4.8.1 -flto', and when linking unittest programs, I got the following error:
/tmp/cc8pMk84.ltrans30.ltrans.o:(.data.rel.ro._ZTIN4llvm2cl15OptionValueCopyISsEE[_ZTIN4llvm2cl15OptionValueCopyISsEE]+0x10): undefined reference to `typeinfo for llvm::cl::GenericOptionValue'
2013 Jun 12
0
[LLVMdev] "anchor" method policy, request for clarification
(+Chris, since I assume he wrote this policy - and, as I said in my
previous email, I wouldn't mind seeing some justification or just
seeing the rule go away & drop the anchors I added previously (or, if
we're going to keep it, we could add more anchors & actually get to
the point where we're -Wweak-vtable clean & enable that warning))
On Wed, Jun 12, 2013 at 1:44 PM,
2014 May 13
1
Performance tests of the current version (git-b1b6caf)
Current sources (git-b1b6caf) were compiled with GCC 4.8.2 and GCC 4.9.0
with various -msseN options (the default is -msse2). Then I took two WAV
files (one is 16-bit and the other is 24-bit) and compressed them using
best compression mode. The results are in the table below.
(please remember that the resulting value is an encoding time, not encoding speed)
CPU: Intel Core i7 950 (up to SSE4.2)
2019 May 11
1
R problems with lapack with gfortran
Hi,
gfortran trunk and 9-branch now have an option to automatically
generate C prototypes for old-style F77 procedures. I just did
for a in *.f; do gfortran -fsyntax-only -fc-prototypes-external $a >
${a%.f}.h; done
in the src/modules/lapack directory. This generates header
files which contain prototypes like
int ilaenv_ (int *ispec, char *name, char *opts, int *n1, int *n2, int
*n3,
2019 Sep 12
0
Fwd: Launchpad [Bug 1843743] [NEW] klibc ftbfs in eoan
---------- Forwarded message ----------
From: Matthias Klose <doko at ubuntu.com>
Message-ID:
<156829951299.6967.9341353260688596797.malonedeb at soybean.canonical.com>
Date: Thu, 12 Sep 2019 14:45:12 -0000
Subject: [Bug 1843743] [NEW] klibc ftbfs in eoan
Reply-To: Bug 1843743 <1843743 at bugs.launchpad.net>
Public bug reported:
2011 May 31
0
[XEN-NVIDIA] Update 270.41.06 Failed
Hi,
I tried to Update the Nvidia driver.
But the result is a failed because it''s not for Xen Kernel.
This the log
> [ebuild U ] x11-drivers/nvidia-drivers-270.41.06 [260.19.36]
> USE="(multilib)
> -acpi -custom-cflags -gtk" 0 kB
>
> >>> Source
> prepared.
> >>> Configuring source in
>
2015 Sep 29
2
Building clang in llvm-3.7 on Linux with RT support enabled
Hi All,
I need to build clang/llvm from source on an Ubuntu Linux system, in order to build the gnustep Objective-C environment. I was able to build clang using cmake without a problem (following the instructions at clang.llvm.org/get_started.html), but when I tried to build gnustep, I found that clang failed to compile an autoconf-generated program. The compile error in the configure log was:
2018 Sep 15
0
Network Meltdown after Samba 4.9.0 Upgrade
On Sat, 2018-09-15 at 12:52 +1000, Reuben Farrelly via samba wrote:
> Hi,
>
> Last night I attempted to upgrade from Samba 4.8.5 to 4.9.0, with
> disastrous results. Upon starting Samba 4.9.0 my entire network came
> to
> a screaming halt a few seconds later, and upon shutting Samba down
> it
> came back to life again.
> Just to be sure this wasn't a
2018 Nov 13
0
Domain join issues - 4.9.0
On Tue, 13 Nov 2018 20:55:08 +0000
Jonathan Hunter via samba <samba at lists.samba.org> wrote:
> Hi,
>
> After a recent hardware failure where I did not have a working backup,
> I am trying to re-create one of my DCs (DC1). This is a Samba 4.9.0
> environment throughout. I have DC1 (the one that is hopefully being
> re-joined), but also DC2, DC3 and DC4 which are still
2018 Sep 15
0
Network Meltdown after Samba 4.9.0 Upgrade
On Sat, 15 Sep 2018 12:52:52 +1000
Reuben Farrelly via samba <samba at lists.samba.org> wrote:
> Hi,
>
> Last night I attempted to upgrade from Samba 4.8.5 to 4.9.0, with
> disastrous results. Upon starting Samba 4.9.0 my entire network came
> to a screaming halt a few seconds later, and upon shutting Samba down
> it came back to life again.
>
> The config is
2015 Sep 29
2
Building clang in llvm-3.7 on Linux with RT support enabled
Building the BlocksRuntime isn’t supported via CMake at the moment. It should be pretty straightforward to make it work, but it currently isn’t supported.
-Chris
> On Sep 29, 2015, at 9:45 AM, Alex Wang via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> As far as I know the makefile in there isn't the makefile that gets executed during the cmake build -- cmake generates its
2018 Nov 13
2
Domain join issues - 4.9.0
Hi,
After a recent hardware failure where I did not have a working backup,
I am trying to re-create one of my DCs (DC1). This is a Samba 4.9.0
environment throughout. I have DC1 (the one that is hopefully being
re-joined), but also DC2, DC3 and DC4 which are still present, and
these have not experienced issues.
After running the following:
$ sudo samba-tool domain join mydomain.org DC -U myadmin
2018 Sep 15
6
Network Meltdown after Samba 4.9.0 Upgrade
Hi,
Last night I attempted to upgrade from Samba 4.8.5 to 4.9.0, with
disastrous results. Upon starting Samba 4.9.0 my entire network came to
a screaming halt a few seconds later, and upon shutting Samba down it
came back to life again.
Just to be sure this wasn't a coincidence, I then started Samba again.
Once again all connectivity stopped, but came back as soon as I was able
to shut