X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE
X-Spam-Check-By:	sourceware.org
X-Eon-Dm:	dm0227
X-Eon-Sig:	AQMb1uJNWjITPG+ilAIAAAAB,584adbfb6a743a718a8abeea05d45f8b
Message-ID:	<4D5A321C.4020608@member.fsf.org>
Date:	Mon, 14 Feb 2011 23:58:20 -0800
From:	L Anderson <lowella AT member DOT fsf DOT org>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Coreutils' Build Fails After Linking rm.exe
X-Proofpoint-Spam-Details:	rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1102140239
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I'm trying to build coreutils and I've run into a problem that has me
puzzled. I'd greatly appreciate any ideas or pointers on what might be
causing the problem and steps I could take to figure it out.  The
problem is repeatable, stopping at the exact same place.

I'm running 'XpProSp3', 'cygcheck -c' shows all OK.

1st--I used setup to install 'coreutils-8.10-1' source and placed the
files in '/usr/src/coreutils-8.10-1'

2nd--From that directory, I did 'cygport coreutils-8.10-1 prep', which
completed successfully.

3rd--I ran 'cygport coreutils-8.10-1 compile', which appeared to work
ok until it exited with a "make error" as shown by the following last
few lines of the output:

   ...
   CCLD   pwd.exe
   CCLD   readlink.exe
   CCLD   rm.exe
   CCLD   rmdir.exe <<<---up to and including rmdir.exe have been linked
./rm: ./rm: cannot execute binary file
make[3]: *** [runcon.exe] Error 126 <<<--runcon.exe and on, not linked
make[3]: *** Waiting for unfinished jobs....
./rm: ./rm: cannot execute binary file
make[3]: *** [seq.exe] Error 126
make[3]: Leaving directory 
`/usr/src/coreutils-8.10-1/coreutils-8.10-1/build/src
'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/usr/src/coreutils-8.10-1/coreutils-8.10-1/build/src
'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/usr/src/coreutils-8.10-1/coreutils-8.10-1/build'
make: *** [all] Error 2
*** ERROR: make failed

The above is output from 'make', chewing on the following 'makefile' lines:

...
pwd$(EXEEXT): $(pwd_OBJECTS) $(pwd_DEPENDENCIES)
	@rm -f pwd$(EXEEXT)
	$(AM_V_CCLD)$(LINK) $(pwd_OBJECTS) $(pwd_LDADD) $(LIBS)
readlink$(EXEEXT): $(readlink_OBJECTS) $(readlink_DEPENDENCIES)
	@rm -f readlink$(EXEEXT)
	$(AM_V_CCLD)$(LINK) $(readlink_OBJECTS) $(readlink_LDADD) $(LIBS)
rm$(EXEEXT): $(rm_OBJECTS) $(rm_DEPENDENCIES)
	@rm -f rm$(EXEEXT)
	$(AM_V_CCLD)$(LINK) $(rm_OBJECTS) $(rm_LDADD) $(LIBS)
rmdir$(EXEEXT): $(rmdir_OBJECTS) $(rmdir_DEPENDENCIES)
	@rm -f rmdir$(EXEEXT)
	$(AM_V_CCLD)$(LINK) $(rmdir_OBJECTS) $(rmdir_LDADD) $(LIBS)
runcon$(EXEEXT): $(runcon_OBJECTS) $(runcon_DEPENDENCIES)
	@rm -f runcon$(EXEEXT) <<<-----error occurs at this point<<--
	$(AM_V_CCLD)$(LINK) $(runcon_OBJECTS) $(runcon_LDADD) $(LIBS)
seq$(EXEEXT): $(seq_OBJECTS) $(seq_DEPENDENCIES)
	@rm -f seq$(EXEEXT)
	$(AM_V_CCLD)$(LINK) $(seq_OBJECTS) $(seq_LDADD) $(LIBS)
...	

The problem is related to 'rm.exe' being created in '..../build/src'.
Up until that point, the 'rm.exe' in the recipe lines is executed out
of '/bin'. So what causes 'make' to hiccup, when another 'rm.exe' is
created in the build directory? Is this a problem related to timing,
path, permissions, configuration, or?

Any insight in to what might be causing this would be greatly appreciated.

Thanks,

Lowell Anderson


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -