[BRLTTY] Intro and a question

Mon May 31 21:36:20 EDT 2021

Hi Mario.

The patch applied correctly. Not surprising I guess as it had the stock GNU Screen 4.2.1` tarball to work with.

I totally concede this is was an inadvisable tactic, which I idlely tried with the expectation that it would fail immediately. I plan to dig deeper when I have more time, i.e., the toddler is asleep and the house is clean. lol

For what it's worth, I've just tried building without the patch, with identical results. I'll keep looking when I can, but the output is below FYI.

Cheers.
Ben

The build with GCC fails at the link stage with:
/usr/local/bin/gcc-11  -o screen screen.o ansi.o fileio.o mark.o misc.o resize.o socket.o search.o tty.o term.o window.o utmp.o loadav.o putenv.o help.o termcap.o input.o attacher.o pty.o process.o display.o comm.o kmapdef.o acls.o braille.o braille_tsi.o logfile.o layer.o list_generic.o list_display.o list_window.o sched.o teln.o nethack.o encoding.o canvas.o layout.o viewport.o -lcurses 
duplicate symbol '_shm' in:
    screen.o
    sched.o
ld: 1 duplicate symbol for architecture x86_64
collect2: error: ld returned 1 exit status

When running ./configure with clang, my cursory examination of the output showed:
conftest.c:24:8: error: implicitly declaring library function 'exit' with type
      'void (int) __attribute__((noreturn))'
      [-Werror,-Wimplicit-function-declaration]
main(){exit(0);}
       ^
conftest.c:24:8: note: include the header <stdlib.h> or explicitly provide a
      declaration for 'exit'
1 warning and 1 error generated.

I'll keep lookinCheers.
Ben

> On 1 Jun 2021, at 3:16 am, Mario Lang <mlang at blind.guru> wrote:
> 
> Jason White <jason at jasonjgw.net <mailto:jason at jasonjgw.net>> writes:
> 
>> I've been on this list for a long time, and the GNU screen-based
>> interface to BRLTTY is rarely mentioned. You may be the first person
>> to try it in quite a while.
> 
> The GNU Screen patch method is pretty much the only way to get things
> going on some of the platforms we try to support.  MacOS and OpenBSD come to mind.
> We wanted to implement bridges to more terminal emulators one day, but
> that project never really got off the ground.
> 
> Regarding what Ben wrote, I dont think it is a good idea to trick
> configure and override the compiler manually.  It would be far more
> fruitful to actually investigate what configure is complaining about.
> 
> I currently have no working Mac at my disposal, so I can not do this
> myself.  Remote access could help, or someone with a Mac and current OS
> would need to investigate why building screen apparently fails.
> 
> Ben, did the patch actually apply without errors?  Did you check that?
> 
>> On 29/5/21 9:02 pm, Ben van Poppel wrote:
>>> 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 <mlang at tugraz.at> wrote:
>>>> 
>>>> Ben van Poppel <benvanpoppel at gmail.com> 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: mlang at tugraz.at
>>>> 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: BRLTTY at brltty.app
>>> For general information, go to: http://brltty.app/mailman/listinfo/brltty
>> _______________________________________________
>> This message was sent via the BRLTTY mailing list.
>> To post a message, send an e-mail to: BRLTTY at brltty.app
>> For general information, go to: http://brltty.app/mailman/listinfo/brltty
>> 
> 
> -- 
> CYa,
>  ⡍⠁⠗⠊⠕
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.app <mailto:BRLTTY at brltty.app>
> For general information, go to: http://brltty.app/mailman/listinfo/brltty <http://brltty.app/mailman/listinfo/brltty>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.app/pipermail/brltty/attachments/20210601/5d233845/attachment.html>