From: Roger Pack <rogerdpack2@gmail.com>
To: cygwin@cygwin.com
Cc: llvm-dev@lists.llvm.org
Subject: Re: [ANNOUNCEMENT] llvm 3.8.1-1
Date: Tue, 13 Dec 2016 22:56:00 -0000 [thread overview]
Message-ID: <CAL1QdWeBMsMpSg6sHAP3UvebUAcA385Y1Arxgv3tJceW0LHbLA@mail.gmail.com> (raw)
In-Reply-To: <e04f072b-6ca9-f3d3-fff2-8c924d759f50@cygwin.com>
On 12/7/16, Yaakov Selkowitz <yselkowitz@cygwin.com> wrote:
> On 2016-12-07 17:57, Roger Pack wrote:
>> Awesome. I tried building 3.9.0 today and ran into
>>
>> llvm-3.9.0.src/lib/Support/Unix/Signals.inc:418:5: error: ‘Dl_info’
>> was not declared in this scope
>> Dl_info dlinfo;
>
> Already fixed upstream:
>
> http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Support/Unix/Signals.inc?r1=282919&r2=283427
>
> I plan to look at rebasing sometime after 3.9.1 is out.
OK that fixed my initial problem with 3.9.0
the next failure after that (with both 3.9.0 and 3.9.1) is
Scanning dependencies of target LLVMPasses
[ 64%] Building CXX object
lib/Passes/CMakeFiles/LLVMPasses.dir/PassBuilder.cpp.o
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/as:
CMakeFiles/LLVMPasses.dir/PassBuilder.cpp.o: too many sections (34877)
/tmp/ccTGhQkv.s: Assembler messages:
/tmp/ccTGhQkv.s: Fatal error: can't write
CMakeFiles/LLVMPasses.dir/PassBuilder.cpp.o: File too big
so I guess I'll look forward to your release, I guess 3.9.1 was just cut.
Thanks!
-roger-
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-12-13 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 20:25 Yaakov Selkowitz
2016-12-07 23:58 ` Roger Pack
2016-12-08 6:49 ` Yaakov Selkowitz
2016-12-13 22:56 ` Roger Pack [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL1QdWeBMsMpSg6sHAP3UvebUAcA385Y1Arxgv3tJceW0LHbLA@mail.gmail.com \
--to=rogerdpack2@gmail.com \
--cc=cygwin@cygwin.com \
--cc=llvm-dev@lists.llvm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).