On Mon, 10 Mar 2025 at 16:30, Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx> wrote: > > On Mon, 2025-03-10 at 17:19 +0100, Basile Starynkevitch wrote: > > On Mon, 2025-03-10 at 17:04 +0100, Alberto Gcchelp via Gcc-help wrote: > > > Hi > > > > > > I plan to build (and use) GCC 15 right after relesase. Building GCC takes > > > several hours on my computer, so I would prefer to get it right at the > > > first try. > > > > > > Yes this is expected. What matters are your options to your configure script. > > And you should build GCC outside of its source tree. > > Expect to fail the build at first, unless you are familiar with building GCC > > and > > contributing to it. > > > > In other words you may need to try twice. > > The solution I use on my Linux computer is to compile GNU emacs (fetched with > git clone) from its source code daily. > > It takes a few minutes, the time to drink your morning coffee. > > Here is the script (in $HOME/bin/getemacstrunk) I use to fetch and compile it: > > #! /bin/bash -x > export PATH=/usr/bin:/bin > sync > cd /usr/src/Editor/emacs > rm -f etc/DOC* > git pull > git log -3 | cat > sync > oldemacspids=$(pgrep -u $(id -u) emacs-trunk) > if [ -n "$oldemacspids" ] ; then > kill -TERM $oldemacspids > printf "%s: killed %s\n" $0 $oldemacspids > fi > rm -rf /tmp/emacsinst/ > time nice make -j 6 -l 9 || exit 1 > sudo /bin/mv -v /usr/local/bin/emacs-trunk /usr/local/bin/emacs-trunk~ > time make install DESTDIR=/tmp/emacsinst || exit 1 > sudo /bin/cp -v -r -p /tmp/emacsinst/usr/local/. /usr/local/. > sync& What on earth has this got to do with the thread topic of the 'std' module?
