Bruno Haible <bruno@xxxxxxxxx> wrote: > Perry Hutchison wrote in > <https://lists.gnu.org/archive/html/autoconf/2019-03/msg00013.html>: > > this system's native sed has been crippled > > to always operate in "sandbox" mode, even without "--sandbox" having > > been specified on the command line. > ... > > Can you tell us, please, which system this is? I'd like to estimate > the urgency/necessity of providing a workaround. It is a Lenovo N21 Chromebook*, running Chrome OS 71.0.3578.127, in developer mode**. "sed --version" reports: sed (GNU sed) 4.4 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. ... * Yes, I am aware of Chromebrew; I am using it as a starting point but trying to bootstrap as much as possible from source rather than installing from binary packages (long story). ** Chrome OS provides no shell access at all, nor ability to run any binaries other than its own, unless in developer mode; presumably none of its own scripts need a fully functional sed. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
