|

bootstrap oddity

View: New views

3 Messages — Rating Filter: Alert me

	bootstrap oddity by Reuben Thomas :: Rate this Message: \| View Threaded \| Show Only this Message I just got the following output from $ ./bootstrap ./bootstrap: Bootstrapping from checked-out hello sources... ./bootstrap: consider installing git-merge-changelog from gnulib ./bootstrap: getting gnulib files... Submodule 'gnulib' () registered for path 'gnulib' ./bootstrap: getting translations into po/.reference for hello... receiving incremental file list sent 34 bytes received 652 bytes 1372.00 bytes/sec total size is 295770 speedup is 431.15 ./bootstrap: updated po//home/rrt/repo/hello/po/.reference.po... cp: cannot stat `po/.reference//home/rrt/repo/hello/po/.reference.po': No such file or directory (and then it continued, fine). But it seems to have constructed a bogus filename on the way. -- http://rrt.sc3d.org
	Re: bootstrap oddity by Jim Meyering :: Rate this Message: \| View Threaded \| Show Only this Message Reuben Thomas wrote: > I just got the following output from > > $ ./bootstrap > ./bootstrap: Bootstrapping from checked-out hello sources... > ./bootstrap: consider installing git-merge-changelog from gnulib > ./bootstrap: getting gnulib files... > Submodule 'gnulib' () registered for path 'gnulib' > ./bootstrap: getting translations into po/.reference for hello... > receiving incremental file list > > sent 34 bytes received 652 bytes 1372.00 bytes/sec > total size is 295770 speedup is 431.15 > ./bootstrap: updated po//home/rrt/repo/hello/po/.reference.po... > cp: cannot stat `po/.reference//home/rrt/repo/hello/po/.reference.po': No such > file or directory > > (and then it continued, fine). But it seems to have constructed a bogus filename > on the way. Hi Reuben, I suggest you run "bash -x ./bootstrap >& log". Then, if you look in the log, you can determine how that bogus-looking name was formed. Once you know that, I'll bet you can even suggest a patch.
	Re: bootstrap oddity by Reuben Thomas :: Rate this Message: \| View Threaded \| Show Only this Message On 19 April 2012 10:45, Jim Meyering <jim@...> wrote: > > I suggest you run "bash -x ./bootstrap >& log". > Then, if you look in the log, you can determine how that bogus-looking > name was formed. Once you know that, I'll bet you can even suggest a patch. Thanks, I think that worked. Patch sent separately. -- http://rrt.sc3d.org