I'm trying to compile alsa-driver-RTv5.18 but get date-time error for gcc 4.9.2
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
/home/user/Downloads/Rt-Linux-HDaudio-5.18/alsa-driver-RTv5.18/alsa/acore/info.c:1065:22: error: macro "__DATE__" might prevent reproducible builds [-Werror=date-time]
"Compiled on " __DATE__ " for kernel %s"
^
cc1: some warnings being treated as errors
I've tried to
export CFLAGS="-Wno-error=date-time"
but nothing changed.
date gcc alsa realtek
asked Oct 28 '15 at 16:19
Vyacheslav
15139
add a comment |Â
up vote
3
down vote
favorite
/home/user/Downloads/Rt-Linux-HDaudio-5.18/alsa-driver-RTv5.18/alsa/acore/info.c:1065:22: error: macro "__DATE__" might prevent reproducible builds [-Werror=date-time]
"Compiled on " __DATE__ " for kernel %s"
^
cc1: some warnings being treated as errors
I've tried to
export CFLAGS="-Wno-error=date-time"
but nothing changed.
date gcc alsa realtek
asked Oct 28 '15 at 16:19
Vyacheslav
15139
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
/home/user/Downloads/Rt-Linux-HDaudio-5.18/alsa-driver-RTv5.18/alsa/acore/info.c:1065:22: error: macro "__DATE__" might prevent reproducible builds [-Werror=date-time]
"Compiled on " __DATE__ " for kernel %s"
^
cc1: some warnings being treated as errors
I've tried to
export CFLAGS="-Wno-error=date-time"
but nothing changed.
date gcc alsa realtek
asked Oct 28 '15 at 16:19
Vyacheslav
15139
/home/user/Downloads/Rt-Linux-HDaudio-5.18/alsa-driver-RTv5.18/alsa/acore/info.c:1065:22: error: macro "__DATE__" might prevent reproducible builds [-Werror=date-time]
"Compiled on " __DATE__ " for kernel %s"
^
cc1: some warnings being treated as errors
I've tried to
export CFLAGS="-Wno-error=date-time"
but nothing changed.
date gcc alsa realtek
date gcc alsa realtek
asked Oct 28 '15 at 16:19
Vyacheslav
15139
asked Oct 28 '15 at 16:19
Vyacheslav
15139
edited Oct 28 '15 at 16:27
asked Oct 28 '15 at 16:19
Vyacheslav
15139
asked Oct 28 '15 at 16:19
Vyacheslav
15139
asked Oct 28 '15 at 16:19
Vyacheslav
15139
15139
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
It's hard to judge just by output of gcc, please add compiling invocation command line.
Generally, developers add -Werror gcc command line switch to prevent successful build when there are any warnings triggered during compiling, and "[-Werror=date-time]" is just a name of that triggered warning, not a switch you should find and change.
Try first disabling -Werror by removing it from CFLAGS or grepping it in your source directory recursively: fgrep -lr -- -Werror ., then removing it from each found file.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It's hard to judge just by output of gcc, please add compiling invocation command line.
Generally, developers add -Werror gcc command line switch to prevent successful build when there are any warnings triggered during compiling, and "[-Werror=date-time]" is just a name of that triggered warning, not a switch you should find and change.
Try first disabling -Werror by removing it from CFLAGS or grepping it in your source directory recursively: fgrep -lr -- -Werror ., then removing it from each found file.
add a comment |Â
up vote
0
down vote
It's hard to judge just by output of gcc, please add compiling invocation command line.
Generally, developers add -Werror gcc command line switch to prevent successful build when there are any warnings triggered during compiling, and "[-Werror=date-time]" is just a name of that triggered warning, not a switch you should find and change.
Try first disabling -Werror by removing it from CFLAGS or grepping it in your source directory recursively: fgrep -lr -- -Werror ., then removing it from each found file.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
It's hard to judge just by output of gcc, please add compiling invocation command line.
Generally, developers add -Werror gcc command line switch to prevent successful build when there are any warnings triggered during compiling, and "[-Werror=date-time]" is just a name of that triggered warning, not a switch you should find and change.
Try first disabling -Werror by removing it from CFLAGS or grepping it in your source directory recursively: fgrep -lr -- -Werror ., then removing it from each found file.
It's hard to judge just by output of gcc, please add compiling invocation command line.
Generally, developers add -Werror gcc command line switch to prevent successful build when there are any warnings triggered during compiling, and "[-Werror=date-time]" is just a name of that triggered warning, not a switch you should find and change.
Try first disabling -Werror by removing it from CFLAGS or grepping it in your source directory recursively: fgrep -lr -- -Werror ., then removing it from each found file.
answered Oct 30 '15 at 15:50
user140866
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f239251%2fim-trying-to-compile-alsa-driver-rtv5-18-but-get-date-time-error-for-gcc-4-9-2%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
