MinGW, GCC Vista,
Hi, Do you guys know if the problem with the access() standard library function has been worked around? Windows vista has an updated MSVCRT.DLL which returns false for access() using X_OK, this parameter was previously ignored, and returned true. MinGW / GCC does not work on Vista as a result. Regards Craig This message was sent using IMP, the Internet Messaging Program.
Can You Put Comments Into GCC Compiler Options Files?
GNU Compiler Collection Free Software Foundation 51 Franklin Street, Suite 500 Boston, MA 02110-1335 Everyone: I would like to start using the GNU Compiler Collection (GCC), particularly GFortran. Given the number of compiler and linker options that there are, it makes a lot of sense to put the commonly used compiler options into an options file. I read the description of the @file options file on page 28 of the manual, Using the GNU Compiler Collection 4.6.0. However, I could not find any information on whether comments are allowed in options files and, if so, how comments are designated so that the compiler does not attempt to treat them as compiler or linker options. Please let me know whether or not programmers can put comments into compiler options files. If so, please let me know how to designate comments. I am looking forward to hearing from you soon. Sincerely, Craig T. Dedo 17130 W. Burleigh Place P. O. Box 423 Mobile Phone: (414) 412-5869 Brookfield, WI 53008-0423 E-mail: USA Linked-In: http://www.linkedin.com/in/craigdedo
Code Samples
Hello, Does anyone know of a good web site for sample C code supported by GCC 3.3.2? Specifically, I am looking for code that can read files from a directory and do I/O. thanks, Craig _ PC Magazines 2007 editors choice for best Web mailaward-winning Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507
Documentation Error in Using the GNU Compiler Collection 4.2.1 & 4.3.0
GNU Compiler Collection Documentation Free Software Foundation Dear Sir or Madam: Today I found an error in versions 4.2.1 and 4.3.0 of Using the GNU Compiler Collection. Both versions have the same error. The error is at the very end of section 3.2 and is on page 21 of version 4.2.1 and page 25 of version 4.3.0. The error concerns what apparently is supposed to be the description of the @file option. Based on my knowledge of other compilers, it appears that the @file option is supposed to name a file that contains a list of compiler options. Instead of such a discussion, there are 16 lines of what is apparently LaTeX source code. Here is the content of the error. [Begin error text] %% %% This is file .tex, %% generated with the docstrip utility. %% %% The original source files were: %% %% fileerr.dtx (with options: return) %% %% This is a generated file. %% %% Copyright 1993 1994 1995 1996 1997 1998 1999 2000 %% The LaTeX3 Project and any individual authors listed elsewhere %% in this file. %% %% This file was generated from file(s) of the Standard LaTeX Tools Bundle. %% %% %% It may be distributed and/or modified under the %% conditions of the LaTeX Project Public License, either version 1.2 %% of this license or (at your option) any later version. %% The latest version of this license is in %% http://www.latex-project.org/lppl.txt %% and version 1.2 or later is part of all distributions of LaTeX %% version 1999/12/01 or later. %% %% This file may only be distributed together with a copy of the LaTeX %% Tools Bundle. You may however distribute the LaTeX Tools Bundle %% without such generated files. %% %% The list of all files belonging to the LaTeX Tools Bundle is %% given in the file manifest.txt. %% \messageFile ignored \endinput %% %% End of file .tex. /tmp/gcc-doc-update.17595/gcc/gcc/../libiberty/at-file.texi [End of error text] Please fix this error as soon as possible and replace it with the proper text. Also, when you fix this error, please include a complete description of how the @file option is supposed to work. What is the proper structure of such a file? Can it include comments? If so, how are those comments delimited? Please feel free to contact me at any time with any questions or concerns that you may have. Sincerely, Craig Dedo 17130 W. Burleigh Place P. O. Box 423 Voice Phone: (262) 783-5869 Brookfield, WI 53008-0423 Fax Phone: (262) 783-5928 USA Mobile Phone: (414) 412-5869 E-mail: <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
Successful build of gcc 3.3.4
Hi all. Just reporting a successful build of GCC version 3.3.4 for the full GCC bundle on a platform not listed in your build stats. Note that this exact version is of special interest, since it is the required release for development of Maya plugins (see http://www.alias.com/eng/support/maya/qualified_hardware/QUAL/maya_65_linux.html#os). Details of my platform are as follows: Output from config.guess: i686-pc-linux-gnu Output from gcc -v: Configured with: ./configure --prefix=/opt/gcc334 --program-suffix=334 --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --disable-libunwind-exceptions --enable-__cxa_atexit Thread model: posix gcc version 3.3.4 ** Note that the above configuration is the exact set of options required by Maya Languages selected: All in the gcc-3.3.4.tar.gz tarball. Looks like C, C++ and Java from what I can see in the bin directory. Can't see anything for ada or objc, but I wouldn't know what I was looking for anyway. ;) Distribution/OS details: Fedora Core 3 kernel-2.6.12-1.1378_FC3 glibc-2.3.5-0.fc3.1 -- Dr Craig Scott CFD group, CSIRO (CMIS) Melbourne, Australia
Re: Question regarding copyright assignment
Antoni, You'll want to get an employer disclaimer signed by your employer to make sure your contributions cannot be claimed by them. Please email ass...@fsf.org and we can work through the process. -- All the best, Craig Topham Copyright & Licensing Associate Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110 Phone: +1-617-542-5942 Fax: +1-617-542-2652 Email: cra...@fsf.org GPG key: 36C9 950D 2F68 254E D89C 7C03 F9C1 3A10 581A B853
[gnu.org #1622724] Antoni Boucher GCC
Antoni, Thank you so much for contributing. Please find the attached PDF(s) of your assignment(s) in the email after this one. Please print out the form, sign it, and then email a scanned copy in PDF format to or fax it to us at +1-617-542-2652. You can also send it to us via the postal mail if you prefer: Copyright & Licensing Associate Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110 Once the FSF has signed it, we will send you a digital copy in PDF format for your records. Remember, we can protect your work as long as we hold copyright on it. Do keep us informed as you change employers, or as your disclaimers run their course. In addition, would it be acceptable for us to publicize your contribution by microblogging that you are contributing, and listing your name in our monthly newsletter? Thank you for your contribution! All the best, Craig Topham Copyright & Licensing Associate Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110 Phone +1-617-542-5942 Fax +1-617-542-2652
[gnu.org #1622724] Antoni Boucher GCC
Antoni, Your assignment/disclaimer process with the FSF is currently complete; your fully executed PDF will be sent to you in a separate email immediately following this one. Please remember to let us know when your employment status changes, as this may affect your assignment status. Thank you for your contribution! All the best, Craig Topham Copyright & Licensing Associate Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110 Phone +1-617-542-5942 Fax +1-617-542-2652 cc - maintainer ___ INFORMATION FOR THE MAINTAINER(S) Here's how the contributor answered the question, “ Did you copy any files or text written by someone else in these changes?” No [Which files have you changed so far, and which new files have you written so far?] The patches has not been merged yet, but they changed the following files: - gcc/jit/docs/topics/compatibility.rst - gcc/jit/docs/topics/functions.rst - gcc/jit/libgccjit.c - gcc/jit/libgccjit.h - gcc/jit/libgccjit.map - gcc/jit/jit-playback.c - gcc/testsuite/jit.dg/all-non-failing-tests.h and added the following files: - gcc/testsuite/jit.dg/test-reflection.c - gcc/testsuite/jit.dg/test-cast.c
[gnu.org #1880318] Antoni Boucher, modified employer disclaimer
On 2023-02-28 17:44:55, boua...@zoho.com wrote: > Hi. > Here is the document signed. > Thank you. > My apologies, I was unexpectedly out the last couple of days. This has been resolved and you are clear to contribute with the new employer disclaimer in place. Thank you for your patience and I appreciate you following through. ~Craig > On Tue, 2023-02-28 at 15:29 -0500, Craig Topham via RT wrote: > > On 2023-02-27 10:33:46, boua...@zoho.com wrote: > > > Hi. > > > Any update on this? > > > Regards. > > > > > > > Yes. The adaptation seems fine indeed, but there a couple of small > > issues with the text: > > > > then the Free Software Foundation and the general public will be > > permanently and irrevocably licensed solely as necessary to use, > > distribute, and permit modifications by anyone, the contributions as > > originally authored by Antoni Bouche in > > these works in the Released Categories of programs they enhance, > > withoutroyalty or limitation, the subject matter of the dominating > > interest. > > > > -- there should be a "to" after anyone and I would probably leave out > > the comma too. > > -- Boucher > > -- without royalty > > > > If you can get these corrected and print/sign the disclaimer we > > should be good to go. > > > > ~Craig > > > > > > > On Tue, 2023-02-14 at 21:51 -0500, Antoni Boucher wrote: > > > > Hi. > > > > They change the text. > > > > I attached the new version. > > > > Does that look correct? > > > > Thanks. > > > > > > > > On Mon, 2023-01-30 at 16:01 -0500, Craig Topham via RT wrote: > > > > > On 2023-01-30 09:27:02, boua...@zoho.com wrote: > > > > > > Hi. > > > > > > Any news on this? > > > > > > Thanks. > > > > > > > > > > > > On Tue, 2022-12-13 at 13:58 -0500, Craig Topham via RT wrote: > > > > > > > On 2022-12-13 10:24:30, boua...@zoho.com wrote: > > > > > > > > Hi. > > > > > > > > Is there any progress here? > > > > > > > > > > > > > > > > > We have made some progress. However, there is some other > > > > > language > > > > > that concerns us. In the second to last paragraph it reads, > > > > > "...solely as necessary to use the contributions as originally > > > > > authored...". > > > > > > > > > > As stated, it would only cover your original contributions > > > > > unedited. > > > > > Therefore, versions of your contributions edited by other > > > > > developers > > > > > would not be covered by this disclaimer. Can you request to > > > > > have > > > > > this > > > > > language changed? > > > > > > > > > > Assuming this can be corrected there is no other language in > > > > > the > > > > > disclaimer that concerns us, so we could proceed with accepting > > > > > this > > > > > disclaimer. > > > > > > > > > > Thank you again for working through this process. > > > > > > > > > > ~Craig > > > > > > > > > > > > > > > > > Thank you for the ping. I have no new updates at this time > > > > > > > except > > > > > > > that the removal of the problematic sentence allows us to > > > > > > > look > > > > > > > at > > > > > > > the > > > > > > > other language in the disclaimer. I am glad to say yours is > > > > > > > next > > > > > > > to > > > > > > > be reviewed. Please feel free to ping me at any time for an > > > > > > > update. > > > > > > > > > > > > > > ~Craig > > > > > > > > > > > > > > > > > > > > > > Regards. > > > > > > > > > > > > > > > > On Thu, 2022-12-01 at 12:08 -0500, Antoni Boucher wrote: > > > > > > > > > They're ok with removing that sentence. > > > > > > > > > Do you have any news from the legal counsel? > > > > > > > > > > > > > > > > > >
[gnu.org #2021668] Robert Joseph Dubner GCC, GDB
Robert, Thank you so much for contributing. Please find the attached PDF of your assignment(s) in the email following this one. Please print out the form, sign it, and then email a scanned copy in PDF format to or fax it to us at +1-617-542-2652. You can also send it to us via the postal mail if you prefer: Assignment Administrator Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110 Once the FSF has signed it, we will send you a digital copy in pdf format for your records. If you use GPG, you can sign your assignment using a detached signature in the following manner: gpg -a --detach-sig ASSIGNMENT Where ASSIGNMENT is the PDF file(s) as you have received it from us. Then simply email the assignment, key ID, and signature file back to us at ass...@gnu.org. Please make sure that your key is listed on a public keyserver. Remember, we can protect your work as long as we hold copyright on it. Do keep us informed as you change employers, or as your disclaimers run their course. Your current disclaimer with Symas is good until 2025-02-11. In addition, would it be acceptable for us to publicize your contribution by microblogging that you are contributing, and listing your name in our monthly newsletter? Thank you for your contribution! All the best, Craig Topham Copyright & Licensing Associate Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110 Phone +1-617-542-5942 Fax +1-617-542-2652 Email: cra...@fsf.org GPG key: 36C9 950D 2F68 254E D89C 7C03 F9C1 3A10 581A B853
[gnu.org #2021668] Robert Joseph Dubner GCC, GDB
Hello, Your assignment/disclaimer process with the FSF is currently complete; your fully executed PDF will be sent to you in a separate email immediately following this one. Please remember to let us know when your employment status changes, as this may affect your assignment status. Thank you for your contribution! All the best, Craig Topham Copyright & Licensing Associate Free Software Foundation 31 Milk Street, # 960789 Boston, MA 02196 USA Phone +1-617-542-5942 Fax +1-617-542-2652 Email: cra...@fsf.org GPG key: 36C9 950D 2F68 254E D89C 7C03 F9C1 3A10 581A B853 cc - maintainer ___ INFORMATION FOR THE MAINTAINER(S) Here's how the contributor answered the question, “ Did you copy any files or text written by someone else in these changes?” No [Which files have you changed so far, and which new files have you written so far?] None.
