Re: [sed] command failure? Porting a project to FreeBSD

Am 07.06.17 um 11:06 schrieb Jov: > I don't think there is. > Man page of FreeBSD tool may have a section of STANDARDS and/or > COMPATIBILITY, but it does not list all the difference with GNU version. Greg Leheys 'Porting Unix Software' published by O'Reilly and later re-released under Creative

Re: [sed] command failure? Porting a project to FreeBSD

I don't think there is. Man page of FreeBSD tool may have a section of STANDARDS and/or COMPATIBILITY, but it does not list all the difference with GNU version. 2017-06-07 15:40 GMT+08:00 blubee blubeeme : > Ahhh, that was it. Doing a find and ask to replace all instances

Re: [sed] command failure? Porting a project to FreeBSD

On 07/06/2017 09:40, blubee blubeeme wrote: > Ahhh, that was it. Doing a find and ask to replace all instances of sed > with gsed passed that part. > > By the way, is knowledge like this written down somewhere centralized or is > it just floating in the ether? >From my experience of porting

Re: [sed] command failure? Porting a project to FreeBSD

Ahhh, that was it. Doing a find and ask to replace all instances of sed with gsed passed that part. By the way, is knowledge like this written down somewhere centralized or is it just floating in the ether? Thank you, Owen On Wed, Jun 7, 2017, 14:26 Jov wrote: > The default

Re: [sed] command failure? Porting a project to FreeBSD

The default sed on FreeBSD is different from GNU sed,there is some limit for bsd sed.You can try to patch the makefile to using gsed. 2017-06-07 14:10 GMT+08:00 blubee blubeeme : > Hello > > I am trying to bring these updated print drivers to FreeBSD: >

[sed] command failure? Porting a project to FreeBSD

Hello I am trying to bring these updated print drivers to FreeBSD: https://github.com/utsushi/utsushi.git There's the automake scripts in there that's sorta helpful but I seem to have gotten stuck with something. I made sure that my environmental variables are set LDFLAGS -L/usr/local/lib