I am looking for a cloud builder with gnu make. The Google cloud builders listed here do not mention any.
As far as I can tell it is not documented but I found out that you can use the go image for this:
$ docker run -it --entrypoint make gcr.io/cloud-builders/go:debian --version
GNU Make 4.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Related
I am using macOS Monterey (12.4).
I used ssh -X username#asasd.de for login.
Modules that are already loaded in system.
Module list:
intel-oneapi-compilers/2022.0.1-gcc-11.2.0
openmpi/4.1.2-intel-2021.5.0
netcdf-c/4.8.1-openmpi-4.1.2-intel-2021.5.0
netcdf-fortran/4.5.3-openmpi-4.1.2-intel-2021.5.0
intel-oneapi-mkl/2022.0.1-gcc-11.2.0
ncview/2.1.8-gcc-11.2.0
hdf5/1.12.1-threadsafe-intel-2021.5.0
After running a model in a /work/ directory I generate a file "file.cdf" there.
I want to open it with ncview.
So I did : $ ncview file.cdf and I am getting this error.
Ncview 2.1.8 David W. Pierce 8 March 2017
http://meteora.ucsd.edu:80/~pierce/ncview_home_page.html
Copyright (C) 1993 through 2015, David W. Pierce
Ncview comes with ABSOLUTELY NO WARRANTY; for details type `ncview -w'.
This is free software licensed under the Gnu General Public License version 3; type `ncview -c' for redistribution details.
Note: could not open file /home/.ncviewrc for reading
Error: Can't open display:
I am a win10 user. Using ubuntu 20.04 version. loaded ncview package via "sudo apt install ncview" command. 2.1.8+ds-3build2 version seems loaded but facing with the same error:
Ncview 2.1.8 David W. Pierce 8 March 2017
http://meteora.ucsd.edu:80/~pierce/ncview_home_page.html
Copyright (C) 1993 through 2015, David W. Pierce
Ncview comes with ABSOLUTELY NO WARRANTY; for details type ncview -w'. This is free software licensed under the Gnu General Public License version 3; type ncview -c' for redistribution details.
Note: could not open file /home/cahit/.ncviewrc for reading
Error: Can't open display:
Any suggestios for this situation ?
For Mac users:
I was also facing the same issue. It was solved for me after installing Xquartz on my local machine. https://www.xquartz.org/
I hope it works for you.
I also face the same problem,
Ncview 2.1.8 David W. Pierce 8 March 2017
http://meteora.ucsd.edu:80/~pierce/ncview_home_page.html
Copyright (C) 1993 through 2015, David W. Pierce
Ncview comes with ABSOLUTELY NO WARRANTY; for details type ncview -w'. This is free software licensed under the Gnu General Public License version 3; type ncview -c' for redistribution details.
Note: could not open file /home/user/.ncviewrc for reading
Error: Can't open display: :0.0
if someone resolved this issue please share.
I'm trying to update the version of make on my mac but am running into issues. The minimum project dependency is 4.1 but my version seems to be 3.81. I've updated Xcode to the latest version and installed the command line tools but it still seems to be the older version.
Has anyone run into this issue or know of a way to resolve it?
Here is what I did, and it works on my MacOS:
Step1: Install homebrew (installation command comes from https://brew.sh/):
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
Step2: Use homebrew to install make
brew install make --with-default-names
just incase it doesn't work, try this:
brew install homebrew/dupes/make --with-default-names
Step3: You need to change the default command to use correct make instead of the default one from your MacBook or Mac.
For example, if you type
make --version
You will see:
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for i386-apple-darwin11.3.0
Which is the default path for default version.
So, now, in your .bash_profile (which should be under your home dir /Users/your_name), add the following line:
export PATH="/usr/local/bin:$PATH"
Note: If you see the following message when you installed make:
GNU "make" has been installed as "gmake". If you need to use it as "make", you can add a "gnubin" directory to your PATH from
your bashrc like:
PATH="/usr/local/opt/make/libexec/gnubin:$PATH"
then instead run,
export PATH="/usr/local/opt/make/libexec/gnubin:$PATH"
Then source your .bash_profile. Now try to check your version:
make --version
It should show:
GNU Make 4.2.1
Built for x86_64-apple-darwin16.5.0
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Cheers.
Firstly, the current version:
$ make --version
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for i386-apple-darwin11.3.0
Steps to install/configure:
brew install make
export PATH="/usr/local/opt/make/libexec/gnubin:$PATH"
Result:
$ make -v
GNU Make 4.3
Built for x86_64-apple-darwin19.6.0
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
If you choose the homebrew method, you should use brew info make after brew install make succeeds. Then you will see a text like this:
If you need to use it as "make", you can add a "gnubin" directory
to your PATH from your bashrc like:
PATH="/opt/homebrew/opt/make/libexec/gnubin:$PATH"
So, add this path in your .bash_profile,The detailed steps as:
open ~/.bash_profile
Add line: export PATH="/opt/homebrew/opt/make/libexec/gnubin:$PATH"(the path you just got)
⌘ S
source ~/.bash_profile
I attempted a fix by a different approach, namely downloading the newer version of GNU Make I want to upgrade into compile that from source downloaded from the official GNU link, instead of using homebrew. Then, on my mac, I added a path to my bash shell:
export PATH=/usr/local/bin
to the ".bashrc" file in my $HOME directory.
Then reset my Terminal. And, it worked. There seems to be some issue with the homebrew download because the formula automatically links the "gmake" installation to the wrong bin, or more accurately missing the bin in the /usr/local/Cellar/etc./path. So I reckon that's probably why it does not work as of now. Hope maybe someone will fix that soon.
I am using Eclipse LUNA CDT on my Mac OSX Yosemite and I recently set up GDB 7.9.1 on my machine to debug my applications.
I noticed that the debug session is very poor: no step run per instruction, no stop on break points, I can not watch the variables content or visualise the memory (stack/heap) etc...
Does anyone use GDB for the same purpose?
Is this a limitation of Eclipse or did I install a wrong version somewhere in my development environment?
Thanks for help.
I show the following versions of my development environment:
Eclipse Version: Luna Service Release 2 (4.4.2)
gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1
Apple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM 3.6.0svn)
Target: x86_64-apple-darwin14.3.0
Thread model: posix
gdb --version
GNU gdb (GDB) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This GDB was configured as "x86_64-apple-darwin14.3.0".
Apple phased out support for GDB 7.9.1 in favor of LLDB beginning with Yosemite. Unfortunately Eclipse CDT doesn't support LLDB.
Try installing the mac ports version of gdb and the apple-gcc
compiler:
$ sudo port install gdb-apple
$ sudo port install apple-gcc42
Code sign gdb-apple after you create a system cert for it:
codesign -s gdb-cert $(which gdb-apple)
Restart the taskgated process.
Set the debugger in eclipse to use gdb-apple instead of gdb , it
should be installed to /opt/local/bin/gdb-apple
More details can be found here
http://ntraft.com/installing-gdb-on-os-x-mavericks/
I installed GDB 7.8.1 and GCC 4.9 through Homebrew.
When I open a core file generated by a GCC-compiled (gcc-4.9 -g xxx.c -o xxx) program, it reports:
→ gdb ./list_test /cores/core.1176
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin14.0.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./list_test...
warning: `/var/folders/r1/3sx4x5k1557g_v5by83k4hg00000gn/T//cchuMtAU.o': can't open to read symbols: No such file or directory.
(no debugging symbols found)...done.
"/cores/core.1176": no core file handler recognizes format
I googled and found someone suggested to use LLDB instead of GDB.
Is is possible to use GDB to debug the core file? And is it because GDB does not support the binary format on Yosemite?
Based on the long GDB developers' discussion thread on this issue, it seems Apple did not merge their changes back to the official GNU mainline, and instead chose to publish the modified source code on their own site. As a result, the Homebrew GDB install (which uses the stock GDB sources) can't load OS X core files.
At this point, I see three choices:
Give in and learn LLDB. There's a GDB to LLDB cheat sheet to help.
Install Apple's custom GDB from MacPorts. I've long forsaken MacPorts, so I can't test it, but if you have MacPorts installed, try the following:
$ sudo port install gdb-apple
$ codesign -s <your_GDB_cert_id> /opt/local/bin/gdb-apple
$ /opt/local/bin/gdb-apple ./list_test /cores/core.1176
Translate MacPorts' GDB patches and build spec into a Homebrew formula. It's theoretically possible, but I don't have the time to do it myself.
Personally, I've opted to just learn LLDB. Apple has moved permanently to LLVM, so it's probably just a matter of time before the old patched GDB stops working with the latest-and-greatest Xcode tools.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I read the article A Bash Code Injection Vulnerability via Specially Crafted Environment Variables (CVE-2014-6271) this morning when I came into work. I have updated Bash on most of my systems that I am responsible for, however, I was asked to upgrade Bash on a couple of FreeBSD servers.
How do I check which version of Bash is running on FreeBSD and how do I patch it to get rid of this exploit?
You can verify the installed version of bash with
pkg info bash
The patched version of bash is already in the ports tree, you can therefore upgrade it like any application.
Once bash has been rebuilt by the package build farm, you can upgrade bash as you would upgrade any package, with
pkg upgrade bash
If you are not familiar with pkg you should read the appropriate chapter in the Handbook.
Important note. At the time of writing it seems that the package is not yet available, so here is the manual procedure to build your own package from sources:
1. Be sure to upgrade your ports tree before trying to upgrade.
2. Move your shell to the ports directory and build
cd /usr/ports/shell/bash
make BATCH=yes build
3. Replace the old batch with
make BATCH=yes deinstall
make BATCH=yes reinstall
From this Ask Ubuntu answer, a command to check this is:
env x='() { :;}; echo vulnerable' bash -c 'echo hello'
If you get vulnerable, it's still vulnerable.
This should work with Bash on any system to test the vulnerability, AFAIK. I've tested on SUSE and Red Hat Linux, but they're not BSDs. To check the version, it should be similar to other systems:
$ echo $BASH_VERSION
4.3.11(1)-release
$ bash --version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
See the FreeBSD forums for more information on downloading/installing the patch. From that link:
Everything before 4.3.25 is vulnerable, 4.3.25 should contain the fix.