public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bug-reports.delphin at laposte dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/105819] comma `,` in directory name causes build to fail
Date: Mon, 15 May 2023 16:35:04 +0000	[thread overview]
Message-ID: <bug-105819-4-UqKjEpNtZB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105819-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105819

--- Comment #17 from bug-reports.delphin at laposte dot net ---
First of all, thank you very much. You were stronly right.

In fact, it was not a PATH error, but a folder name error. I check it again and
it was true : unfortunately, I changed a dot sign to a coma sign in the name of
the folders.

I zoomed my Terminal window, and I found this : my eye vision has fairly
weakened. I didn't well differentiate between the two signs, my vision now is
too low. Even though I changed some months ago my glasses : myopia decreased,
but presbyopia increased. The new lenses have corrected - in its way of
accomodation... - the crystalline(eye) lenses, but I found that the field of
view is now very reduces : just a rectangle with a 1-mm width only,
approximately. Good book reading but failing to work before a computer screen
during several hours each day. I met the optician two weeks ago, and, when I
told her I work on a computer from the morning to the afternoon, explaining my
issues with such a vision and their glasses, she told me that my glasses are
not fairly adapted to screen reading. Now, I need to buy new dedicated glasses
for screen working, with wider and a larger and wider field of view (but not
good for book reading). Next months, or in one year.

With GCC, it was now well compiled for versions : 12.1.0, 12.2.0, 13.1.0. I had
just a matter for the 1st compilation of 13.1.0 : it looped during several (>=
6) hours at the step : echo timestamp s-gyte. I canceled the process and
started it again, after having cleaned everything in the build folder. It
compiled to the end in around 10 hours now.

Son, an advice for every developer :

Even though you are young or have a good vision, ALWAYS wear glasses protecting
your eyes when you are in front of a screen. ALWAYS. Otherwise, one day, your
vision will stronly weaken.

As an example ->

https://www.essilorindia.com/products/computer-glasses

Kind regards,

L. D.

      parent reply	other threads:[~2023-05-15 16:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  8:56 [Bug other/105819] New: GCC 12.1.0 Make failed - Compiled with GCC 4.9.4 and under Mac OS X lion - I bug-reports.delphin at laposte dot net
2022-06-02  8:57 ` [Bug other/105819] " bug-reports.delphin at laposte dot net
2022-06-02  8:58 ` bug-reports.delphin at laposte dot net
2022-06-02  9:27 ` jakub at gcc dot gnu.org
2022-06-02  9:41 ` jakub at gcc dot gnu.org
2022-06-09  8:47 ` bug-reports.delphin at laposte dot net
2022-06-09  9:11 ` redi at gcc dot gnu.org
2022-06-09  9:15 ` pinskia at gcc dot gnu.org
2022-06-09  9:18 ` jakub at gcc dot gnu.org
2022-06-09  9:20 ` jakub at gcc dot gnu.org
2022-06-14  8:38 ` bug-reports.delphin at laposte dot net
2022-09-16 15:43 ` bug-reports.delphin at laposte dot net
2022-09-16 16:31 ` redi at gcc dot gnu.org
2022-09-16 16:33 ` redi at gcc dot gnu.org
2022-09-17 10:51 ` bug-reports.delphin at laposte dot net
2023-05-03 20:22 ` redi at gcc dot gnu.org
2023-05-03 20:31 ` [Bug other/105819] comma `,` in directory name causes build to fail redi at gcc dot gnu.org
2023-05-15 16:35 ` bug-reports.delphin at laposte dot net [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105819-4-UqKjEpNtZB@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).