public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52122] [4.6/4.7/4.8 Regression] incorrect ln -s replacement for mingw like targets in configure files
Date: Wed, 13 Feb 2013 10:09:00 -0000	[thread overview]
Message-ID: <bug-52122-4-HPFelCDHSQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52122-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52122

--- Comment #31 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-02-13 10:09:02 UTC ---
(In reply to comment #30)
> --- Makefile.in (revision 195997)
> +++ Makefile.in (working copy)
> @@ -115,8 +115,8 @@
>     && touch stamp-libada
>     -rm -rf adainclude
>     -rm -rf adalib
> -       $(LN_S_RECUSIVE) $(ADA_RTS_DIR) adainclude
> -       $(LN_S_RECUSIVE) $(ADA_RTS_DIR) adalib
> +       $(LN_S_RECURSIVE) $(ADA_RTS_DIR) adainclude
> +       $(LN_S_RECURSIVE) $(ADA_RTS_DIR) adalib
> 
>  osconstool:
>     $(MAKE) -C $(GCC_DIR)/ada $(LIBADA_FLAGS_TO_PASS) ./bldtools/oscons/xoscons
> ...

Please install as obvious.


  parent reply	other threads:[~2013-02-13 10:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 13:24 [Bug target/52122] New: [4.6.x/4.7] " daniel.f.starke at freenet dot de
2012-04-05 10:57 ` [Bug target/52122] [4.6/4.7/4.8 Regression] " rguenth at gcc dot gnu.org
2012-04-05 16:14 ` daniel.f.starke at freenet dot de
2012-04-26 14:06 ` rguenth at gcc dot gnu.org
2012-04-26 18:07 ` daniel.f.starke at freenet dot de
2012-04-26 18:08 ` daniel.f.starke at freenet dot de
2012-05-29 14:12 ` rguenth at gcc dot gnu.org
2012-08-08 21:10 ` tim.vanholder at anubex dot com
2012-09-22 16:00 ` daniel.f.starke at freenet dot de
2012-09-23  5:56 ` andris.pavenis at iki dot fi
2012-09-24 16:56 ` daniel.f.starke at freenet dot de
2012-09-24 16:58 ` daniel.f.starke at freenet dot de
2013-01-16  9:09 ` jakub at gcc dot gnu.org
2013-01-16  9:52 ` ktietz at gcc dot gnu.org
2013-02-08 17:28 ` karlson2k at gmail dot com
2013-02-09 15:03 ` karlson2k at gmail dot com
2013-02-12 15:33 ` ktietz at gcc dot gnu.org
2013-02-12 15:37 ` ktietz at gcc dot gnu.org
2013-02-12 15:39 ` ktietz at gcc dot gnu.org
2013-02-12 15:44 ` ktietz at gcc dot gnu.org
2013-02-12 17:51 ` dominiq at lps dot ens.fr
2013-02-12 18:03 ` ktietz at gcc dot gnu.org
2013-02-12 18:05 ` ktietz at gcc dot gnu.org
2013-02-12 18:07 ` dominiq at lps dot ens.fr
2013-02-12 18:11 ` k2k at narod dot ru
2013-02-12 18:42 ` jakub at gcc dot gnu.org
2013-02-12 19:15 ` dominiq at lps dot ens.fr
2013-02-12 19:49 ` jakub at gcc dot gnu.org
2013-02-12 20:17 ` dominiq at lps dot ens.fr
2013-02-13  9:53 ` vries at gcc dot gnu.org
2013-02-13 10:04 ` ktietz at gcc dot gnu.org
2013-02-13 10:06 ` vries at gcc dot gnu.org
2013-02-13 10:09 ` jakub at gcc dot gnu.org [this message]
2013-02-13 10:20 ` ktietz at gcc dot gnu.org
2013-02-13 10:21 ` ktietz at gcc dot gnu.org
2013-02-13 10:22 ` ktietz at gcc dot gnu.org
2013-02-13 10:25 ` vries at gcc dot gnu.org
2013-02-14  4:26 ` andris.pavenis at iki dot fi
2013-04-12 15:18 ` [Bug target/52122] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-05-13 20:09 ` ktietz 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-52122-4-HPFelCDHSQ@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: 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).