Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 13993
Product:  
Component:  
Status: RESOLVED
Resolution: FIXED
Assigned To: Not yet assigned to anyone <unassigned@gcc.gnu.org>
Host:
Reported against  
Priority:  
Severity:  
Target Milestone:  
 
 
Target:
Reporter: Paul N. Hilfinger <Hilfinger@gnat.com>
Add CC:
CC:
Remove selected CCs
Build:
URL:
Summary:
Keywords:
Known to work:
Known to fail:

Attachment Description Type Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 13993 depends on: Show dependency tree
Show dependency graph
Bug 13993 blocks:

Additional Comments:






View Bug Activity   |   Format For Printing   |   Clone This Bug

Description:   Last confirmed: 2004-06-02 20:18 Opened: 2004-02-03 08:43 
Configuring the head version of GCC with 

  CC=gcc ../../src/gcc-head/configure --enable-languages="c" \
--prefix=$HOME/obj/gcc-head/install

causes a problem after

make bootstrap
make install

Specifically, within the gcc subdirectory, 'make install' looks for install-sh
in ../../src/gcc-head, the top-level source directory, which is wrong (should be
../../../src/gcc-head.  This is a change from earlier versions (3.3.2, for
example).  It is causes by the definition of INSTALL in the top-level
Makefile.in, which gets passed down to and overrides the (correct) definition
of INSTALL in the gcc subdirectory.  

If the use of relative paths when invoking configure is to be deprecated, there
should be a warning.  Better still, revert to the previous definition of INSTALL
or otherwise convert to an absolute pathname for INSTALL, as previous versions
did.

------- Comment #1 From Andrew Pinski 2004-04-21 20:53 ------- 
Hmm this worked in 3.4.0 because I just did a build.

------- Comment #2 From Andrew Pinski 2004-04-25 20:27 ------- 
Can you try again?

------- Comment #3 From Andrew Pinski 2004-05-26 13:53 ------- 
This worked for me, can you try again?

------- Comment #4 From Andrew Pinski 2004-06-02 20:18 ------- 
*** Bug 15668 has been marked as a duplicate of this bug. ***

------- Comment #5 From Mark Mitchell 2004-06-09 19:32 ------- 
Andrew reports success.  Until more details are provided, I'm closing this PR.

------- Comment #6 From Andrew Pinski 2004-07-04 19:38 ------- 
I know this is a bug now, the reason why it works for me is because I
compatiable "install" installed.

------- Comment #7 From Andrew Pinski 2004-07-04 19:38 ------- 
*** Bug 16363 has been marked as a duplicate of this bug. ***

------- Comment #8 From Andrew Pinski 2004-07-30 15:20 ------- 
*** Bug 16835 has been marked as a duplicate of this bug. ***

------- Comment #9 From Mark Mitchell 2004-08-29 19:09 ------- 
Postponed until GCC 3.4.3.

------- Comment #10 From Andrew Pinski 2004-10-01 12:31 ------- 
*** Bug 17769 has been marked as a duplicate of this bug. ***

------- Comment #11 From Andrew Pinski 2004-10-01 12:31 ------- 
*** Bug 17768 has been marked as a duplicate of this bug. ***

------- Comment #12 From Andrew Pinski 2004-10-23 19:22 ------- 
Patch posted here: <http://gcc.gnu.org/ml/gcc-patches/2004-10/msg01987.html>.

This is also known as <http://sources.redhat.com/bugzilla/show_bug.cgi?id=179>.

------- Comment #13 From Andrew Pinski 2004-10-23 20:31 ------- 
Daniel since your patch fixes this bug, could you look into backporting it to
the 3.4 branch?

------- Comment #14 From Mark Mitchell 2004-11-01 00:46 ------- 
Postponed until GCC 3.4.4.

------- Comment #15 From Andrew Pinski 2005-01-07 03:13 ------- 
*** Bug 19306 has been marked as a duplicate of this bug. ***

------- Comment #16 From Andrew Pinski 2005-02-02 14:30 ------- 
*** Bug 19751 has been marked as a duplicate of this bug. ***

------- Comment #17 From Daniel Jacobowitz 2005-03-08 17:31 ------- 
Fixed on 3.4 and 4.0 branches.

------- Comment #18 From Andrew Pinski 2005-03-23 20:35 ------- 
*** Bug 20609 has been marked as a duplicate of this bug. ***

------- Comment #19 From Andrew Pinski 2005-10-20 21:42 ------- 
*** Bug 24463 has been marked as a duplicate of this bug. ***
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug