public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jay dot krell at cornell dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/37079] cannot find -lgcc_s Date: Thu, 14 Aug 2008 12:06:00 -0000 [thread overview] Message-ID: <20080814120543.3772.qmail@sourceware.org> (raw) In-Reply-To: <bug-37079-16543@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from jay dot krell at cornell dot edu 2008-08-14 12:05 ------- wrong workaround before, actual: def WorkaroundUnableToFindSparc64LibGcc(): # # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37079 # ld: cannot find -lgcc_s # collect2: ld returned 1 exit status # make[4]: *** [libstdc++.la] Error 1 # make[4]: Leaving directory /obj/gcc.1/sparc64-sun-solaris2.10/sparc64-sun-solaris2.10/sparc64-sun-solaris2.10/libstdc++-v3/src # # -disable-shared is probably also a good workaround here # PatchName = "inability to find sparc64 libgcc.so" print("patching install " + PatchName) Directory = Prefix + "/lib/gcc/sparc64-sun-solaris2.10/" + GccVersion Run(".", "mkdir -p " + Directory) Run(Directory, "-ln -s sparcv9/libgcc_s.so libgcc_s.so") Run(Directory, "-ln -s sparcv9/libgcc_s.so.1 libgcc_s.so.1") print("done patching " + PatchName) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37079
next prev parent reply other threads:[~2008-08-14 12:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-11 9:29 [Bug c/37079] New: " jayk123 at hotmail dot com 2008-08-14 11:57 ` [Bug c/37079] " jay dot krell at cornell dot edu 2008-08-14 12:06 ` jay dot krell at cornell dot edu [this message] 2008-08-16 22:38 ` [Bug bootstrap/37079] " pinskia at gcc dot gnu dot org 2008-08-17 8:52 ` jay dot krell at cornell dot edu 2008-08-17 8:53 ` jay dot krell at cornell dot edu 2009-12-09 2:00 ` 3dw4rd at verizon dot net 2009-12-09 4:22 ` howarth at nitro dot med dot uc dot edu 2009-12-09 13:22 ` 3dw4rd at verizon dot net
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=20080814120543.3772.qmail@sourceware.org \ --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).