[gnu.org #858034] Re: Broken links to online gcc manual

2013-09-21 Thread Niels Möller
Jonathan Wakely writes: > On 21 September 2013 09:11, Niels Möller wrote: >> The page https://www.gnu.org/software/gcc/ links to >> https://www.gnu.org/software/gcc/onlinedocs/, which is dead (404 Not >> found). > > Works for me, I get a 302 redirect: After a night's sleep, I realize that most l

gcc-4.7-20130921 is now available

2013-09-21 Thread gccadmin
Snapshot gcc-4.7-20130921 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20130921/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Impressive music!

2013-09-21 Thread Mike Mainstream Media
You've ben invited to gain access to our website. After reviewing some material , I could see why. You have potential, and we have the power to give you an advantage over your competition in this internet era. Enjoy! GoMainstreamUk.com Password: nmg Thanks Mike

Re: Broken links to online gcc manual

2013-09-21 Thread Jonathan Wakely
On 21 September 2013 09:11, Niels Möller wrote: > I tried to find the gcc manual online, and it was harder than I > expected. You can find them via www.gnu.org, or go straight to the GCC website, http://gcc.gnu.org/ > The page https://www.gnu.org/software/gcc/ links to > https://www.gnu.org/softw

Broken links to online gcc manual

2013-09-21 Thread Niels Möller
I tried to find the gcc manual online, and it was harder than I expected. The page https://www.gnu.org/software/gcc/ links to https://www.gnu.org/software/gcc/onlinedocs/, which is dead (404 Not found). And the long list at https://www.gnu.org/manual/ links to http://gcc.gnu.org/onlinedocs/gcc/, w

Re: possible gcc bug?

2013-09-21 Thread Andreas Schwab
George R Goffe writes: > This error message appears because line 500 of the configure script has an > improperly(?) formed if statement:     > > > 500   if ls -dL / >/dev/null 2>&1; then This statement is perfectly correct. It is testing the exit code of executing the ls command. Your proble