I am attempting to build the Perl DBD::Teradata DBI driver on 64 bit linux. However, I do not have the header files necessary to do so. According to the documentation (http://www.presicient.com/tdatdbd/), the following files are required:
parcel.h
dbcarea.h
coperr.h
coptypes.h
I've spent hours scouring Teradata's site and the internet at large with no success. I saw mention of a CLIv2 developer's kit, but could not locate this either.
Could anyone point me to where I can get these files? I would sincerely appreciate the help.
You should have searched your PC instead :-)
Installing the Teradata Client usually includes CLI, the header files are located in the Teradata Client directory under cliv2, e.g. in Windows
C:\program files\teradata\client\14.10\cliv2\inc
If you're running a different OS you might check the installation guide
I was able to find the headers in one of the rpm files from the cliv2 linux download. I missed the second rpm file last time around and so I didn't find my files.
Here's the download link (as pointed out by dnoeth in comments below):
downloads.teradata.com/download/connectivity/cliv2/linux
if you decompress the tarball you'll find the headers in this rpm:
cliv2/cliv2-15.00.00.03-1.noarch.rpm
I am still not able to install the rpm, but I was able to pull the headers out for my DBD::Teradata build:
plxc16479> rpm2cpio cliv2/cliv2-15.00.00.03-1.noarch.rpm | cpio -idmv
./opt/teradata
./opt/teradata/client
./opt/teradata/client/15.00
./opt/teradata/client/15.00/include
./opt/teradata/client/15.00/include/cliv2if.h
./opt/teradata/client/15.00/include/coperr.h
./opt/teradata/client/15.00/include/coptypes.h
./opt/teradata/client/15.00/include/dbca2px.h
./opt/teradata/client/15.00/include/dbcarea.h
./opt/teradata/client/15.00/include/dbcerr.h
./opt/teradata/client/15.00/include/dbchqep.h
./opt/teradata/client/15.00/include/mosiif.h
./opt/teradata/client/15.00/include/parcel.h
Thanks for those that took the time to help out!
Related
I'm using tcsh shell to access installation packages for my research. After a recent update, my login shell is no longer able to find where those installation files are located. I receive a prompt like this:
!! Attention: GEMC installation check /opt/jlab_software/2.5/Darwin_macosx12.2.1-clang13.0.0/gemc/2.9/gemc not found
Where GEMC is one of several installation files.
I see that it is looking in the directory Darwin_macosx12.2.1-clang13.0.0, which is not where the files are located, but rather they are located in Darwin_macosx12.1-clang13.0.0. I tried creating a symbolic link with the following command:
ln -s Darwin_macosx12.2.1-clang13.0.0 Darwin_macosx12.1-clang13.0.0
But I am still receiving the error informing me that the files are not found. I figured that I incorrectly used the symbolic link (and probably still am) so I pasted in the entire paths in the above command, and still no luck.
I am still kind of a newbie when it comes to Unix commands and navigation, so I apologize if I explained this poorly. That being said, I would really appreciate if someone could help me find a solution to this problem. Thank you in advance!
I have a bit of a stupid question. I am trying to install Eucalyptus Fast Start and the installation guide states that you must have access to the Eucalyptus FastStart ISO.
It then directs you to the following link:
http://www.eucalyptus.com/download/faststart
However this only gives me documentation on the installation process.
Does anyone know where I can find the relevant ISO files to download? I have been searching for the last number of hours with no luck.
Thanks in advance,
Amy
It looks to me like FastStart ISO has been removed. But the RPMs are still in the repository. So, if you have a CentOS 7.3 machine, you can try using a bash script from www.eucalyptus.com/install to drive an all-in-one installation:
bash <(curl -Ls http://www.eucalyptus.com/install)
Or you can follow the full installation instructions, of course:
https://docs.eucalyptus.com/eucalyptus/latest/#install-guide/index.html
Admittedly that's more work than booting up an ISO.
I downloaded the code of kibana 4.1.3 in GitHub.
I tried to run it, but I don't know how?
Here is the code I used,
sudo npm install
sudo bower install -allow-root
grunt
I am not exactly sure what you are looking at here.
I had a look here,
https://github.com/elastic/kibana
and it says this,
Download: http://www.elastic.co/downloads/kibana
Extract the files
Run bin/kibana on unix, or bin\kibana.bat on Windows.
Visit http://localhost:5601
When I downloaded something from here,
https://www.elastic.co/downloads/past-releases/kibana-4-1-3
The readme.txt file inside says this,
Installation
============
Download: http://www.elastic.co/downloads/kibana
Run bin/kibana on unix, or bin\kibana.bat on Windows.
Visit http://localhost:5601
Which is pretty much the same. In the bin folder there is a script, kibana, and I think that is what it is telling you to run.
Hopefully that helps, but I have no specific knowledge of what you are doing here. Please expand your question if you need further help.
I have a computer behind a very restrictive proxy server it only allows me to surf the web and download programs it does not allow programs like the Atom text editor to download it's packages.
My question is how do I install them using only browser based downloads?
It is certainly possible:
Find the package you want to install, for example the activate-power-mode package.
Click on the Repo button to go to the GitHub repository.
Click Releases towards the top of the UI, then click on the most recent release, 0.4.1 in this case.
Download the source code release in either Zip or GZip depending on your platform.
Extract the content of the archive to a known permanent location, I have chosen:
C:\Source\Atom
Run the following command from your terminal / command prompt (make sure to include quotes around the path):
apm link "C:\Source\Atom\activate-power-mode-0.4.1"
Restart or Reload Ctrl-Alt-R Atom and the package will now be installed.
You can alternatively extract the package directly to your ~/.atom/packages folder however you will have to rename the folder to exactly match the name of the package, additionally uninstalling the package from Atom will delete the files which could be annoying if it is an accidental deletion.
Because of package dependencies a safest bet is this:
Install package normally on connected computer
Copy contents from your ~/.atom/packages
Paste contents to ~/.atom/packages on offline computer
Restart Atom
At least this worked for me like a charm.
The answer of Richard Slater is informative and the answer of Andriy Buday could look less professional. But, in my case, the answer of Andriy Buday was also very important.
I tried to install two packages atom-beautify and prettier-atom by following the answer of Richard Slater and had some problems of not being able to find some modules. It was not only me who had these problems. Consider checking the following links.
The issue of "cannot find module event-kit"
https://github.com/Glavin001/atom-beautify/issues/1734
https://github.com/Glavin001/atom-beautify/issues/1366#issuecomment-269716306
When I decompressed a file (atom-beautify-0.30.3.tar.gz) I received from GitHub respository, I could find out directories like appveyor, docs, and examples. But I could not find out a directory named node_modules which was present when I installed this package atom-beautify using Atom Editor online.
To check if the absence of directory node_modules is the only problem, I went through the following steps.
Start Atom Editor.
Install atom-beautify using Atom Editor online like the answer of Andriy Buday suggests.
Close Atom Editor.
Move atom-beautify directory from ~/.atom/packages (that was %HOMEDIRECTORY%%HOMEPATH%.atom\packages in my case because I used cmd on Windows 10) to somewhere else.
Decompress atom-beautify-0.30.3.tar.gz and move or copy atom-beautify-0.30.3 directory from this decompressed result into %HOMEDIRECTORY%%HOMEPATH%.atom\packages as the answer of Andriy Buday suggests.
Rename directory %HOMEDIRECTORY%%HOMEPATH%.atom\packages\atom-beautify-0.30.3 to %HOMEDIRECTORY%%HOMEPATH%.atom\packages\atom-beautify as the answer of Richard Slater suggests.
Move or copy node_modules directory from the directory moved at step 4 into %HOMEDIRECTORY%%HOMEPATH%.atom\packages\atom-beautify.
Start Atom Editor.
I found that no error message appeared and that package atom-beautify worked properly, thus I am thinking that absence of node_modules directory was the only problem of the file atom-beautify-0.30.3.tar.gz I received from GitHub repository.
I am afraid if it is normal that directory node_modules is not contained in the file atom-beautify-0.30.3.tar.gz downloaded from GitHub repository because of any rules I do not know yet, like placing directories like node_modules somewhere else. If there really are such rules and somebody tells me about such rules by adding an answer or a comment here, I will appreciate it a lot.
I am not sure if it is same with all other packages, but I found that it was same at least with package prettier-atom.
I wish it helps somebody.
+++++++++++++++++++++++++++
I found why the directory node_modules was not contained in atom-beautify-0.30.3.tar.gz.
I checked answers of the following link.
How can I manually download packages for atom editor and install them (manually)?
Answer by D3181 included a link to a page of http://discuss.atom.io/ (I could get a helpful answer by Alchiadus from the link) and suggested running apm install in the package's directory. If it is necessary to use a file downloaded from GitHub repository like atom-beautify-0.30.3.tar.gz, it is necessary to run apm install in the package's directory before copying or moving into %HOMEDIRECTORY%%HOMEPATH%\.atom\package (~/.atom/package in case of *nix) of the offline computer.
Decompress the file downloaded from GitHub repository like atom-beautify-0.30.3.tar.gz.
Go into the directory like atom-beautify-0.30.3 of the decompressed result.
Run apm install on an online computer. (If the directory of apm.cmd is not in PATH, run {directory of apm.cmd}\apm.cmd install.)
Rename directory like atom-beautify-0.30.3 to the correct name of the package like atom-beautify.
Move directory with the correct name of the package like atom-beautify into %HOMEDIRECTORY%%HOMEPATH%\.atom\packages of the offline computer.
Run Atom Editor on the offline computer and check if the package works properly.
It seems normal that the directory node_modules is not included the the compressed file downloaded from GitHub repository.
I wrote a .spec file on RHEL and I am building RPM using rpmbuild. I need ideas on how to handle the situation below.
My RPM creates an empty logs directory when it installs first time within the installation folder like below
/opt/MyInstallation-1.0.0-1/some executables
/opt/MyInstallation-1.0.0-1/lib/carries shared objects(.so files)
/opt/MyInstallation-1.0.0-1/config/carries some XML and custom configuration files(.xml, etc)
/opt/MyInstallation-1.0.0-1/log--->This is where application writes logs
When my RPM upgrades MyInstallation-1.0.0-1, to MyInstallation-1.0.0-2 for example, I get everything right as I wanted.
But, my question is how to preserve log files written in MyInstallation-1.0.0-1? Or to precisely copy the log directory to MyInstallation-1.0.0-2.
I believe if you tag the directory as %config, it is expected that the user will have files in there, so it will leave it alone.
I found a solution or workaround to this by hit and trial method :)
I am using rpmbuild version 4.8.0 on RHEL 6.3 x86_64. I believe it will work on other distros as well.
If you install with one name only like "MyInstallation" rather than "MyInstallation-version number-RPM Build Number" and create "logs directory as a standard directory(no additional flags on it)[See Original Question for scenario] Whenever you upgrade, you normally don't touch logs directory. RPM will leave its contents as it is. All you have to do is to ensure that you keep the line below in the install section.
%install
install --directory $RPM_BUILD_ROOT%{_prefix}/%{name}/log
Here, prefix and name are macros. That has to do nothing with underlying concept.
Regarding config files, the following is a very precise table that will help you guarding your config files. Again, this rule can't be applied on logs our applications create.
http://www-uxsup.csx.cam.ac.uk/~jw35/docs/rpm_config.html
Thanks & Regards.