gnu

Oracle's pro*C compiler and gnu C (__builtin_va_list, __attribute__, etc)

由 泪湿孤枕 提交于 2019-12-10 18:32:57
问题 I'm compiling a database library with pro C which converts the .ppc library file to a .c file that gcc can use. However, I'm getting a lot of errors in pro C like the following PCC-S-02201, Encountered the symbol "__ attribute__ " when expecting one of the `following` ... , Encountered the symbol "__builtin_va_list" when expecting one of the `following` The missing symbols are from a chain of standard includes like stdio.h and stdlib.h. How do I get around this issue? The library I'm

Makefiles and wildcards

由 送分小仙女□ 提交于 2019-12-10 16:24:59
问题 Alright so this is my current setup for a makefile. There are files which are named public01.c , public02.c , etc. I'm trying to make object files for each of them using the public*.o label with a wildcard. public*.o: public*.c hashtable.h $(CC) $(CFLAGS) -c public*.c public*: public*.o $(CC) -o public* public*.o However, when I try and run the makefile, I get this: make: *** No rule to make target `public*.c', needed by `public*.o'. Stop. I guess it's treating public*.c as a label and not a

GNU Smalltalk 80 Debugger. How to debug smallcode code ? Start Debugger?

由 删除回忆录丶 提交于 2019-12-10 14:32:31
问题 In GNU Smalltalk 80 it is possible to write smalltalk code in your own plain text editor of personal choice. Therefore, it is very important to debug the code. First you save the file as txt File. Then you open the file from the programmers text editor with the "Tools". Here the tool - link C/programme/GNU/gnu smalltalk/gst.exe. The code is running. The debug option is not included. Under these circumstances programming is not possible. There must be a "debug" option to activate. My question

BASH: [ ] (test) behaves unconformly

由 被刻印的时光 ゝ 提交于 2019-12-10 14:08:20
问题 In my bash test has an attitude to exit with status 0 : $ test -n && echo true || echo false -> true while $ test -n "" && echo true || echo false -> false It means when it doesn't receive any argument at all, it assumes nonzero. The case -z works properly instead: $ test -z && echo true || echo false -> true $ test -z "" && echo true || echo false -> true Is this the expected behavior? 回答1: Basically, you are asking test whether the string "-z" is nonempty. It is, so it tells you true . The

configure 参数详解

由 生来就可爱ヽ(ⅴ＜●) 提交于 2019-12-10 14:03:51
linux ./configure 的参数详解 ./configure 该脚本将运行一些测试来猜测一些系统相关的变量并检测你的操作 系统的特殊设置，并且最后在制做树中创建一些文件以记录它找到了什么． 缺省设置将制作服务器和应用程序，还有所有只需要C编译器的客户端程序和接口。 缺省时所有文件都将安装到 /usr/local/pgsql． 你可以通过给出下面 configure 命令行选项中的一个或更多的选项来客户化 制作和安装过程： --prefix=PREFIX 把所有文件装在目录 PREFIX下面而不是 /usr/local/pgsql 里．实际的文件会安装到不同的子目录里；甚至没有一个文件会直接 安装到 PREFIX 目录里． 如果你有特殊需要，你还可以用下面的选项客户化不同的子目录 的位置． --exec-prefix=EXEC-PREFIX 你可以把体系相关的文件安装到一个不同的位置， EXEC-PREFIX，而不是 PREFIX 设置的地方．这样做可以比较方便地在不同主机之间共享体系相关的文件． 如果你省略这些，那么 EXEC-PREFIX 就会被设置为等于 PREFIX 并且体系相关和体系无关的文件都会安装到同一棵目录树下， 这也可能是你想要的． --bindir=DIRECTORY 为可执行程序声明目录，缺省是 EXEC-PREFIX/bin， 通常也就是 /usr

How to use POSIXLY_CORRECT in grep?

由 隐身守侯 提交于 2019-12-10 12:55:22
问题 There is a variable POSIXLY_CORRECT in Bash POSIXLY_CORRECT If this variable is in the environment when Bash starts, the shell enters POSIX mode (see Bash POSIX Mode) before reading the startup files, as if the --posix invocation option had been supplied. If it is set while the shell is running, Bash enables POSIX mode, as if the command set -o posix had been executed. I was told that some options of grep are not POSIX and so I confirmed in The Open Group Base Specifications Issue 6 for grep.

GNU screen command not showing status bar

由 蹲街弑〆低调 提交于 2019-12-10 11:24:17
问题 I am new to GNU screen command. I created .screenrc file in my home directory and added below two lines(source) to display the status bar. caption always caption string "%{= bW}%3n %{y}%t %{-}%= %{m}%H%?%{-} -- %{c}%l%?%{-} -- %D %M %d %{y}%c" but I am not seeing the status bar(after entering into screen mode). When I run source .screenrc , I am getting error "-bash: caption: command not found" . What am I missing here? 回答1: Problem was that, I already started screen and then added the file

Error during making “xz-5.2.1” with MinGW/MSYS

由 会有一股神秘感。 提交于 2019-12-10 11:18:09
问题 I am trying to compile "xz-5.2.1" in MinGW/MSYS environment. I see the following errors: #error UINT32_C is not defined and unsigned int is not 32-bit. error: #error size_t is not 32-bit or 64-bit I am not familiar with MinGW, could anyone shed some light on this? It looks like some macro definition are missing. Some header file missing? ADD 1 The commands I used to compile the xz-5.2.1 are: ./configure ./make The error screenshot: Some background, I am following this link to compile the

How to add colors to every point in gnuplot from inside the point file

由 自作多情 提交于 2019-12-10 10:38:40
问题 Reading this and this answer I understood that changing the colours of every point is possible, but: it has to be defined using set palette model RGB defined () , hence if I want 100 different colours I will have to define all of them the colour of the point is specified just before it is drawn. My question is, is there a way to avoid all of the above, for example modify my data file as follows: x y z R G B 1 2 3 0 255 255 5 6 2 255 0 0 And have the according point drawn with the specified

How to install gnu gettext (>0.15) on windows? So I can produce .po/.mo files in Django

由 霸气de小男生 提交于 2019-12-10 03:54:18
问题 When runing django make messages : ./manage.py makemessages -l pt I get: CommandError: Can't find msguniq. Make sure you have GNU gettext tools 0.15 or newer installed. I tried to install but the last version I find with an Instalation Setup is 0.14. Where may I find a recent version and how do I install it? 回答1: Django removed this explanation from the recent docs and it took me some time to found it so i pasted it here before this old documentation goes offline: Source: Django Docs 1.7
订阅 gnu