Re: Long paths with ../../../../ throughout

2011-07-05 Thread Ian Lance Taylor
Jon Grant writes: > Ian Lance Taylor wrote, On 03/07/11 05:27: >> Jon Grant writes: > [.] >>> Another reply for this old thread. I wondered, if collect2 is >>> possibly not needed in normal use on GNU/Linux, could GCC be >>> configured to call ld directly in those cases to save launching >>> an

Re: Long paths with ../../../../ throughout

2011-07-04 Thread Jon Grant
Ian Lance Taylor wrote, On 03/07/11 05:27: Jon Grant writes: [.] Another reply for this old thread. I wondered, if collect2 is possibly not needed in normal use on GNU/Linux, could GCC be configured to call ld directly in those cases to save launching another binary. collect2 is needed if y

Re: Long paths with ../../../../ throughout

2011-07-03 Thread Richard Guenther
On Sun, Jul 3, 2011 at 6:27 AM, Ian Lance Taylor wrote: > Jon Grant writes: > >> On 2 February 2010 22:47, Ian Lance Taylor wrote: >>> Jon writes: >>> Is there a way to get collect2 to save the temporary .c file it generates to have a look at it? I believe it may be the __main()

Re: Long paths with ../../../../ throughout

2011-07-02 Thread Ian Lance Taylor
Jon Grant writes: > On 2 February 2010 22:47, Ian Lance Taylor wrote: >> Jon writes: >> >>> Is there a way to get collect2 to save the temporary .c file it >>> generates to have a look at it? I believe it may be the __main() >>> function, with the -debug option it gives the attached >>> gpluspl

Re: Long paths with ../../../../ throughout

2011-07-02 Thread Jon Grant
On 2 February 2010 22:47, Ian Lance Taylor wrote: > Jon writes: > >> Is there a way to get collect2 to save the temporary .c file it >> generates to have a look at it? I believe it may be the __main() >> function, with the -debug option it gives the attached >> gplusplus_collect2_log.txt, looking

Re: Long paths with ../../../../ throughout

2010-04-27 Thread Dave Korn
On 27/04/2010 08:17, Manuel López-Ibáñez wrote: > On 27 April 2010 02:16, Dave Korn wrote: >> Here, sometimes it's easier to show than to explain in terms of rules: > > The wiki link has a template and an example. If you think it can be > improved, please do so. I hadn't even read it at that

Re: Long paths with ../../../../ throughout

2010-04-27 Thread Manuel López-Ibáñez
On 27 April 2010 02:16, Dave Korn wrote: >  Here, sometimes it's easier to show than to explain in terms of rules: The wiki link has a template and an example. If you think it can be improved, please do so. >  Summary: Asterisks are only used for the first line of each file's changes. >  TABs at

Re: Long paths with ../../../../ throughout

2010-04-26 Thread Dave Korn
On 26/04/2010 23:18, Jon wrote: > Hi Manuel > > Manuel López-Ibáñez wrote, On 25/04/10 22:37: > [.] >> http://gcc.gnu.org/wiki/ChangeLog >> >> Basically, in your case, do not repeat the filename and mention which >> function is affected (if any). > > 2010-03-13 Jon Grant <0...@jguk.org> >

Re: Long paths with ../../../../ throughout

2010-04-26 Thread Jon
Hi Manuel Manuel López-Ibáñez wrote, On 25/04/10 22:37: [.] http://gcc.gnu.org/wiki/ChangeLog Basically, in your case, do not repeat the filename and mention which function is affected (if any). 2010-03-13 Jon Grant <0...@jguk.org> * collect2.h: vflag extern changed to bool so true/f

Re: Long paths with ../../../../ throughout

2010-04-25 Thread Ian Lance Taylor
Manuel López-Ibáñez writes: > Ian, how can I check that there is a copyright assignment in place? http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html Jon does have a copyright assignment. Ian

Re: Long paths with ../../../../ throughout

2010-04-25 Thread Manuel López-Ibáñez
On 25 April 2010 23:17, Jon wrote: > Hi Manuel > > Manuel López-Ibáñez wrote, On 25/04/10 22:00: > [.] >> >> Jon, would you mind writing a proper Changelog? > > I've attached the Changelog I wrote before. I can change if needed, let me > know what info I should add. Ideally, the format should fol

Re: Long paths with ../../../../ throughout

2010-04-25 Thread Jon
Hi Manuel Manuel López-Ibáñez wrote, On 25/04/10 22:00: [.] Jon, would you mind writing a proper Changelog? I've attached the Changelog I wrote before. I can change if needed, let me know what info I should add. I will test that the patch still passes the regression test and commit it for

Re: Long paths with ../../../../ throughout

2010-04-25 Thread Manuel López-Ibáñez
On 25 April 2010 20:03, Ian Lance Taylor wrote: > Jon writes: > >> Ian Lance Taylor wrote, On 15/03/10 03:12: >>> Jon writes: >>> How long is it until back in stage 1 development phase? >>> >>> Reasonably soon, I hope, but there is no specific schedule. >> >> Hi Ian, >> Just wanted to ask i

Re: Long paths with ../../../../ throughout

2010-04-25 Thread Ian Lance Taylor
Jon writes: > Ian Lance Taylor wrote, On 15/03/10 03:12: >> Jon writes: >> >>> How long is it until back in stage 1 development phase? >> >> Reasonably soon, I hope, but there is no specific schedule. > > Hi Ian, > Just wanted to ask if it had been possible to integrate the patch. We are now ba

Re: Long paths with ../../../../ throughout

2010-04-24 Thread Manuel López-Ibáñez
On 25 April 2010 00:19, Jon wrote: > Ian Lance Taylor wrote, On 15/03/10 03:12: >> >> Jon writes: >> >>> How long is it until back in stage 1 development phase? >> >> Reasonably soon, I hope, but there is no specific schedule. > > Hi Ian, > Just wanted to ask if it had been possible to integrate

Re: Long paths with ../../../../ throughout

2010-04-24 Thread Jon
Ian Lance Taylor wrote, On 15/03/10 03:12: Jon writes: How long is it until back in stage 1 development phase? Reasonably soon, I hope, but there is no specific schedule. Hi Ian, Just wanted to ask if it had been possible to integrate the patch. Would it be useful for me to create a bugzi

Re: Long paths with ../../../../ throughout

2010-03-14 Thread Ian Lance Taylor
Jon writes: > How long is it until back in stage 1 development phase? Reasonably soon, I hope, but there is no specific schedule. Ian

Re: Long paths with ../../../../ throughout

2010-03-13 Thread Jon
Hello Ian Ian Lance Taylor wrote, On 22/02/10 03:26: Jon writes: Good point. Updated patch attached for review. I suppose this counts as a functionality change, and as such should not be committed until after the release branch is made. This is OK when we are back in stage 1, with a Change

Re: Long paths with ../../../../ throughout

2010-02-21 Thread Ian Lance Taylor
Jon writes: > Good point. Updated patch attached for review. I suppose this counts as a functionality change, and as such should not be committed until after the release branch is made. This is OK when we are back in stage 1, with a ChangeLog entry, assuming it passes bootstrap (you didn't say)

Re: Long paths with ../../../../ throughout

2010-02-20 Thread Jon
Joseph S. Myers wrote, On 20/02/10 11:36: On Sat, 20 Feb 2010, Jon wrote: + fprintf (stderr, "Report bugs: http://gcc.gnu.org/\n";); You should use bug_report_url from version.c, which can be controlled with --with-bugurl so that distributors only need to use one configure option to ca

Re: Long paths with ../../../../ throughout

2010-02-20 Thread Joseph S. Myers
On Sat, 20 Feb 2010, Jon wrote: > + fprintf (stderr, "Report bugs: http://gcc.gnu.org/\n";); You should use bug_report_url from version.c, which can be controlled with --with-bugurl so that distributors only need to use one configure option to cause all bug reports for their distributions

Re: Long paths with ../../../../ throughout

2010-02-19 Thread Jon
Hi Ian Ian Lance Taylor wrote, On 04/02/10 00:48: Jon writes: [.] I've attached collect2 patch. Let me know what you think of it. There is actually a GNU standard for --help output, and collect2 might as well follow it. http://www.gnu.org/prep/standards/html_node/_002d_002dhelp.html That

Re: Long paths with ../../../../ throughout

2010-02-05 Thread Jon
Hello Ian Ian Lance Taylor wrote: [.] I've attached collect2 patch. Let me know what you think of it. There is actually a GNU standard for --help output, and collect2 might as well follow it. http://www.gnu.org/prep/standards/html_node/_002d_002dhelp.html Ok, looks good, I've updated the ch

Re: Long paths with ../../../../ throughout

2010-02-03 Thread Ian Lance Taylor
Jon writes: > Is there any information about how GCC start up constructors for C/C++ > are generated and called before main you could point me to please. I'd > like to understand how it works. Second half of http://www.airs.com/blog/archives/51 . > I've attached collect2 patch. Let me know what

Re: Long paths with ../../../../ throughout

2010-02-03 Thread Jon
Updated patch attached which includes collect2.h change to bool. Please include my address in any replies. Best regards, Jon Index: collect2.c === --- collect2.c (revision 156482) +++ collect2.c (working copy) @@ -174,7 +174,7 @@

Re: Long paths with ../../../../ throughout

2010-02-03 Thread Jon
Hello Ian Thank you for your reply. Ian Lance Taylor wrote: Jon writes: Is there a way to get collect2 to save the temporary .c file it generates to have a look at it? I believe it may be the __main() function, with the -debug option it gives the attached gplusplus_collect2_log.txt, looking

Re: Long paths with ../../../../ throughout

2010-02-02 Thread Ian Lance Taylor
Jon writes: > Is there a way to get collect2 to save the temporary .c file it > generates to have a look at it? I believe it may be the __main() > function, with the -debug option it gives the attached > gplusplus_collect2_log.txt, looking at the [/tmp/ccyBAI9V.c] file > though it is empty, any i

Re: Long paths with ../../../../ throughout

2010-02-02 Thread Jon
Hi Ian, Thank you for your reply. Ian Lance Taylor wrote: Jon Grant writes: I see that some of the files are located in the -L library directory specified, crtbegin.o, crtend.o in which case, perhaps they both do not need their full long path specified. Most linkers do not use the -L path t

Re: Long paths with ../../../../ throughout

2010-01-25 Thread Ian Lance Taylor
Jon Grant writes: > I see that some of the files are located in the -L library directory > specified, crtbegin.o, crtend.o in which case, perhaps they both do > not need their full long path specified. Most linkers do not use the -L path to search for file names on the command line. >>> Also I

Re: Long paths with ../../../../ throughout

2010-01-23 Thread Jon Grant
Hello Ian Thank you for the quick reply with explanations. 2010/1/19 Ian Lance Taylor : > Jon Grant writes: > >> Any easy way to evaluate and reduce command lines? Consider this: >> >> /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/crt1.o >> >> Is actually the same as: /usr/lib/crt1.o  -- whi

Re: Long paths with ../../../../ throughout

2010-01-19 Thread Ian Lance Taylor
Jon Grant writes: > Any easy way to evaluate and reduce command lines? Consider this: > > /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/crt1.o > > Is actually the same as: /usr/lib/crt1.o -- which is much clearer! Using this form of path makes it easy to move an installed gcc tree to a new

Re: Long paths with ../../../../ throughout

2010-01-19 Thread Jon Grant
2010/1/19 Jon Grant : > I should add, I'm not on this mailing list, so please include my email > address in any replies. Also I notice lots of duplicate parameters: Is this directory really needed twice? -L/usr/lib/gcc/i486-linux-gnu/4.3.3 -L/usr/lib/gcc/i486-linux-gnu/4.3.3 also -lgcc_s is ment

Re: Long paths with ../../../../ throughout

2010-01-19 Thread Jon Grant
I should add, I'm not on this mailing list, so please include my email address in any replies. Cheers, Jon