08-01-2014
You're compiling it correctly.
How many cores does your system have? The failing assert amounts to, "your system must have a power-of-2 number of cores". So 1, 2, 4, 8, ... cores would be okay -- 6 cores would not.
I don't know very much about OMP at all. I'm not sure whether this is referring to physical cores or just the number OMP is allowed to use in this context.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi! I have downloaded a precompiled gcc package but I'm having problems installing it. It is supposed to install in /usr/local and there is plenty of space left there but during the installation I get the following error message “No space left on device”. Is it some kind of temp folder that is out... (2 Replies)
Discussion started by: alfabetman
2 Replies
2. Programming
I have some crypting functions in object-file - for example,func.o
Main file,from where crypting functions called, named as main.cpp .
"gcc main.cpp -o main func.o" print "undefined reference to ... "
But if I rename main.cpp to main.c and execute
"gcc main.c -o main func.o" - ok. If anybody,... (3 Replies)
Discussion started by: Gigachel
3 Replies
3. Programming
Hi mates,
I am a new comer of this forums.
I have a problem while using function "fread(buffer, size, number, file-pointer)" to read a binary file.
While I used the "fread()" to read the binary file under Solaris UNIX System, it worked very well. But it gets a incorrect result... (6 Replies)
Discussion started by: cquedugdylp
6 Replies
4. Solaris
Hello All,
I have been using String.h with gcc 2.95. Now I have upgraded to gcc 3.4. The support for String.h has been removed and I believe Regex.h support is also not inbuilt. So I tried to build my own library for String.h. I had to use Regex.h and rx.h for a succesful library compilation.... (0 Replies)
Discussion started by: manishs13
0 Replies
5. Programming
Im trying to compile some code that involves using X-Windows based functions (XDisplayName() and XOpenDisplay() ), however each time I run the compiler, Im getting a problem with the linker.
The linker says that both XDisplayName() and XOpenDisplay() are unresolved text symbols. Is there a... (1 Reply)
Discussion started by: JamesGoh
1 Replies
6. Red Hat
I have a host PC and a target system .
Host System -> gcc (3.2) Redhat linux kernel 2.4.20-8 , glibc 2.3
Target System -> gcc (4.1) Fedora linux kernel 2.6.18-1.2798.fc6, glibc 2.5
I would like to build test program that can be run on both systems
---------------------------
... (0 Replies)
Discussion started by: mugdha
0 Replies
7. Solaris
I just installed gcc from the latest package at sunfreeware.com using pkgadd. I write a simple 'Hello World!' program to test it. I try to compile it and I get this error:
rockstar# gcc hello.c -o hello
ld.so.1: gcc: fatal: libiconv.so.2: open failed: No such file or directory
Killed
I... (0 Replies)
Discussion started by: Bradj47
0 Replies
8. Programming
Hi,
I just try to solve the problem why one app failing on box1 and runs ok on box2, they have diff gcc version as I see from /proc/version:
box1:: 3.4.1
box2:: 4.1.2
It's RedHat 64b boxes, so I can not run some <make all> command on box1, do you think I need to upgrade (if I'm using... (1 Reply)
Discussion started by: mario17
1 Replies
9. Programming
Hello together,
I have a question for you. Since a few weeks I am trying to programm
a small bruteforce application in C on Ubuntu 14.04.1 using Code::Blocks
with gcc-4.8.2. My programm is nothing special. It's just for practise,
Without hashing or something like that. For me the focus is on... (11 Replies)
Discussion started by: DaveX
11 Replies
10. Programming
I need a lot of help with c programming.
I have the source code.
Running configure, I got one error message about a missing library.
I downloaded and successfully compiled it in another dir.
Do I throw all the new files into my source dir and run configure again ?
Thanks. (3 Replies)
Discussion started by: drew77
3 Replies
klcc(1) H. Peter Anvin klcc(1)
NAME
klcc - compile a program against klibc
SYNOPSIS
klcc [gcc options] [-o outfile] infile...
DESCRIPTION
klcc is a wrapper around gcc(1) and ld(1) which compiles and links a program against the klibc tiny C library. It supports most gcc
options.
Unlike gcc, klcc compiles with optimization on by default. Furthermore, the optimization level used depends on whether or not -g is speci-
fied, since klcc frequently uses options in the normal case which makes debugging impossible. Therefore, compile without -g, -O, -f or -m
option to use the default optimization level; this will generally result in the smallest binaries. You may want to use -s when linking,
however. Use -O0 to compile without any optimization whatsoever; this may not work depending on the version of gcc used.
-nostdinc
allows to turn off klibc include files.
Use the -shared or -static option to compile for and link against shared or static klibc. Note that shared klibc only supports running
against the exact same klibc binary as the binary was linked with.
In addition to standard gcc options, klcc supports options of the form -print-klibc-option, which prints the corresponding klibc configura-
tion option.
AUTHOR
Written by H. Peter Anvin <hpa@zytor.com>.
COPYRIGHT
Copyright (C) 2005 H. Peter Anvin - All Rights Reserved
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MER-
CHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SEE ALSO
gcc(1)
klibc 1 March 2005 klcc(1)