Re: Packaging ttyd a tty over http backend

[sven falempin]

On Fri, Mar 3, 2017 at 1:04 PM, Stuart Henderson  wrote:
> On 2017/03/03 11:34, sven falempin wrote:
>> About Bison, this is how it fails:
>>
>> checking for bison... yacc
>> checking for ranlib... (cached) ranlib
>> checking for GNU M4 that supports accurate traces... configure: error:
>> no acceptable m4 could be found in $PATH.
>> GNU M4 1.4.6 or later is required; 1.4.16 or newer is recommended.
>> GNU M4 1.4.15 uses a buggy replacement strstr on some systems.
>
> You may need to use gnu m4 to build this. For some configure scripts
> you can do this with "M4 = ${LOCALBASE}/bin/gm4" (and add the build dep).
>


Okay,

Actually the BUILD_DEPENDS already contains devel/m4
and the m4 i got is not in my local dir, so it is too old, and providing a path
would work ( i tried to put M4= in CONFIGURE_ENV )
did not work, so i went to m4 package and i am scratching my head

The package references libsigsegv well in WANTLIB and LIB_DEPENDS
but the command `make` simply refuses to do anything because the explicitly
marked dependencies is not fulfilled, and the program is not even trying ...
in complete head scratching mode i change the Makefile to add BUILD_DEPENDS
with of course no effect.

Index: Makefile
===
RCS file: /cvs/ports/devel/m4/Makefile,v
retrieving revision 1.32
diff -u -p -r1.32 Makefile
--- Makefile22 Nov 2013 19:53:46 -  1.32
+++ Makefile3 Mar 2017 20:42:49 -
@@ -14,6 +14,7 @@ PERMIT_PACKAGE_CDROM= Yes

 WANTLIB=   c sigsegv

+BUILD_DEPENDS= devel/libsigsegv
 LIB_DEPENDS=   devel/libsigsegv

 CONFIGURE_STYLE= gnu
cvs server: Diffing patches
cvs server: Diffing pkg
[1]-[vps102084]-[/usr/ports/devel/m4]
# make
===>  Verifying specs:  c sigsegv
Missing library for sigsegv>=0.0
Fatal error
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2144
'/usr/ports/pobj/m4-1.4.17/.buildwantlibs')
*** Error 1 in /usr/ports/devel/m4
(/usr/ports/infrastructure/mk/bsd.port.mk:2396 'all')


make install in /usr/ports/devel/libsigsegv  theproblem

Once deve/m4 is installed
bison build

Now it was my understanding that BUILD_DEPENDS would do make install
of the listed
ports.


Cheers.
-- 
--
-
Knowing is not enough; we must apply. Willing is not enough; we must do

Re: Packaging ttyd a tty over http backend

[sven falempin]

On Fri, Mar 3, 2017 at 1:04 PM, Stuart Henderson  wrote:
> On 2017/03/03 11:34, sven falempin wrote:
>> About Bison, this is how it fails:
>>
>> checking for bison... yacc
>> checking for ranlib... (cached) ranlib
>> checking for GNU M4 that supports accurate traces... configure: error:
>> no acceptable m4 could be found in $PATH.
>> GNU M4 1.4.6 or later is required; 1.4.16 or newer is recommended.
>> GNU M4 1.4.15 uses a buggy replacement strstr on some systems.
>
> You may need to use gnu m4 to build this. For some configure scripts
> you can do this with "M4 = ${LOCALBASE}/bin/gm4" (and add the build dep).
>
>> Another iccups, that is more interesting, i think, is the fact i add
>> to override MASTER_SITE
>> after using GH_ vars.
>>
>> Any pointer on that would be helpfull.
>
> You aren't using the right variables, compare yours with Makefile.template
> or any other port using them.
>

Indeed GH_TAG was not the good one,
i got confused again the the link was so close to the good one !

The following ports compile, and the binary run correctly,
a bug force to use it beside a proxy ( on my test the bundled html
file is not fullly send ) but it s stable otherwise.

I created _ttyd user and group with uid 888,
because the daemon could run as a user and only need
one html file.

Testing the software i have doubt this is a good idea,
maybe adding a rc file and user to this package is complete
overkill.

-- 
--
-
Knowing is not enough; we must apply. Willing is not enough; we must do


ttyd.tar.gz
Description: GNU Zip compressed data

Re: Packaging ttyd a tty over http backend

[Stuart Henderson]

On 2017/03/03 11:34, sven falempin wrote:
> About Bison, this is how it fails:
> 
> checking for bison... yacc
> checking for ranlib... (cached) ranlib
> checking for GNU M4 that supports accurate traces... configure: error:
> no acceptable m4 could be found in $PATH.
> GNU M4 1.4.6 or later is required; 1.4.16 or newer is recommended.
> GNU M4 1.4.15 uses a buggy replacement strstr on some systems.

You may need to use gnu m4 to build this. For some configure scripts
you can do this with "M4 = ${LOCALBASE}/bin/gm4" (and add the build dep).

> Another iccups, that is more interesting, i think, is the fact i add
> to override MASTER_SITE
> after using GH_ vars.
> 
> Any pointer on that would be helpfull.

You aren't using the right variables, compare yours with Makefile.template
or any other port using them.

Re: Packaging ttyd a tty over http backend

[sven falempin]

About Bison, this is how it fails:

checking for bison... yacc
checking for ranlib... (cached) ranlib
checking for GNU M4 that supports accurate traces... configure: error:
no acceptable m4 could be found in $PATH.
GNU M4 1.4.6 or later is required; 1.4.16 or newer is recommended.
GNU M4 1.4.15 uses a buggy replacement strstr on some systems.

Another iccups, that is more interesting, i think, is the fact i add
to override MASTER_SITE
after using GH_ vars.

Any pointer on that would be helpfull.




On Fri, Mar 3, 2017 at 10:32 AM, sven falempin  wrote:
> xterm.js is a modern implementation for tty in browser.
>
> https://github.com/tsl0922/ttyd provides a backend in c to use with xterm.js.
>
> A few patches are needed for openbsd compilation (thus i am not sure why cmake
> is used if putting c99 is such a hassle )
>
> I wanted to make a real complete package and  the html  file
> and encountered a few iccups :
> bison is not compiling ( ports tree at -rOPENBSD_6_0)
> node is required to run the yarn thingy and it requires bison
> to build.
>
> I just pkg_add node to workaround.
>
> But running node just do not work, the device is 6.0 GENERIC#2148 amd64
> # pkg_info | grep node
> node-4.4.5  V8 JavaScript for clients and servers
>
> # npm install yarn
> Abort trap (core dumped)
>
> The attached package is working ( compilation ) and maybe the yarn packaging
> would not pass the review before integration.
>
> Another way would be to yarn this somewhere else and put the result
> file in ./pkg
> along with a rcscript , the package would be build without node and without 
> the
> npm package.
>
> Please advice.
>
> Cheers.
>
> --
> -
> Knowing is not enough; we must apply. Willing is not enough; we must do.



-- 
--
-
Knowing is not enough; we must apply. Willing is not enough; we must do

Re: Packaging ttyd a tty over http backend

[sven falempin]

On Fri, Mar 3, 2017 at 10:49 AM, Aaron Bieber  wrote:
> On Fri, Mar 03, 2017 at 10:42:03AM -0500, sven falempin wrote:
>> On Fri, Mar 3, 2017 at 10:32 AM, sven falempin 
>> wrote:
>>
>> > xterm.js is a modern implementation for tty in browser.
>> >
>> > https://github.com/tsl0922/ttyd provides a backend in c to use with
>> > xterm.js.
>> >
>> > A few patches are needed for openbsd compilation (thus i am not sure why
>> > cmake
>> > is used if putting c99 is such a hassle )
>> >
>> > I wanted to make a real complete package and  the html  file
>> > and encountered a few iccups :
>> > bison is not compiling ( ports tree at -rOPENBSD_6_0)
>> > node is required to run the yarn thingy and it requires bison
>> > to build.
>> >
>> > I just pkg_add node to workaround.
>> >
>> > But running node just do not work, the device is 6.0 GENERIC#2148 amd64
>> > # pkg_info | grep node
>> > node-4.4.5  V8 JavaScript for clients and servers
>> >
>> > # npm install yarn
>> > Abort trap (core dumped)
>> >
>> > The attached package is working ( compilation ) and maybe the yarn
>> > packaging
>> > would not pass the review before integration.
>> >
>> > Another way would be to yarn this somewhere else and put the result
>> > file in ./pkg
>> > along with a rcscript , the package would be build without node and
>> > without the
>> > npm package.
>> >
>> > Please advice.
>> >
>> > Cheers.
>> >
>> >
>> >
>> About the core :
>>
>> Core was generated by `node'.
>> Program terminated with signal SIGABRT, Aborted.
>> #0  0x0a6a9b7af17a in _thread_sys___syscall () at :2
>> 2   : No such file or directory.
>> [Current thread is 1 (process 87071)]
>> (gdb) bt
>> #0  0x0a6a9b7af17a in _thread_sys___syscall () at :2
>> #1  0x0a6a9b7e688a in *_libc_mmap (addr=0x39804a722000, len=4096,
>> prot=-1686441606, flags=4098, fd=-1,
>> offset=) at /usr/src/lib/libc/sys/mmap.c:47
>> #2  0x0a67d6746271 in v8::base::OS::Allocate(unsigned long, unsigned
>> long*, bool) ()
>> #3  0x0a67d65905c5 in v8::internal::CreateSqrtFunction() ()
>> #4  0x0a67d62d8779 in v8::internal::init_fast_sqrt_function() ()
>> #5  0x0a67d6563134 in v8::internal::V8::InitializeOncePerProcessImpl()
>> ()
>> #6  0x0a67d6745240 in v8::base::CallOnceImpl(long*, void (*)(void*),
>> void*) ()
>> #7  0x0a67d65631a6 in v8::internal::V8::Initialize() ()
>> #8  0x0a67d627f799 in v8::V8::Initialize() ()
>> #9  0x0a67d61efb0e in node::Start(int, char**) ()
>> #10 0x0a67d61ce8e2 in _start ()
>> (gdb) info frame
>>   [26/1213]
>> Stack level 8, frame at 0x7f7eff20:
>>  rip = 0xa67d627f799 in v8::V8::Initialize(); saved rip = 0xa67d61efb0e
>>  called by frame at 0x7f7f0080, caller of frame at 0x7f7eff10
>>  Arglist at 0x7f7eff10, args:
>>  Locals at 0x7f7eff10, Previous frame's sp is 0x7f7eff20
>>  Saved registers:
>>   rbp at 0x7f7eff10, rip at 0x7f7eff18
>> (gdb) f 3
>> #3  0x0a67d65905c5 in v8::internal::CreateSqrtFunction() ()
>> (gdb) info frame
>> Stack level 3, frame at 0x7f7efeb0:
>>  rip = 0xa67d65905c5 in v8::internal::CreateSqrtFunction(); saved rip =
>> 0xa67d62d8779
>>  called by frame at 0x7f7efec0, caller of frame at 0x7f7efd50
>>  Arglist at 0x7f7efd50, args:
>>  Locals at 0x7f7efd50, Previous frame's sp is 0x7f7efeb0
>>  Saved registers:
>>   rbx at 0x7f7efe80, rbp at 0x7f7efea0, r12 at 0x7f7efe88, r13
>> at 0x7f7efe90, r14 at 0x7f7efe98,
>>   rip at 0x7f7efea8
>>
>>
>> the core file is here : http://filebin.ca/3EIqXoO4mmAm/node.core
>
> This looks suspiciously like the WX stuff. Is there anything in `dmesg`?
>
> --
> PGP: 0x1F81112D62A9ADCE / 3586 3350 BFEA C101 DB1A  4AF0 1F81 112D 62A9 ADCE


Yes , i just notice the wxallowed is removed because i moved around
/usr/local  to gain disk space

oops

-- 
--
-
Knowing is not enough; we must apply. Willing is not enough; we must do

Re: Packaging ttyd a tty over http backend

[sven falempin]

On Fri, Mar 3, 2017 at 10:32 AM, sven falempin 
wrote:

> xterm.js is a modern implementation for tty in browser.
>
> https://github.com/tsl0922/ttyd provides a backend in c to use with
> xterm.js.
>
> A few patches are needed for openbsd compilation (thus i am not sure why
> cmake
> is used if putting c99 is such a hassle )
>
> I wanted to make a real complete package and  the html  file
> and encountered a few iccups :
> bison is not compiling ( ports tree at -rOPENBSD_6_0)
> node is required to run the yarn thingy and it requires bison
> to build.
>
> I just pkg_add node to workaround.
>
> But running node just do not work, the device is 6.0 GENERIC#2148 amd64
> # pkg_info | grep node
> node-4.4.5  V8 JavaScript for clients and servers
>
> # npm install yarn
> Abort trap (core dumped)
>
> The attached package is working ( compilation ) and maybe the yarn
> packaging
> would not pass the review before integration.
>
> Another way would be to yarn this somewhere else and put the result
> file in ./pkg
> along with a rcscript , the package would be build without node and
> without the
> npm package.
>
> Please advice.
>
> Cheers.
>
>
>
About the core :

Core was generated by `node'.
Program terminated with signal SIGABRT, Aborted.
#0  0x0a6a9b7af17a in _thread_sys___syscall () at :2
2   : No such file or directory.
[Current thread is 1 (process 87071)]
(gdb) bt
#0  0x0a6a9b7af17a in _thread_sys___syscall () at :2
#1  0x0a6a9b7e688a in *_libc_mmap (addr=0x39804a722000, len=4096,
prot=-1686441606, flags=4098, fd=-1,
offset=) at /usr/src/lib/libc/sys/mmap.c:47
#2  0x0a67d6746271 in v8::base::OS::Allocate(unsigned long, unsigned
long*, bool) ()
#3  0x0a67d65905c5 in v8::internal::CreateSqrtFunction() ()
#4  0x0a67d62d8779 in v8::internal::init_fast_sqrt_function() ()
#5  0x0a67d6563134 in v8::internal::V8::InitializeOncePerProcessImpl()
()
#6  0x0a67d6745240 in v8::base::CallOnceImpl(long*, void (*)(void*),
void*) ()
#7  0x0a67d65631a6 in v8::internal::V8::Initialize() ()
#8  0x0a67d627f799 in v8::V8::Initialize() ()
#9  0x0a67d61efb0e in node::Start(int, char**) ()
#10 0x0a67d61ce8e2 in _start ()
(gdb) info frame
  [26/1213]
Stack level 8, frame at 0x7f7eff20:
 rip = 0xa67d627f799 in v8::V8::Initialize(); saved rip = 0xa67d61efb0e
 called by frame at 0x7f7f0080, caller of frame at 0x7f7eff10
 Arglist at 0x7f7eff10, args:
 Locals at 0x7f7eff10, Previous frame's sp is 0x7f7eff20
 Saved registers:
  rbp at 0x7f7eff10, rip at 0x7f7eff18
(gdb) f 3
#3  0x0a67d65905c5 in v8::internal::CreateSqrtFunction() ()
(gdb) info frame
Stack level 3, frame at 0x7f7efeb0:
 rip = 0xa67d65905c5 in v8::internal::CreateSqrtFunction(); saved rip =
0xa67d62d8779
 called by frame at 0x7f7efec0, caller of frame at 0x7f7efd50
 Arglist at 0x7f7efd50, args:
 Locals at 0x7f7efd50, Previous frame's sp is 0x7f7efeb0
 Saved registers:
  rbx at 0x7f7efe80, rbp at 0x7f7efea0, r12 at 0x7f7efe88, r13
at 0x7f7efe90, r14 at 0x7f7efe98,
  rip at 0x7f7efea8


the core file is here : http://filebin.ca/3EIqXoO4mmAm/node.core

Packaging ttyd a tty over http backend

[sven falempin]

xterm.js is a modern implementation for tty in browser.

https://github.com/tsl0922/ttyd provides a backend in c to use with xterm.js.

A few patches are needed for openbsd compilation (thus i am not sure why cmake
is used if putting c99 is such a hassle )

I wanted to make a real complete package and  the html  file
and encountered a few iccups :
bison is not compiling ( ports tree at -rOPENBSD_6_0)
node is required to run the yarn thingy and it requires bison
to build.

I just pkg_add node to workaround.

But running node just do not work, the device is 6.0 GENERIC#2148 amd64
# pkg_info | grep node
node-4.4.5  V8 JavaScript for clients and servers

# npm install yarn
Abort trap (core dumped)

The attached package is working ( compilation ) and maybe the yarn packaging
would not pass the review before integration.

Another way would be to yarn this somewhere else and put the result
file in ./pkg
along with a rcscript , the package would be build without node and without the
npm package.

Please advice.

Cheers.

-- 
-
Knowing is not enough; we must apply. Willing is not enough; we must do.


ttyd.tar.gz
Description: GNU Zip compressed data