public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ralf dot corsepius at rtems dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/26473]  New: cross-building installs ssp headers to $(includedir)
Date: Sun, 26 Feb 2006 12:55:00 -0000	[thread overview]
Message-ID: <bug-26473-9952@http.gcc.gnu.org/bugzilla/> (raw)

Cross building gcc-4.1.0rc2 installs

$prefix/include/ssp/unistd.h
$prefix/include/ssp/string.h
$prefix/include/ssp/ssp.h
$prefix/include/ssp/stdio.h

i.e. they are being installed into the build-host's include directory.

This hardly can be correct.


-- 
           Summary: cross-building installs ssp headers to $(includedir)
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ralf dot corsepius at rtems dot org
GCC target triplet: != host


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


             reply	other threads:[~2006-02-26 12:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-26 12:55 ralf dot corsepius at rtems dot org [this message]
2006-02-26 14:48 ` [Bug other/26473] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-02-26 15:01 ` pinskia at gcc dot gnu dot org
2006-02-27 14:12 ` ralf dot corsepius at rtems dot org
2006-02-27 14:14 ` ralf dot corsepius at rtems dot org
2006-02-27 17:48 ` ralf dot corsepius at rtems dot org
2006-02-27 18:11 ` ralf dot corsepius at rtems dot org
2006-02-27 22:36 ` mmitchel at gcc dot gnu dot org
2006-02-28  0:41 ` mmitchel at gcc dot gnu dot org
2006-02-28  0:45 ` mmitchel at gcc dot gnu dot org
2006-02-28  1:18 ` mmitchel at gcc dot gnu dot org
2006-06-21 16:36 ` fche at gcc dot gnu dot 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-26473-9952@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).