How do I tell GCC and Clang to look at /usr/local/cuda for include/libs?

up vote
0
down vote

favorite

I have installed CUDA on my system, but seems like its files are not being found by libraries that depend on it. What should I append to my .bashrc in order for both GCC and Clang to look on the directories /usr/local/cuda/include and /usr/local/cuda/lib ?

asked Jan 20 '15 at 4:35

MaiaVictor

1094

add a commentÂ |Â

up vote
0
down vote

favorite

asked Jan 20 '15 at 4:35

MaiaVictor

1094

add a commentÂ |Â

up vote
0
down vote

favorite

asked Jan 20 '15 at 4:35

MaiaVictor

1094

shell gcc

asked Jan 20 '15 at 4:35

MaiaVictor

1094

asked Jan 20 '15 at 4:35

MaiaVictor

1094

asked Jan 20 '15 at 4:35

MaiaVictor

1094

asked Jan 20 '15 at 4:35

MaiaVictor

1094

asked Jan 20 '15 at 4:35

MaiaVictor

1094

add a commentÂ |Â

3 Answers
3

active

oldest

votes

up vote
1
down vote

You have to do it:

gcc -I/path_of_include_files -L/path_of_load_libraries_files

NOTE: you can have some -I and some -L such as :

gcc -I. -L. -I../include -L../libs

answered Jan 20 '15 at 4:43

PersianGulf

6,76543358

add a commentÂ |Â

up vote
1
down vote

Both gcc and clang respect some environment variables that can help achieve what you want. Try adding these to your ~/.bashrc:

export CFLAGS="-I /usr/local/cuda/include"
export LDFLAGS="-L /usr/local/cuda/lib"

However this is usually not done on a global level - different projects need different includes and libs so best to configure the custom include and lib directories per-project in your Makefile or using ./configure.

answered Jan 20 '15 at 4:52

MLu

1,223821

This answer is misleading. CFLAGS and LDFLAGS aren't environment variables related to GCC or Clang. These are make variables merely respected by convention.
â€“Â alecov
11 mins ago

add a commentÂ |Â

up vote
0
down vote

Both the GCC and Clang drivers respect the following environment variables:

export C_INCLUDE_PATH=/usr/local/cuda/include
export CPLUS_INCLUDE_PATH=/usr/local/cuda/include
export LIBRARY_PATH=/usr/local/cuda/lib

Check the manuals.

answered 1 min ago

alecov

1062

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f179986%2fhow-do-i-tell-gcc-and-clang-to-look-at-usr-local-cuda-for-include-libs%23new-answer', 'question_page');

);

Post as a guest

Name

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

up vote
1
down vote

You have to do it:

gcc -I/path_of_include_files -L/path_of_load_libraries_files

NOTE: you can have some -I and some -L such as :

gcc -I. -L. -I../include -L../libs

answered Jan 20 '15 at 4:43

PersianGulf

6,76543358

add a commentÂ |Â

up vote
1
down vote

You have to do it:

gcc -I/path_of_include_files -L/path_of_load_libraries_files

NOTE: you can have some -I and some -L such as :

gcc -I. -L. -I../include -L../libs

answered Jan 20 '15 at 4:43

PersianGulf

6,76543358

add a commentÂ |Â

up vote
1
down vote

You have to do it:

gcc -I/path_of_include_files -L/path_of_load_libraries_files

NOTE: you can have some -I and some -L such as :

gcc -I. -L. -I../include -L../libs

answered Jan 20 '15 at 4:43

PersianGulf

6,76543358

You have to do it:

gcc -I/path_of_include_files -L/path_of_load_libraries_files

NOTE: you can have some -I and some -L such as :

gcc -I. -L. -I../include -L../libs

answered Jan 20 '15 at 4:43

PersianGulf

6,76543358

answered Jan 20 '15 at 4:43

PersianGulf

6,76543358

answered Jan 20 '15 at 4:43

PersianGulf

6,76543358

answered Jan 20 '15 at 4:43

PersianGulf

6,76543358

add a commentÂ |Â

up vote
1
down vote

Both gcc and clang respect some environment variables that can help achieve what you want. Try adding these to your ~/.bashrc:

export CFLAGS="-I /usr/local/cuda/include"
export LDFLAGS="-L /usr/local/cuda/lib"

answered Jan 20 '15 at 4:52

MLu

1,223821

This answer is misleading. CFLAGS and LDFLAGS aren't environment variables related to GCC or Clang. These are make variables merely respected by convention.
â€“Â alecov
11 mins ago

add a commentÂ |Â

up vote
1
down vote

Both gcc and clang respect some environment variables that can help achieve what you want. Try adding these to your ~/.bashrc:

export CFLAGS="-I /usr/local/cuda/include"
export LDFLAGS="-L /usr/local/cuda/lib"

answered Jan 20 '15 at 4:52

MLu

1,223821

This answer is misleading. CFLAGS and LDFLAGS aren't environment variables related to GCC or Clang. These are make variables merely respected by convention.
â€“Â alecov
11 mins ago

add a commentÂ |Â

up vote
1
down vote

Both gcc and clang respect some environment variables that can help achieve what you want. Try adding these to your ~/.bashrc:

export CFLAGS="-I /usr/local/cuda/include"
export LDFLAGS="-L /usr/local/cuda/lib"

answered Jan 20 '15 at 4:52

MLu

1,223821

Both gcc and clang respect some environment variables that can help achieve what you want. Try adding these to your ~/.bashrc:

export CFLAGS="-I /usr/local/cuda/include"
export LDFLAGS="-L /usr/local/cuda/lib"

answered Jan 20 '15 at 4:52

MLu

1,223821

answered Jan 20 '15 at 4:52

MLu

1,223821

answered Jan 20 '15 at 4:52

MLu

1,223821

answered Jan 20 '15 at 4:52

MLu

1,223821

This answer is misleading. CFLAGS and LDFLAGS aren't environment variables related to GCC or Clang. These are make variables merely respected by convention.
â€“Â alecov
11 mins ago

add a commentÂ |Â

This answer is misleading. CFLAGS and LDFLAGS aren't environment variables related to GCC or Clang. These are make variables merely respected by convention.
â€“Â alecov
11 mins ago

This answer is misleading. CFLAGS and LDFLAGS aren't environment variables related to GCC or Clang. These are make variables merely respected by convention.
â€“Â alecov
11 mins ago

add a commentÂ |Â

up vote
0
down vote

Both the GCC and Clang drivers respect the following environment variables:

export C_INCLUDE_PATH=/usr/local/cuda/include
export CPLUS_INCLUDE_PATH=/usr/local/cuda/include
export LIBRARY_PATH=/usr/local/cuda/lib

Check the manuals.

answered 1 min ago

alecov

1062

add a commentÂ |Â

up vote
0
down vote

Both the GCC and Clang drivers respect the following environment variables:

export C_INCLUDE_PATH=/usr/local/cuda/include
export CPLUS_INCLUDE_PATH=/usr/local/cuda/include
export LIBRARY_PATH=/usr/local/cuda/lib

Check the manuals.

answered 1 min ago

alecov

1062

add a commentÂ |Â

up vote
0
down vote

Both the GCC and Clang drivers respect the following environment variables:

export C_INCLUDE_PATH=/usr/local/cuda/include
export CPLUS_INCLUDE_PATH=/usr/local/cuda/include
export LIBRARY_PATH=/usr/local/cuda/lib

Check the manuals.

answered 1 min ago

alecov

1062

Both the GCC and Clang drivers respect the following environment variables:

export C_INCLUDE_PATH=/usr/local/cuda/include
export CPLUS_INCLUDE_PATH=/usr/local/cuda/include
export LIBRARY_PATH=/usr/local/cuda/lib

Check the manuals.

answered 1 min ago

alecov

1062

answered 1 min ago

alecov

1062

answered 1 min ago

alecov

1062

answered 1 min ago

alecov

1062

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

搜尋此網誌

mjhjmtu