bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

More: binutils-2.17 build tries to modify distribution directory


From: anirkko
Subject: More: binutils-2.17 build tries to modify distribution directory
Date: Thu, 19 Apr 2007 15:21:42 +0200 (MET DST)

Hi again
Regarding modifying the dist.directory, my  "Not so bad, the build proceeds 
alright"
below was optimistic. When the dist. directory is totally read-only (such as on
a read-only disk, or wich "chmod -R go-w binutils-2.17"), the build fails at the
step shown below. What is the point of building in a different directory, if the
original directory still needs to be modified?
Arto


> From anirkko Thu Apr 19 10:25:16 2007
> To: address@hidden
> Subject: binutils-2.17 build tries to modify distribution directory
> 
> 
> Hi
> When building binutils-2.17 in a different obj directory (as recommended),
> with the original distribution directory write protected/owned by a different
> user, one notices that the build process tries to modify the distribution
> directory (with messages such as "Permission denied" and "touch: cannot change
> times on /build/binutils-2.17/bfd/doc/bfd.info") instead of writing everything
> into the obj directory), and also emits a misleading WARNING message.
> 
> Not so bad, the build proceeds alright.
> 
> Best regards,
> Arto Nirkko
> 
> -----------------------------------------------------------------------------
> ...
> ...
> gmake[2]: Entering directory 
> `/build/binutils-2.17_obj0-static_g412-b214-O3-mcpu=supersparc/bfd'
> Making info in doc
> gmake[3]: Entering directory 
> `/build/binutils-2.17_obj0-static_g412-b214-O3-mcpu=supersparc/bfd/doc'
> restore=: && backupdir=".am$$" && \
> am__cwd=`pwd` && cd /build/binutils-2.17/bfd/doc && \
> rm -rf $backupdir && mkdir $backupdir && \
> for f in /build/binutils-2.17/bfd/doc/bfd.info 
> /build/binutils-2.17/bfd/doc/bfd.info-[0-9] 
> /build/binutils-2.17/bfd/doc/bfd.info-[0-9][0-9] 
> /build/binutils-2.17/bfd/doc/bfd.i[0-9] 
> /build/binutils-2.17/bfd/doc/bfd.i[0-9][0-9]; do \
>   if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
> cd "$am__cwd"; \
> if /build/binutils-2.17/missing makeinfo --split-size=5000000 
> --split-size=5000000   -I /build/binutils-2.17/bfd/doc \
>  -o /build/binutils-2.17/bfd/doc/bfd.info 
> /build/binutils-2.17/bfd/doc/bfd.texinfo; \
> then \
>   rc=0; \
>   cd /build/binutils-2.17/bfd/doc; \
> else \
>   rc=$?; \
>   cd /build/binutils-2.17/bfd/doc && \
>   $restore $backupdir/* `echo ".//build/binutils-2.17/bfd/doc/bfd.info" | sed 
> 's|[^/]*$||'`; \
> fi; \
> rm -rf $backupdir; exit $rc
> mkdir: Failed to make directory ".am12945"; Permission denied
> WARNING: `makeinfo' is missing on your system.  You should only need it if
>          you modified a `.texi' or `.texinfo' file, or any other file
>          indirectly affecting the aspect of the manual.  The spurious
>          call might also be the consequence of using a buggy `make' (AIX,
>          DU, IRIX).  You might want to install the `Texinfo' package or
>          the `GNU make' package.  Grab either from any GNU archive site.
> touch: cannot change times on /build/binutils-2.17/bfd/doc/bfd.info
> gmake[3]: Leaving directory 
> `/build/binutils-2.17_obj0-static_g412-b214-O3-mcpu=supersparc/bfd/doc'
> Making info in po
> gmake[3]: Entering directory 
> `/build/binutils-2.17_obj0-static_g412-b214-O3-mcpu=supersparc/bfd/po'
> gmake[3]: Nothing to be done for `info'.
> gmake[3]: Leaving directory 
> `/build/binutils-2.17_obj0-static_g412-b214-O3-mcpu=supersparc/bfd/po'
> ...
> ...
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]