I know this might be a dumb question, but I cannot figure out how to install and use Apache Daffodil. Any help would be appreciated. I cannot find anything helpful. Thank you!
Download apache Daffodil from below url
https://downloads.apache.org/daffodil/3.0.0/src/apache-daffodil-3.0.0-incubating-src.zip
The binary Daffodil releases contain a /bin directory that contains two scripts: daffodil.bat for Windows and daffodil for Linux. These files must be executed on the command line.
Extract downloaded zip
Path of bin directory export as environment variables.
After that you can verify its installed or not via below cammand it will show the version of daffodil
daffodil --version
Global Options
-d, --debug [FILE]
Enable the interactive debugger. See the Interactive Debugger documentation for more information.
The optional FILE argument contains a list of debugger commands that are provided to the debugger as they were typed by the user.
This option cannot be used with the --trace option.
-t, --trace
Enable a trace mode. This mode prints out helpful information during every stage of parsing.
This option cannot be used with the --debug option.
-v, --verbose
Enable verbose mode and increment verbosity level. Each additional v provides a new level of information.
--version
Display the version of Daffodil.
--help
Display help message.
Related
I've built the release version of OpenSSL 1.1.1c libraries without a problem, but I cannot create the Debug version.
According the documentation I used:
perl Configure --debug VC-WIN64A
However the Perl % (ActiveState) doesn't recognize the argument debug.
When I use -d, the build alone will switch to the debug execution mode.
Somewhere on Internet I found the form:
perl Configure debug-VC-WIN64A
However, I couldn't confirm it with the documentation.
What is the proper format for the Perl?
-d does not work with windows builds... The original poster had it correct, he just had the parameters in the wrong order...
On Windows, to build a debug version, you do it like:
perl Configure VC-WIN64A --debug
I just verified it just now, as I'm building 1.1.1l as we speak. Omitting that flag, defined NDEBUG, but specifying that flag defines DEBUG. Original poster specified --debug before VC-WIN64A, but it must be specified after.
according the documentation I used:
perl Configure --debug VC-WIN64A
However the Perl % (ActiveState) doesn't recognize the argument debug.
When I use -d, the build alone will switch to the debug execution
mode.
According to Compilation and Installation on the OpenSSL wiki, you should use -d. See Configure Options
Somewhere on Internet I found
perl Configure debug-VC-WIN64A
however, I couldn't confirm it with the documentation.
Use Configure LIST to show the targets.
$ ./Configure LIST | grep VC
VC-CE
VC-WIN32
VC-WIN32-ARM
VC-WIN32-ARM-UWP
VC-WIN32-ONECORE
VC-WIN32-UWP
VC-WIN64-ARM
VC-WIN64-ARM-UWP
VC-WIN64A
VC-WIN64A-ONECORE
VC-WIN64A-UWP
VC-WIN64A-masm
VC-WIN64I
You might also be interested in NOTES.WIN, which are the build and install notes for Windows. The notes do not list --debug.
It looks like --debug is detailed in INSTALL file. --debug works on Linux for OpenSSL 1.1. Maybe it does not work on Windows, or maybe it used to work with a version like OpenSSL 1.0.
(I don't have a Windows machine with Perl, so I can't run the tests for you).
Question: What are the steps to install a kubectl plugin on Windows?
I have written a plugin standalone binary that I would like to invoke from within kubectl (following the instructions in https://kubernetes.io/docs/tasks/extend-kubectl/kubectl-plugins/)
The documentation for installation states to perform the following steps:
"A plugin is nothing more than a standalone executable file, whose name begins with kubectl-. To install a plugin, simply move this executable file to anywhere on your PATH."
This works fine on Mac and Linux, but performing those instructions on Windows does not seem to work. Running "kubectl plugin list" does not list my plugin and I cannot invoke it from within kubectl. I even tried adding my binary to the .kube directory autogenerated by kubectl, and it does not detect the plugin.
Several discussions on github reference this issue, without providing a response of how to install a kubectl plugin on Windows (ex: https://github.com/kubernetes/kubernetes/issues/73289). And after performing a lengthy google/stackoverflow search, there don't seem to be any tutorials/solutions that I (or my teammates) could locate. Any help would be much appreciated! Thank you.
In my case I don't have an issue with installing a plugin on Windows 10 machine (by simply including it on my PATH). Here is the output of 'kubectl plugin list':
c:\opt\bin>kubectl plugin list
The following kubectl-compatible plugins are available:
c:\opt\bin\kubectl-getbuildver.bat
- warning: c:\opt\bin\kubectl-getbuildver.bat identified as a kubectl plugin, but it is not executable
c:\opt\bin\kubectl-hello.exe
c:\opt\bin\kubectl-helloworld.p6
- warning: c:\opt\bin\kubectl-helloworld.p6 identified as a kubectl plugin, but it is not executable
error: 2 plugin warnings were found
Instead I'm encountering a known github issue: 'not supported by windows' error, while invoking my plugin with kubectl (v1.13.4).
c:\opt\bin>kubectl hello
not supported by windows
c:\opt\bin>kubectl-hello.exe
Tuesday
*kubectl-hello.exe - is console application written in csharp. I tried also to use Windows batch file and Perl6 program as plugins, but none of these worked out on Windows.
I think only .exe file extensions are considered as executables by kubectl when it searches for plugins in the $PATH when running in Windows environment.
I tested by creating a simple HelloWorld App as a single file executable, added it to my system's $PATH and it got picked up and executed correctly.
kubectl krew like brew to manage the kubectl plugin. You can try it. It supports Window.
https://github.com/kubernetes-sigs/krew
So I am trying to use both the -verbosity and -version option together on the nuget command line. I need to use both and then parse the output of the verbosity log (this will determine other behaviors). So it is important that I get the verbose log. But for version control and making sure I can download the necessary packages again if need be I need to be able to specify -version.
Here is my commands and outputs:
(with only verbosity)
[C:\Users\C\Downloads]nuget install prism.PubSubEvents -verbosity detailed
GET https://www.nuget.org/api/v2/FindPackagesById()?$filter=IsLatestVersion&$orderby=Version desc&$top=1&id='prism.PubSubEvents'
GET https://www.nuget.org/api/v2/Packages(Id='prism.PubSubEvents',Version='1.1.2')
Installing 'Prism.PubSubEvents 1.1.2'.
Successfully installed 'Prism.PubSubEvents 1.1.2'.
(with both, after deleting the folder I just downloaded)
[C:\Users\C\Downloads]nuget install prism.PubSubEvents -verbosity detailed -version 1.0.0
Installing 'Prism.PubSubEvents 1.0.0'.
Successfully installed 'Prism.PubSubEvents 1.0.0'.
Switching the order of the options around and also it doesn't matter if I specify and older version or even the newest version.
Any help would be greatly appreciated.
I am returning to answer this in case anyone else finds it.
As it turns out, nuget caches all packages which are downloaded in %APPDATA%Local\NuGet\Cache and looks there first before going to download any packages from the web. That is why no output was coming out, because it doesn't say that is is looking in the cache and just picks them up from there without going to the web.
However, you can choose to ignore the cache with the -nocache option. This will always give you some kind of verbose output (although it is a little unpredictable)
When running phpunit 4.5 with hhvm inside docker sometimes it crashes the container. I'm not sure if I should alter the way I run hhvm on the command line or not. Are there any standards for running hhvm on the commandline?
So I'd like to get more familiar with hhvm's command line flags and definitions. Where can I find documentation on this?
I read on the https://codeascraft.com/2015/04/06/experimenting-with-hhvm-at-etsy/ that they used a tool called 'perf'. I don't seem to generate any perf.map files from the commandline. Browser requests have generated perf.map files though.
FYI
I've installed hhvm-nightly-dbg on ubuntu:14.10 to try to get more information when hhvm hangs on the command line.
My setup consists of the following
Mac osx Mavericks
Vagrant 1.7.2
VirtualBox 4.3.26
coreos-vagrant (running all containers with docker 1.5)
The containers are running
Redis:2.8.19
Mysql:5.1.73
hhvm-nightly-dbg
In our Ubuntu packages, configuration lives in /etc/hhvm/*.ini. Both files are loaded and combined when running in server mode.
Many INI options from PHP are available in HHVM with the same name. The HHVM-specific INI options are listed on the HHVM wiki; many are unfortunately missing documentation, though all of the important ones are there. There's a huge array of configurability here; you'll never need 99% of these.
/etc/init.d/hhvm controls the exact command-line options; you shouldn't need to modify this, set INI options instead.
Although you can pass any INI option to HHVM on the command line when not running in server mode, the mapping between command-line and INI syntax is weird and inconsistent for historical reasons. I'd strongly recommend just passing -c path/to/config.ini as a command line option instead, and just writing all your options in INI files. You can pass -c more than once; the files will be combined.
This is sort of a followup to this thread--unfortunately I didn't make any progress at the time so I thought I would start over. I am consistently getting this in the debugging log (QtCreator 2.3.1, Qt 4.7.3, gdb 7.2):
A syntax error in expression, near 0'.\n"
295^error,msg="A syntax error in expression, near0'."
&"Python scripting is not supported in this copy of GDB.\n"
296^error,msg="Python scripting is not supported in this copy of GDB."
&"Python scripting is not supported in this copy of GDB.\n"
297^error,msg="Python scripting is not supported in this copy of GDB."
&"Python scripting is not supported in this copy of GDB.\n"
298^error,msg="Python scripting is not supported in this copy of GDB."
&"Undefined command: \"bbsetup\". Try \"help\".\n"
299^error,msg="Undefined command: \"bbsetup\". Try \"help\"."
dThe debugging helper library was not found at .
&"source /home/matt/QtSDK-4.7.3/pythongdb/gdb\n"
&"/home/matt/QtSDK-4.7.3/pythongdb/gdb:1: Error in sourced command file:\n"
&"Undefined command: \"\". Try \"help\".\n"
300^error,msg="/home/matt/QtSDK-4.7.3/pythongdb/gdb:1: Error in sourced command file:\nUndefined command: \"\". Try \"help\"."
&"Undefined command: \"bbsetup\". Try \"help\".\n"
301^error,msg="Undefined command: \"bbsetup\". Try \"help\"."
dThe debugging helper library was not found at .
302^done
<303set substitute-path /var/tmp/qt-src /usr/include
The specific problem is that without the debugging helper, I'm unable to see the contents of QStrings and many other data structures during the debugging process, which makes it much more time-consuming. The error messages above are symptomatic, the problem arises when gdb can't find the debugging helper.
Anyway, looking at the discussion referenced in the answer in the above thread, I hunted around for different versions of gdb on my system but each one of them produced the same error (with the path changed appropriately of course), including version 7.3.1 when I downloaded it. I've also located libDebuggingHelper.so, but sticking it in different places hasn't helped either. Lastly looking at ./configure --help for gdb, I didn't see any options for enabling/disabling python in the build. Anybody know how I can get this to work?
This site claims you need to configure GDB using
./configure --with-python
It's pretty clear from the error message that the GDB you built does not have python support compiled in.
In gdb/config.log look for messages like checking whether to use python and see why GDB decided to not use Python on your system.
Perhaps you need to install Python development packages?
Once you've configured GDB to use Python, an easy way to check whether Python support is properly compiled in is:
(gdb) python print "hello"
If that prints anything other than hello, you are still not where you want to be.
I solved the problem with
sudo apt-get install gdb-multiarch
Thanks to #Employed-Russian for allowing me to check if GDB indeed has python support.
I did have to use the syntax
(gdb) python print("Hello")
To get a proper response from python within GDB.