public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ibenrunnin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/55349] arm-linux-androideabi-gcc-4.6: Internal compiler error compiling libpng in debug mode Date: Fri, 16 Nov 2012 03:44:00 -0000 [thread overview] Message-ID: <bug-55349-4-e1GpVWMALf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55349-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55349 --- Comment #1 from Ben Clapp <ibenrunnin at gmail dot com> 2012-11-16 03:44:38 UTC --- ADDITIONAL INFORMATION: I've hunted around Google for a good while, this is what I could find on the subject (virtually no information of worth): http://grokbase.com/t/gg/android-ndk/128b4k8wmm/ndk-r8b-debug-bild-does-not-link-anymore http://stackoverflow.com/questions/11980870/error-on-building-android-ndk-assets/12234953#comment16414063_12234953 https://groups.google.com/forum/#!msg/android-ndk/n4RIOhx9f4Y/oOWF4nUxMPAJ http://stackoverflow.com/questions/13042825/libpng-ndk-build-internal-compiler-error-in-debug-mode http://sourceforge.net/mailarchive/message.php?msg_id=30009240 http://timecubepuzzle.blogspot.com/2012/05/development-on-android-ndk-gluing-c.html?showComment=1347158980877#c6889341856998289570 possible similar issue involving Visual Studio??? http://stackoverflow.com/questions/12933309/linker-error-unresolved-external-symbol-imp-iob-func-in-libpng-lib
next prev parent reply other threads:[~2012-11-16 3:44 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-16 3:44 [Bug c/55349] New: " ibenrunnin at gmail dot com 2012-11-16 3:44 ` ibenrunnin at gmail dot com [this message] 2012-11-16 3:47 ` [Bug c/55349] " pinskia at gcc dot gnu.org 2012-11-16 3:51 ` [Bug target/55349] " pinskia at gcc dot gnu.org 2012-11-16 3:56 ` [Bug c/55349] " ibenrunnin at gmail dot com 2012-11-28 3:08 ` ramana at gcc dot gnu.org 2013-08-05 20:40 ` rearnsha at gcc dot gnu.org
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=bug-55349-4-e1GpVWMALf@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).