Re: other/9534: make install failst with './../mkinstalldirs: No such file or directory'

Re: other/9534: make install failst with './../mkinstalldirs: No such file or directory'

[Christian Cornelssen]

The following reply was made to PR other/9534; it has been noted by GNATS.

From: Christian Cornelssen <ccorn@cs.tu-berlin.de>
To: jb@as220.org
Cc: gcc-gnats@gcc.gnu.org, <gcc-prs@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>
Subject: Re: other/9534: make install failst with './../mkinstalldirs: No
 such file or directory'
Date: Sat, 1 Feb 2003 19:39:02 +0100 (MET)

   This message is in MIME format.  The first part should be readable text,
   while the remaining parts are likely unreadable without MIME-aware tools.
   Send mail to mime@docserver.cac.washington.edu for more info.
 
 ---559023410-851401618-1044124742=:7404
 Content-Type: TEXT/PLAIN; charset=US-ASCII
 
 This happens only for non-VPATH builds.
 We have fixed that on mainline (and it should get to 3.3 too).
 Obviously, 3.2 needs it too.  Could you try the attached patch?
 (Don't forget to rerun autoconf-2.13 to regenerate libiberty/configure.)
 
 References: http://gcc.gnu.org/ml/gcc-bugs/2003-01/msg01701.html
 
 Regards,
 
 Christian Cornelssen
 
 ---559023410-851401618-1044124742=:7404
 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="libiberty_topdir-3.2.diff"
 Content-Transfer-Encoding: BASE64
 Content-ID: <Pine.SOL.4.44.0302011939020.7404@basta.cs.tu-berlin.de>
 Content-Description: 
 Content-Disposition: attachment; filename="libiberty_topdir-3.2.diff"
 
 SW5kZXg6IGxpYmliZXJ0eS9NYWtlZmlsZS5pbg0KPT09PT09PT09PT09PT09
 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
 PT09PT09PQ0KUkNTIGZpbGU6IC9jdnNyb290L2djYy9nY2MvbGliaWJlcnR5
 L01ha2VmaWxlLmluLHYNCnJldHJpZXZpbmcgcmV2aXNpb24gMS43My42LjQN
 CmRpZmYgLXUgLXIxLjczLjYuNCBNYWtlZmlsZS5pbg0KLS0tIGxpYmliZXJ0
 eS9NYWtlZmlsZS5pbgkyOCBKYW4gMjAwMyAyMTo1NDoxMSAtMDAwMAkxLjcz
 LjYuNA0KKysrIGxpYmliZXJ0eS9NYWtlZmlsZS5pbgkxIEZlYiAyMDAzIDE4
 OjMwOjAwIC0wMDAwDQpAQCAtMjYsNiArMjYsNyBAQA0KICMgTWFrZWZpbGUg
 Zm9yIGxpYmliZXJ0eSBkaXJlY3RvcnkNCiAjDQogDQorbGliaWJlcnR5X3Rv
 cGRpciA9IEBsaWJpYmVydHlfdG9wZGlyQA0KIHNyY2RpciA9IEBzcmNkaXJA
 DQogVlBBVEggPSBAc3JjZGlyQA0KIA0KQEAgLTQ4LDcgKzQ5LDcgQEANCiBJ
 TlNUQUxMID0gQElOU1RBTExADQogSU5TVEFMTF9QUk9HUkFNID0gQElOU1RB
 TExfUFJPR1JBTUANCiBJTlNUQUxMX0RBVEEgPSBASU5TVEFMTF9EQVRBQA0K
 LW1raW5zdGFsbGRpcnMgPSAkKFNIRUxMKSAkKHNyY2RpcikvLi4vbWtpbnN0
 YWxsZGlycw0KK21raW5zdGFsbGRpcnMgPSAkKFNIRUxMKSAkKGxpYmliZXJ0
 eV90b3BkaXIpL21raW5zdGFsbGRpcnMNCiANCiBBUiA9IEBBUkANCiBBUl9G
 TEFHUyA9IHJjDQpJbmRleDogbGliaWJlcnR5L2NvbmZpZ3VyZS5pbg0KPT09
 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
 PT09PT09PT09PT09PT09PT09PQ0KUkNTIGZpbGU6IC9jdnNyb290L2djYy9n
 Y2MvbGliaWJlcnR5L2NvbmZpZ3VyZS5pbix2DQpyZXRyaWV2aW5nIHJldmlz
 aW9uIDEuNDYuMi4yDQpkaWZmIC11IC1yMS40Ni4yLjIgY29uZmlndXJlLmlu
 DQotLS0gbGliaWJlcnR5L2NvbmZpZ3VyZS5pbgkzMSBNYXkgMjAwMiAxOToz
 NjoxNSAtMDAwMAkxLjQ2LjIuMg0KKysrIGxpYmliZXJ0eS9jb25maWd1cmUu
 aW4JMSBGZWIgMjAwMyAxODozMDowMCAtMDAwMA0KQEAgLTMwLDYgKzMwLDcg
 QEANCiBlbHNlDQogICBsaWJpYmVydHlfdG9wZGlyPSIke3NyY2Rpcn0vLi4i
 DQogZmkNCitBQ19TVUJTVChsaWJpYmVydHlfdG9wZGlyKQ0KIEFDX0NPTkZJ
 R19BVVhfRElSKCRsaWJpYmVydHlfdG9wZGlyKQ0KIA0KIGRubCBWZXJ5IGxp
 bWl0ZWQgdmVyc2lvbiBvZiBhdXRvbWFrZSdzIGVuYWJsZS1tYWludGFpbmVy
 LW1vZGUNCg==
 ---559023410-851401618-1044124742=:7404--

Re: other/9534: make install failst with './../mkinstalldirs: No such file or directory'

[Jim Bray]

The following reply was made to PR other/9534; it has been noted by GNATS.

From: Jim Bray <jb@as220.org>
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: other/9534: make install failst with './../mkinstalldirs: No
	such file or directory'
Date: 01 Feb 2003 12:44:51 -0500

   That got sent prematurely when I hit return in one of the fields.
 Please s/failst/fails for me. Also, looking at some of the
 related reports, it should maybe be categorised as 'bootstrap'.
 
 Thanks.
 
 On Sat, 2003-02-01 at 12:26, gcc-gnats@gcc.gnu.org wrote:
 > Thank you very much for your problem report.
 > It has the internal identification `other/9534'.
 > The individual assigned to look at your
 > report is: unassigned. 
 > 
 > >Category:       other
 > >Responsible:    unassigned
 > >Synopsis:       make install failst with './../mkinstalldirs: No such file or directory'
 > >Arrival-Date:   Sat Feb 01 17:26:00 UTC 2003
 -- 
 Jim Bray <jb@as220.org>
 

other/9534: make install failst with './../mkinstalldirs: No such file or directory'

[jb]

>Number:         9534
>Category:       other
>Synopsis:       make install failst with './../mkinstalldirs: No such file or directory'
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 01 17:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     jb@as220.org
>Release:        3.2.2-prerelease (cvs, 2/1/2003)
>Organization:
>Environment:

>Description:
  done; \
fi
make[2]: Leaving directory `/src/gcc/i586-pc-linux-gnu/libiberty'
/bin/sh ./../mkinstalldirs /usr/lib
./../mkinstalldirs: ./../mkinstalldirs: No such file or directory
make[1]: *** [install_to_libdir] Error 127
make[1]: Leaving directory `/src/gcc/i586-pc-linux-gnu/libiberty'
make: *** [install-target-libiberty] Error 2
make: Leaving directory `/src/gcc'

  This is a make or makefile problem. mkinstall does
of course exist in the toplevel dir/

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: