'./configure --dotnet' doesn't work - 'import dotnet' returns error

2018-11-07 Thread dmwpepper
Newbie question - The instructions to get .net rules appear to be straight-forward, but it doesn't appear to be working. I've followed the install and configure instructions: ./bootstrap.sh ./configure --dotnet make make install ar -t /usr/local/lib/libyara.a shows dotnet.o in libyara.a Ho

Re: './configure --dotnet' doesn't work - 'import dotnet' returns error

2018-11-07 Thread Wesley Shields
It should be —enable-dotnet — WXS On Wed, Nov 7, 2018 at 2:09 PM wrote: > > Newbie question - The instructions to get .net rules appear to be > straight-forward, but it doesn't appear to be working. > > > I've followed the install and configure instructions: > > ./bootstrap.sh > ./configure --d

Re: './configure --dotnet' doesn't work - 'import dotnet' returns error

2018-11-07 Thread dmwpepper
Sorry, it was --enable-docnet On Wednesday, November 7, 2018 at 2:21:59 PM UTC-5, Wesley Shields wrote: > > It should be —enable-dotnet > > — WXS > > On Wed, Nov 7, 2018 at 2:09 PM > wrote: > >> >> Newbie question - The instructions to get .net rules appear to be >> straight-forward, but it does

Re: './configure --dotnet' doesn't work - 'import dotnet' returns error

2018-11-07 Thread dmwpepper
Sorry, typo in my question. I actually did use ./configure --enable-dotnet and I get the error described. Reinstalling again, however, I get error no. 33, ERROR_INVALID_FIELD_NAME on a line in another rules file that has dotnet.assembly.name. How can I determine what field names are valid or w

Re: './configure --dotnet' doesn't work - 'import dotnet' returns error

2018-11-07 Thread dmwpepper
Looking at the documentation for 3.8.1, docnet.assembly.name appears to be a valid name, example given: *Example: dotnet.assembly.name == “Keylogger”* On Wednesday, November 7, 2018 at 2:33:15 PM UTC-5, dmwp...@gmail.com wrote: > > Sorry, typo in my question. I actually did use ./configure > --