public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/51646] Make libgfortran compile on Android Date: Wed, 18 Apr 2012 08:33:00 -0000 [thread overview] Message-ID: <bug-51646-4-1119c5szFM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51646-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51646 --- Comment #5 from Janne Blomqvist <jb at gcc dot gnu.org> 2012-04-18 08:31:47 UTC --- Another build problem at http://stackoverflow.com/questions/10202966/android-ndk-fortran-build-of-lapack-problems-with-unresolved-sincos
next prev parent reply other threads:[~2012-04-18 8:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-21 8:33 [Bug libfortran/51646] New: Make libgfortran compile on Android - without S_IREAD burnus at gcc dot gnu.org 2011-12-21 10:21 ` [Bug libfortran/51646] " jb at gcc dot gnu.org 2011-12-21 10:26 ` jb at gcc dot gnu.org 2011-12-22 20:50 ` jb at gcc dot gnu.org 2011-12-22 21:18 ` [Bug libfortran/51646] Make libgfortran compile on Android jb at gcc dot gnu.org 2012-04-18 8:33 ` jb at gcc dot gnu.org [this message] 2012-04-18 12:39 ` burnus at gcc dot gnu.org 2012-04-18 13:10 ` burnus 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-51646-4-1119c5szFM@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).