public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dirk-jan@selwerd.nl
To: gcc-gnats@gcc.gnu.org
Cc: dirk-jan@selwerd.nl
Subject: other/3258: gcc does not correctly install into a target directory
Date: Tue, 19 Jun 2001 06:46:00 -0000	[thread overview]
Message-ID: <20010619134541.12885.qmail@sourceware.cygnus.com> (raw)

>Number:         3258
>Category:       other
>Synopsis:       gcc does not correctly install into a target directory
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          mistaken
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 19 06:46:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Dirk-Jan Faber
>Release:        gcc-3.0
>Organization:
>Environment:
An own compiled Linux distribution (snow-2.5).
>Description:
Installation of gcc into a target directory fails on gcc-3.0/libjava/libltdl/Makefile
On installation I get the error message:
make[2]: Entering directory `/work/gcc-3.0.compiled/i686-linux/libjava/libltdl'
make[3]: Entering directory `/work/gcc-3.0.compiled/i686-linux/libjava/libltdl'
/bin/sh ./../../mkinstalldirs /target/usr/lib
./../../mkinstalldirs: ./../../mkinstalldirs: No such file or directory
make[3]: *** [install-libLTLIBRARIES] Error 127

It seems that the Makefile is looking for 'mkinstalldirs" one level to deep into the directory.
>How-To-Repeat:
Compile gcc-3.0 by:
         ./configure --prefix=/usr \
                     --with-local-prefix=/usr \
                     --enable-threads=posix \
                     --enable-shared i686-linux
         make
Installation fails with: 
              DSTDIR=/target
              make prefix=$DSTDIR/usr \
              local_prefix=$DSTDIR/usr install

>Fix:
It is in the attached diff file.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="gcc-3.0.diff"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc-3.0.diff"

ZGlmZiAtcmNOIGdjYy0zLjAub3JpZy9saWJqYXZhL2xpYmx0ZGwvTWFrZWZpbGUuaW4gZ2NjLTMu
MC9saWJqYXZhL2xpYmx0ZGwvTWFrZWZpbGUuaW4KKioqIGdjYy0zLjAub3JpZy9saWJqYXZhL2xp
Ymx0ZGwvTWFrZWZpbGUuaW4JU3VuIFNlcCAxMCAxMDowNDo0MCAyMDAwCi0tLSBnY2MtMy4wL2xp
YmphdmEvbGlibHRkbC9NYWtlZmlsZS5pbglUdWUgSnVuIDE5IDE1OjExOjE2IDIwMDEKKioqKioq
KioqKioqKioqCioqKiA5OCwxMDQgKioqKgogIGxpYmx0ZGxjX2xhX1NPVVJDRVMgPSBsdGRsLmMK
ICBsaWJsdGRsY19sYV9MSUJBREQgPSAkKExJQkFERF9ETCkKICBBQ0xPQ0FMX000ID0gJCh0b3Bf
c3JjZGlyKS9hY2xvY2FsLm00CiEgbWtpbnN0YWxsZGlycyA9ICQoU0hFTEwpICQodG9wX3NyY2Rp
cikvLi4vLi4vbWtpbnN0YWxsZGlycwogIENPTkZJR19IRUFERVIgPSBjb25maWcuaAogIENPTkZJ
R19DTEVBTl9GSUxFUyA9IAogIExUTElCUkFSSUVTID0gICQobGliX0xUTElCUkFSSUVTKSAkKG5v
aW5zdF9MVExJQlJBUklFUykKLS0tIDk4LDEwNCAtLS0tCiAgbGlibHRkbGNfbGFfU09VUkNFUyA9
IGx0ZGwuYwogIGxpYmx0ZGxjX2xhX0xJQkFERCA9ICQoTElCQUREX0RMKQogIEFDTE9DQUxfTTQg
PSAkKHRvcF9zcmNkaXIpL2FjbG9jYWwubTQKISBta2luc3RhbGxkaXJzID0gJChTSEVMTCkgJCh0
b3Bfc3JjZGlyKS8uLi8uLi8uLi9ta2luc3RhbGxkaXJzCiAgQ09ORklHX0hFQURFUiA9IGNvbmZp
Zy5oCiAgQ09ORklHX0NMRUFOX0ZJTEVTID0gCiAgTFRMSUJSQVJJRVMgPSAgJChsaWJfTFRMSUJS
QVJJRVMpICQobm9pbnN0X0xUTElCUkFSSUVTKQo=


             reply	other threads:[~2001-06-19  6:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-19  6:46 dirk-jan [this message]
2001-06-23  3:06 Dirk-Jan Faber

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=20010619134541.12885.qmail@sourceware.cygnus.com \
    --to=dirk-jan@selwerd.nl \
    --cc=gcc-gnats@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).