From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: bug-gnulib@gnu.org
Subject: Problems with directory trees "confdir-14B---" and "confdir3"
Date: Fri, 7 Jan 2022 23:43:17 +0100 [thread overview]
Message-ID: <E648370F-2528-43AF-81E1-62918AE5529C@Web.DE> (raw)
Hello!
Since a few years recent versions of bison (3.8.2), findutils (4.6.0, 4.7.0) and m4 (1.4.19) fail to build on my Apple PowerBook G4 with Tiger (Mac OS X 10.4.11) and/or Leopard (Mac OS X 10.5.8), and eleven years it failed for gzip (1.4) on someone other's Mac. The actual cause seems to be an ability of the MacPorts software (Tcl based) to remove the deep directory structure. From the shell or from inside GNU Emacs it works to overcome a "file name too long" error.
See these bug reports, particularly that for bison:
https://trac.macports.org/ticket/63603 – bison 3.8.2
https://trac.macports.org/ticket/64373 and https://trac.macports.org/ticket/58927 – findutils 4.7.0
https://trac.macports.org/ticket/63059 and https://trac.macports.org/ticket/62994 – m4 1.4.19
https://trac.macports.org/ticket/50567 – findutils 4.6.0
https://trac.macports.org/ticket/28654 – actually gzip 1.4, eleven years ago
--
Greetings
Pete
It isn't pollution that's harming the environment. It's the impurities in our air and water that are doing it.
next reply other threads:[~2022-01-08 2:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 22:43 Peter Dyballa [this message]
2022-01-08 19:27 ` Problems with directory trees "confdir-14B---" and "confdir3" Ryan Schmidt
2022-01-08 21:30 ` Peter Dyballa
2022-01-08 20:27 ` Paul Eggert
2022-01-08 22:03 ` Peter Dyballa
2022-01-08 22:29 ` Peter Dyballa
2022-01-09 0:05 ` Peter Dyballa
2022-01-09 0:31 ` Peter Dyballa
2022-01-09 11:10 ` Peter Dyballa
2022-01-09 12:01 ` Peter Dyballa
2022-01-10 23:35 ` Paul Eggert
2022-01-11 11:43 ` Peter Dyballa
2022-01-11 17:29 ` Paul Eggert
2022-01-11 17:43 ` Peter Dyballa
2024-03-18 10:08 ` Peter Dyballa
2024-03-18 17:57 ` Paul Eggert
2024-03-18 18:38 ` Peter Dyballa
2024-03-18 23:38 ` Paul Eggert
2024-03-19 0:11 ` Peter Dyballa
2024-03-19 0:50 ` Collin Funk
2024-03-19 11:35 ` Peter Dyballa
2024-03-19 11:42 ` Bruno Haible
2024-03-19 11:48 ` Peter Dyballa
2024-03-19 17:34 ` Peter Dyballa
2024-03-19 21:52 ` Paul Eggert
2024-03-19 22:32 ` Peter Dyballa
2024-03-20 0:26 ` Paul Eggert
2024-03-20 4:38 ` Paul Eggert
2024-03-20 8:51 ` Peter Dyballa
2024-03-20 22:23 ` Paul Eggert
2024-03-21 12:27 ` Peter Dyballa
2024-04-18 8:26 ` Peter Dyballa
2024-03-18 16:51 ` Peter Dyballa
2024-03-18 18:51 ` Peter Dyballa
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E648370F-2528-43AF-81E1-62918AE5529C@Web.DE \
--to=peter_dyballa@web.de \
--cc=bug-gnulib@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).