Re: backtrace.h not installed with --enable-plugin
On 2017-06-14 11:05, Richard Biener wrote: On Wed, Jun 14, 2017 at 9:08 AM, wrote: Hello All, I compiled a gcc-7.1 release tree configured with '../gcc-7.1.0/configure' '--program-suffix=-7my' '--enable-shared' '--enable-linker-build-id' '--without-included-gettext' '--enable-threads=posix' '--with-sysroot=/' '--enable-clocale=gnu' '--enable-libstdcxx-debug' '--enable-libstdcxx-time=yes' '--with-default-libstdcxx-abi=new' '--enable-gnu-unique-object' '--enable-libmpx' '--enable-plugin' '--enable-default-pie' '--with-system-zlib' '--enable-multiarch' '--with-arch-32=i686' '--with-abi=m64' '--with-multilib-list=m32,m64,mx32' '--enable-multilib' '--with-tune=native' '--enable-checking=release' '--enable-languages=c,c++,go,lto' I forgot to tell that my platform is a Linux/Debian/Sid/x86-64 I was expecting the installed built tree to contain the backtrace.h from Ian Taylor's libbacktrace. This is not the case. Why? What configure option did I miss? libbacktrace is a convenience library only and is not installed so why do you expect backtrace.h to be installed? Because GCC plugins should be able to use it. Also, that library is linked into cc1plus (whose symbols contain backtrace_open, backtrace_free, backtrace_create_state and so forth) So it does not cost much to publish backtrace.h when plugins are enabled (the static libbacktrace library is part of the cc1plus) BTW, on Debian/x86-64 /usr/lib/gcc/x86_64-linux-gnu/6/include/backtrace.h is part of libgcc-6-dev which also provides files /usr/lib/gcc/x86_64-linux-gnu/6/libasan.so etc, which are definitely provided by GCC. Cheers. -- Basile Starynkevitch (France) http://starynkevitch.net/Basile/
Stale wiki info about CompileFarm registration
Hi all, It seems that info at https://gcc.gnu.org/wiki/CompileFarm#How_to_Get_Involved.3F is out-dated: Laurent's mail is not responsive and one's supposed to use application form at https://cfarm.tetaneutral.net/users/new/ (which provides all the necessary guidance). Could someone update the wiki? (I could do it myself but don't have write access) -Yury
Re: Stale wiki info about CompileFarm registration
On 15 June 2017 at 12:19, Yuri Gribov wrote: > Hi all, > > It seems that info at > https://gcc.gnu.org/wiki/CompileFarm#How_to_Get_Involved.3F is > out-dated: Laurent's mail is not responsive and one's supposed to use > application form at https://cfarm.tetaneutral.net/users/new/ (which > provides all the necessary guidance). > > Could someone update the wiki? (I could do it myself but don't have > write access) Done, thanks for pointing it out.
gcc-7-20170615 is now available
Snapshot gcc-7-20170615 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20170615/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7-branch revision 249229 You'll find: gcc-7-20170615.tar.xzComplete GCC SHA256=33c04f780d1edd94aeb6078960f8d51f20151639d7dcc370bc65a40c1d5d1270 SHA1=9dbf695c4366191565ac62bb844db05c92f35256 Diffs from 7-20170608 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-7 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
git svn dcommit migration error
I ran into another git-svn error. I thought I'd post it here for reference, and in case someone has some ideas of what might have caused it or how to avoid it. $ git svn dcommit Migrating from a git-svn v1 layout... Data from a previous version of git-svn exists, but .git/svn (required for this version (2.9.3) of git-svn) does not exist. Done migrating from a git-svn v1 layout Unable to determine upstream SVN information from HEAD history. Perhaps the repository is empty. at /usr/libexec/git-core/git-svn line 866. The repository was created by $ git clone $ cd $ git remote set-url origin Martin
