Hi Mario. Sorry. To put it another way, the only way to successfully run configure is by setting CC=/usr/local/bin/gcc-11. The only way to build the resulting configuration is setting it back to clang. No I’m definitely not running the stock Mac screen binary by mistake, because in testing I included the full path. By “runs fine“ I mean the resulting screen binary runs and seems otherwise to perform normally.
cheers. Ben > On 30 May 2021, at 12:45 am, Mario Lang <[email protected]> wrote: > > Ben van Poppel <[email protected]> writes: > >> The only strangeness when building Screen itself is that configure >> fails with Clang and the build fails with duplicate symbols with >> standard GCC. But it seems to build and run fine. > > This part of the story is confusing to me. You seem to indicate that > building screen fails with clang and gcc. But a sentence later you say > everything is fine. Could you be a little bit more precise? > How (with which compiler) did you actually successfully build screen? > Are you sure it did actually build and install, > and you aren't using a screen binary already installed on your Mac for some > reason? > > -- > AR Mario Lang Phone: +43 316 873 6897 > Graz University of Technology Mobile: +43 664 60 873 6897 > IT-Services for research and teaching Email: [email protected] > Steyrergasse 30/1, 8010 Graz, Austria Please https://useplaintext.email/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
