You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Try building cloud9 on Ubuntu 12.10 with gcc version 4.7.2
2. When the command gclient sync is issued, errors are encountered while
compiling the file dwarf_reader.cc in binutils/gold directory.
3. When source code is modified to take care of the errors, gclient removes the
files and starts building afresh, thus doing away with the possibility of
manually removing the error.
What is the expected output? What do you see instead?
My expectation is that instead of creating the files again, gclient would use
the already existing files.
What version / revision number of the product are you using? On what
operating system?
Mentioned above.
Please provide any additional information below.
Original issue reported on code.google.com by nilayva...@gmail.com on 6 Feb 2013 at 2:17
The text was updated successfully, but these errors were encountered:
Copy-pasting Paul Rubel's message on the cloud9-dev mailing list:
I believe I've seen this issue as well, though it's hard to tell
without any output. The newer version of gcc, 2.7.2,
doesn't like the code in the older version of binutils that cloud9
wants to use. Binutils was changed to be more standards
compliant and be able to compile with newer version of gcc.
I've had luck upgrading my binutils from 2.22 to 2.23.1 in
build/download_binutils.sh:
diff --git a/build/download_binutils.sh b/build/download_binutils.sh
index e3a8958..9929b39 100755
--- a/build/download_binutils.sh
+++ b/build/download_binutils.sh
@@ -3,7 +3,8 @@
# This script will download binutils into third_party/binutils and build it.
# Do NOT CHANGE this, unless you know what you're doing
-BINUTILS_SNAPSHOT="binutils-2.22.tar.bz2"
+BINUTILS_SNAPSHOT="binutils-2.23.1.tar.bz2"
As far as I can tell, which is admittedly a limited endorsement, this
change hasn't lead to any runtime problems.
Original comment by stefan.b...@gmail.com on 7 Feb 2013 at 9:00
Original issue reported on code.google.com by
nilayva...@gmail.com
on 6 Feb 2013 at 2:17The text was updated successfully, but these errors were encountered: