search

cryptonotefoundation / cryptonote

CryptoNote protocol implementation. This is the reference repository for starting a new CryptoNote currency. See /src/cryptonote_config.h
https://cryptonote.org/
991 stars 6.1k forks source link

Build not Complete #95

Open abdoutelb opened 6 years ago

abdoutelb commented 6 years ago

When try to build the coin i got stuck into this error ` [ 11%] Building CXX object src/CMakeFiles/Common.dir/Common/Base58.cpp.o /usr/local/cryptonote/src/Common/Base58.cpp: In function ‘uint64_t Tools::Base58::{anonymous}::uint_8be_to_64(const uint8_t, size_t)’: /usr/local/cryptonote/src/Common/Base58.cpp:87:32: error: this statement may fall through [-Werror=implicit-fallthrough=] case 1: res |= data++;


/usr/local/cryptonote/src/Common/Base58.cpp:88:9: note: here
         case 2: res <<= 8; res |= *data++;
         ^~~~
/usr/local/cryptonote/src/Common/Base58.cpp:88:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 2: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/usr/local/cryptonote/src/Common/Base58.cpp:89:9: note: here
         case 3: res <<= 8; res |= *data++;
         ^~~~
/usr/local/cryptonote/src/Common/Base58.cpp:89:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 3: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/usr/local/cryptonote/src/Common/Base58.cpp:90:9: note: here
         case 4: res <<= 8; res |= *data++;
         ^~~~
/usr/local/cryptonote/src/Common/Base58.cpp:90:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 4: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/usr/local/cryptonote/src/Common/Base58.cpp:91:9: note: here
         case 5: res <<= 8; res |= *data++;
         ^~~~
/usr/local/cryptonote/src/Common/Base58.cpp:91:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 5: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/usr/local/cryptonote/src/Common/Base58.cpp:92:9: note: here
         case 6: res <<= 8; res |= *data++;
         ^~~~
/usr/local/cryptonote/src/Common/Base58.cpp:92:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 6: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/usr/local/cryptonote/src/Common/Base58.cpp:93:9: note: here
         case 7: res <<= 8; res |= *data++;
         ^~~~
/usr/local/cryptonote/src/Common/Base58.cpp:93:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 7: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/usr/local/cryptonote/src/Common/Base58.cpp:94:9: note: here
         case 8: res <<= 8; res |= *data; break;
         ^~~~
`
any ideas what this related to ??
HannanSolo commented 6 years ago

Just got the same issue now, :(

ghost commented 6 years ago

Help! I can't get past this error either.

SoraKohaku commented 6 years ago

see my repo. Fixed one

On Dec 19, 2017 7:39 AM, "alexieleon" notifications@github.com wrote:

Help! I can't get past this error either.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-352580896, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tfxsfSkPWBIsJdaDpxJvXtw-qKJ1ks5tBumtgaJpZM4Q8HBT .

ghost commented 6 years ago

Hey FndNur1Labs, I didn't understand your reply.

SoraKohaku commented 6 years ago

My repo fixed bug lol

On Dec 19, 2017 11:14 PM, "alexieleon" notifications@github.com wrote:

Hey FndNur1Labs, I didn't understand your reply.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-352764787, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tZZNTRtuQpiTig_fh2IBB1clFQa5ks5tB8S4gaJpZM4Q8HBT .

ghost commented 6 years ago

Thank you very much. Will get new source code and recompile.

abdoutelb commented 6 years ago

@FndNur1Labs i ran the build for your repo https://github.com/FndNur1Labs/cryptonote but still the same error

SoraKohaku commented 6 years ago

this fixed one https://github.com/FndNur1Labs/WayangCli

On Wed, Dec 20, 2017 at 12:19 AM Abd Elrahman Telb notifications@github.com wrote:

@FndNur1Labs https://github.com/fndnur1labs i ran the build for your repo https://github.com/FndNur1Labs/cryptonote but still the same error

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-352789353, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51td8qr31SLE7PNvVKcsxvzKc1MiEfks5tB9QTgaJpZM4Q8HBT .

erikszewczyk commented 6 years ago

I'm getting the same issue on two separate servers, both running Ubuntu 17.10 https://github.com/erikszewczyk/ErikCoin

@FndNur1Labs I tried your Fork as well and I'm getting the same error

SoraKohaku commented 6 years ago

what kind error?

On Dec 20, 2017 4:53 AM, "Erik" notifications@github.com wrote:

I'm getting the same issue on two separate servers, both running Ubuntu 17.10 https://github.com/erikszewczyk/ErikCoin

@FndNur1Labs https://github.com/fndnur1labs I tried your Fork as well and I'm getting the same error

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-352868278, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tSVx7rHHE253D1BzPwPMQnA5txHlks5tCBQ_gaJpZM4Q8HBT .

erikszewczyk commented 6 years ago

The same build errors on Base58 as the OP. Here is using your WayangCli, I get the same error using my own fork: `[ 11%] Building CXX object src/CMakeFiles/Common.dir/Common/Base58.cpp.o /home/erik/WayangCli/src/Common/Base58.cpp: In function ‘uint64_t Tools::Base58::{anonymous}::uint_8be_to_64(const uint8_t, size_t)’: /home/erik/WayangCli/src/Common/Base58.cpp:90:32: error: this statement may fall through [-Werror=implicit-fallthrough=] case 1: res |= data++;


/home/erik/WayangCli/src/Common/Base58.cpp:91:9: note: here
         case 2: res <<= 8; res |= *data++;
         ^~~~
/home/erik/WayangCli/src/Common/Base58.cpp:91:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 2: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/home/erik/WayangCli/src/Common/Base58.cpp:92:9: note: here
         case 3: res <<= 8; res |= *data++;
         ^~~~
/home/erik/WayangCli/src/Common/Base58.cpp:92:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 3: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/home/erik/WayangCli/src/Common/Base58.cpp:93:9: note: here
         case 4: res <<= 8; res |= *data++;
         ^~~~
/home/erik/WayangCli/src/Common/Base58.cpp:93:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 4: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/home/erik/WayangCli/src/Common/Base58.cpp:94:9: note: here
         case 5: res <<= 8; res |= *data++;
         ^~~~
/home/erik/WayangCli/src/Common/Base58.cpp:94:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 5: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/home/erik/WayangCli/src/Common/Base58.cpp:95:9: note: here
         case 6: res <<= 8; res |= *data++;
         ^~~~
/home/erik/WayangCli/src/Common/Base58.cpp:95:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 6: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/home/erik/WayangCli/src/Common/Base58.cpp:96:9: note: here
         case 7: res <<= 8; res |= *data++;
         ^~~~
/home/erik/WayangCli/src/Common/Base58.cpp:96:32: error: this statement may fall through [-Werror=implicit-fallthrough=]
         case 7: res <<= 8; res |= *data++;
                            ~~~~^~~~~~~~~~
/home/erik/WayangCli/src/Common/Base58.cpp:97:9: note: here
         case 8: res <<= 8; res |= *data; break;
         ^~~~
cc1plus: all warnings being treated as errors
src/CMakeFiles/Common.dir/build.make:62: recipe for target 'src/CMakeFiles/Common.dir/Common/Base58.cpp.o' failed
make[3]: *** [src/CMakeFiles/Common.dir/Common/Base58.cpp.o] Error 1
make[3]: Leaving directory '/home/erik/WayangCli/build/release'
CMakeFiles/Makefile2:515: recipe for target 'src/CMakeFiles/Common.dir/all' failed
make[2]: *** [src/CMakeFiles/Common.dir/all] Error 2
make[2]: Leaving directory '/home/erik/WayangCli/build/release'
Makefile:94: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/erik/WayangCli/build/release'
Makefile:20: recipe for target 'build-release' failed
make: *** [build-release] Error 2`
SoraKohaku commented 6 years ago

apt install build-essential libqt4-dev qt5-qmake cmake qttools5-dev libqt5webkit5-dev qttools5-dev-tools qt5-default python-sphinx texlive-latex-base inotify-tools openssl libssl-dev libdb++-dev libminiupnpc-dev git sqlite3 libsqlite3-dev g++ libpng-dev git g++ gedit python gcc make libbz2-dev libdb-dev libssl-dev openssl libreadline-dev autoconf libtool git libleveldb-dev libblkid-dev e2fslibs-dev libboost-all-dev libaudit-dev automake nano qtbase5-dev qt4-dev-tools libqt4-core libqt4-gui libqt5-core libqt5-gui

try this conf

On Dec 21, 2017 2:51 AM, "Erik" notifications@github.com wrote:

[ 11%] Building CXX object src/CMakeFiles/Common.dir/Common/Base58.cpp.o /home/erik/WayangCli/src/Common/Base58.cpp: In function ‘uint64_t Tools::Base58::{anonymous}::uint_8be_to_64(const uint8_t, size_t)’: /home/erik/WayangCli/src/Common/Base58.cpp:90:32: error: this statement may fall through [-Werror=implicit-fallthrough=] case 1: res |= data++;


here case 2: res <<= 8; res |= *data++; ^~~~ /home/erik/WayangCli/src/Common/Base58.cpp:91:32:
error: this statement may fall through [-Werror=implicit-fallthrough=]
case 2: res <<= 8; res |= *data++; ~~~~^~~~~~~~~~ /home/erik/WayangCli/src/Common/Base58.cpp:92:9:
note: here case 3: res <<= 8; res |= *data++; ^~~~ /home/erik/WayangCli/src/Common/Base58.cpp:92:32:
error: this statement may fall through [-Werror=implicit-fallthrough=]
case 3: res <<= 8; res |= *data++; ~~~~^~~~~~~~~~ /home/erik/WayangCli/src/Common/Base58.cpp:93:9:
note: here case 4: res <<= 8; res |= *data++; ^~~~ /home/erik/WayangCli/src/Common/Base58.cpp:93:32:
error: this statement may fall through [-Werror=implicit-fallthrough=]
case 4: res <<= 8; res |= *data++; ~~~~^~~~~~~~~~ /home/erik/WayangCli/src/Common/Base58.cpp:94:9:
note: here case 5: res <<= 8; res |= *data++; ^~~~ /home/erik/WayangCli/src/Common/Base58.cpp:94:32:
error: this statement may fall through [-Werror=implicit-fallthrough=]
case 5: res <<= 8; res |= *data++; ~~~~^~~~~~~~~~ /home/erik/WayangCli/src/Common/Base58.cpp:95:9:
note: here case 6: res <<= 8; res |= *data++; ^~~~ /home/erik/WayangCli/src/Common/Base58.cpp:95:32:
error: this statement may fall through [-Werror=implicit-fallthrough=]
case 6: res <<= 8; res |= *data++; ~~~~^~~~~~~~~~ /home/erik/WayangCli/src/Common/Base58.cpp:96:9:
note: here case 7: res <<= 8; res |= *data++; ^~~~ /home/erik/WayangCli/src/Common/Base58.cpp:96:32:
error: this statement may fall through [-Werror=implicit-fallthrough=]
case 7: res <<= 8; res |= *data++; ~~~~^~~~~~~~~~ /home/erik/WayangCli/src/Common/Base58.cpp:97:9:
note: here case 8: res <<= 8; res |= *data; break; ^~~~ cc1plus: all
warnings being treated as errors src/CMakeFiles/Common.dir/build.make:62:
recipe for target 'src/CMakeFiles/Common.dir/Common/Base58.cpp.o' failed
make[3]: *** [src/CMakeFiles/Common.dir/Common/Base58.cpp.o] Error 1
make[3]: Leaving directory '/home/erik/WayangCli/build/release'
CMakeFiles/Makefile2:515: recipe for target 'src/CMakeFiles/Common.dir/all'
failed make[2]: *** [src/CMakeFiles/Common.dir/all] Error 2 make[2]:
Leaving directory '/home/erik/WayangCli/build/release' Makefile:94:
recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving
directory '/home/erik/WayangCli/build/release' Makefile:20: recipe for
target 'build-release' failed make: *** [build-release] Error 2

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-353135145>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK51tWYtmQT2NqVa_7eHx0CQ0pI3TQBvks5tCUktgaJpZM4Q8HBT>
.
erikszewczyk commented 6 years ago

Thanks for the suggestion - the only packages I did not have installed on my servers was libqt5. Note that for Ubuntu it would be libqt5core5a and libqt5gui5 (and libqtcore4 libqtgui4).

That said after installing libqt5 I'm still getting the same failure on the Base58.cpp build as posted above (I tried against both my fork as well as yours, just in case).

nidscom commented 6 years ago

I tried to compile on ubuntu 16.04 and ended with same error. I downgrade to Ubuntu 14.04, now working as it should.

SoraKohaku commented 6 years ago

since i used debian 8 work. even in GUI is now did have problem too

i update cmake for now and everything there....

try git pull my repo

On Dec 21, 2017 12:10 PM, "nidscom.io" notifications@github.com wrote:

I tried to compile on ubuntu 16.04 and ended with same error. I downgrade to Ubuntu 14.04, now working as it should.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-353246690, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tXDXL_ZpaADuSJfbmrb32OaDM709ks5tCcw-gaJpZM4Q8HBT .

erikszewczyk commented 6 years ago

Thanks for trying to update the cmake @FndNur1Labs , unfortunately I'm still stuck at the same error.

Given that others have been able to make this work correctly after downgrading distributions I think I'm going to try that next.

Erik

SoraKohaku commented 6 years ago

even i used debian 8

On Dec 23, 2017 8:41 AM, "Erik" notifications@github.com wrote:

Thanks for trying to update the cmake @FndNur1Labs https://github.com/fndnur1labs , unfortunately I'm still stuck at the same error.

Given that others have been able to make this work correctly after downgrading distributions I think I'm going to try that next.

Erik

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-353691212, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tYVYKjimBARPuTl91BlylctLyjYLks5tDD4kgaJpZM4Q8HBT .

erikszewczyk commented 6 years ago

FYI all, I did manage to get this working after downgrading to Ubuntu 16.4. If you run into similar problems suggest you try the same.

SoraKohaku commented 6 years ago

yep im update again with premine system and update bcn config~

On Dec 23, 2017 3:24 PM, "Erik" notifications@github.com wrote:

FYI all, I did manage to get this working after downgrading to Ubuntu 16.4. If you run into similar problems suggest you try the same.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-353709936, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tQKFpJYBAjP3IK0AmRDKFN2HdpwOks5tDJyggaJpZM4Q8HBT .

jared201 commented 6 years ago

can anyone do a fix for Ubuntu 17.04?

Vanclief commented 6 years ago

Having exactly same error on Arch linux. Remove -Werror from src/CMakeList

SoraKohaku commented 6 years ago

boost too old sometimes when install 1.66 libboost fail~

On Jan 11, 2018 11:02 AM, "Franco Valencia" notifications@github.com wrote:

Having exactly same error on Arch linux. Probably related to version of gcc, cmake or Boost?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-356800615, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tTRo7sTiUt_sywTesNrP6Ni8ByYBks5tJWvHgaJpZM4Q8HBT .

intrcomp commented 6 years ago

I wished I read this thread prior installing my system, I was able to fix the Base58 error not sure how but now I have an error on: upnpc.c in function 'main' an error directive output nay be truncated writing 1 and 10 bytes into a region of size 6 [-Werror=format-truncation=] snprintf(index, 6, "%d", i);

is marking "%d" as an error

I'm on Ubuntu 17.1

SoraKohaku commented 6 years ago

try my repo old boost. will try boost new and configure it~

On Jan 12, 2018 12:33 PM, "intrcomp" notifications@github.com wrote:

I wished I read this thread prior installing my system, I was able to fix the Base58 error not sure how but now I have an error on: upnpc.c in function 'main' an error directive output nay be truncated writing 1 and 10 bytes into a region of size 6 [-Werror=format-truncation=] snprintf(index, 6, "%d", i);

is marking "%d" as an error

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-357134137, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51ta_V0G_o3-Ixjpsn5qpElmInNr2Pks5tJtKNgaJpZM4Q8HBT .

AlphaCryptoKid commented 6 years ago

Hey guys, I was having this problem as well. I think the problem is a bug in the most recent GCC. GCC 7.2 to be exact, the way i fixed it was by removing GCC 7.2 and installing GCC 6.3 then it worked like a charm.

//Remove GCC 7.2 sudo apt-get purge gcc-7.2

//Install GCC 6.3 sudo apt-get update sudo apt-get install build-essential software-properties-common -y sudo add-apt-repository ppa:ubuntu-toolchain-r/test -y sudo apt-get update sudo apt-get install gcc-snapshot -y sudo apt-get update sudo apt-get install gcc-6 g++-6 -y sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-6 60 --slave /usr/bin/g++ g++ /usr/bin/g++-6

// // Check GCC Installation Verification gcc -v

This worked for me I hope it works for you.

+Edit You can also verify [gcc-v] what GCC version you have in the beginning. If you dont have GCC 7.2 skip its removal and just install GCC 6.3 then verify that it install properly.

SoraKohaku commented 6 years ago

thank for contribute i put on some docs on my web nur1labs.net so people can easy used. since gcc7 have bug self~

On Jan 30, 2018 3:04 PM, "AlphaCryptoKid" notifications@github.com wrote:

Hey guys, I was having this problem as well. I think the problem is a bug in the most recent GCC. GCC 7.2 to be exact, the way i fixed it was by removing GCC 7.2 and installing GCC 6.3 then it worked like a charm.

//Remove GCC 7.2 sudo apt-get purge gcc-7.2

//Install GCC 6.3 sudo apt-get update sudo apt-get install build-essential software-properties-common -y sudo add-apt-repository ppa:ubuntu-toolchain-r/test -y sudo apt-get update sudo apt-get install gcc-snapshot -y sudo apt-get update sudo apt-get install gcc-6 g++-6 -y sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-6 60 --slave /usr/bin/g++ g++ /usr/bin/g++-6

// // Check GCC Installation Verification gcc -v

This worked for me I hope it works for you.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-361486637, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tS8hvBDx11XhopKgQZw1L2B-tXAKks5tPrEEgaJpZM4Q8HBT .

rainmanp7 commented 6 years ago

rainmanp7 To fix the fall through bug on this one.

    uint64_t res = 0;
    switch (9 - size)
    {
    case 1:            res |= *data++; /* FALLTHRU */
    case 2: res <<= 8; res |= *data++; /* FALLTHRU */
    case 3: res <<= 8; res |= *data++; /* FALLTHRU */
    case 4: res <<= 8; res |= *data++; /* FALLTHRU */
    case 5: res <<= 8; res |= *data++; /* FALLTHRU */
    case 6: res <<= 8; res |= *data++; /* FALLTHRU */
    case 7: res <<= 8; res |= *data++; /* FALLTHRU */
    case 8: res <<= 8; res |= *data; break;
    default: assert(false);
    }

    return res;
SoraKohaku commented 6 years ago

Where?on rpcserver.cpp?

On Feb 1, 2018 12:11 PM, "PHFirecoin" notifications@github.com wrote:

rainmanp7 To fix the fall through bug on this one.

uint64_t res = 0;
switch (9 - size)
{
case 1:            res |= *data++; /* FALLTHRU */
case 2: res <<= 8; res |= *data++; /* FALLTHRU */
case 3: res <<= 8; res |= *data++; /* FALLTHRU */
case 4: res <<= 8; res |= *data++; /* FALLTHRU */
case 5: res <<= 8; res |= *data++; /* FALLTHRU */
case 6: res <<= 8; res |= *data++; /* FALLTHRU */
case 7: res <<= 8; res |= *data++; /* FALLTHRU */
case 8: res <<= 8; res |= *data; break;
default: assert(false);
}

return res;

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-362145048, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tUdxNvsPTG_Vz1uhs9T3t5TdHtf9ks5tQStJgaJpZM4Q8HBT .

rainmanp7 commented 6 years ago

Src/common/Base58.cpp

On Feb 1, 2018 1:13 PM, "Founder Nur1Labs" notifications@github.com wrote:

Where?on rpcserver.cpp?

On Feb 1, 2018 12:11 PM, "PHFirecoin" notifications@github.com wrote:

rainmanp7 To fix the fall through bug on this one.

uint64_t res = 0; switch (9 - size) { case 1: res |= data++; / FALLTHRU / case 2: res <<= 8; res |= data++; / FALLTHRU / case 3: res <<= 8; res |= data++; / FALLTHRU / case 4: res <<= 8; res |= data++; / FALLTHRU / case 5: res <<= 8; res |= data++; / FALLTHRU / case 6: res <<= 8; res |= data++; / FALLTHRU / case 7: res <<= 8; res |= data++; / FALLTHRU / case 8: res <<= 8; res |= data; break; default: assert(false); }

return res;

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95# issuecomment-362145048, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tUdxNvsPTG_ Vz1uhs9T3t5TdHtf9ks5tQStJgaJpZM4Q8HBT .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-362160741, or mute the thread https://github.com/notifications/unsubscribe-auth/Afp77ZCqZE15PmAfcaQBh4mBNiUIAYowks5tQUgGgaJpZM4Q8HBT .

SoraKohaku commented 6 years ago

that already fixed. just stuck on blockexplorer bugs~ Gcc7

On Feb 1, 2018 2:30 PM, "PHFirecoin" notifications@github.com wrote:

Src/common/Base58.cpp

On Feb 1, 2018 1:13 PM, "Founder Nur1Labs" notifications@github.com wrote:

Where?on rpcserver.cpp?

On Feb 1, 2018 12:11 PM, "PHFirecoin" notifications@github.com wrote:

rainmanp7 To fix the fall through bug on this one.

uint64_t res = 0; switch (9 - size) { case 1: res |= data++; / FALLTHRU / case 2: res <<= 8; res |= data++; / FALLTHRU / case 3: res <<= 8; res |= data++; / FALLTHRU / case 4: res <<= 8; res |= data++; / FALLTHRU / case 5: res <<= 8; res |= data++; / FALLTHRU / case 6: res <<= 8; res |= data++; / FALLTHRU / case 7: res <<= 8; res |= data++; / FALLTHRU / case 8: res <<= 8; res |= data; break; default: assert(false); }

return res;

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95# issuecomment-362145048, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tUdxNvsPTG_ Vz1uhs9T3t5TdHtf9ks5tQStJgaJpZM4Q8HBT .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95# issuecomment-362160741, or mute the thread https://github.com/notifications/unsubscribe-auth/ Afp77ZCqZE15PmAfcaQBh4mBNiUIAYowks5tQUgGgaJpZM4Q8HBT .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-362163115, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tb-2ChJwWoDDI0RwPs5ZRJCTkQK4ks5tQUv-gaJpZM4Q8HBT .

jojapoppa commented 5 years ago

I would not recommend downgrading the C++ version support, nor compiling under an old version of the operating system. I would instead recommend that we use the explicit fall-through syntax in C++;

Does this alternative method work for everyone?

    uint64_t res = 0;
    switch (9 - size)
    {
    case 1:            res |= *data++; [[fallthrough]];
    case 2: res <<= 8; res |= *data++; [[fallthrough]];
    case 3: res <<= 8; res |= *data++; [[fallthrough]];
    case 4: res <<= 8; res |= *data++; [[fallthrough]];
    case 5: res <<= 8; res |= *data++; [[fallthrough]];
    case 6: res <<= 8; res |= *data++; [[fallthrough]];
    case 7: res <<= 8; res |= *data++; [[fallthrough]];
    case 8: res <<= 8; res |= *data; break;
    default: assert(false);
    }

    return res;
CryptoPalestine commented 5 years ago

I'm recieving this problem what seems the problem, Please Help asap

/home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp: In destructor ‘System::TcpConnection::~TcpConnection()’: /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp:35:9: warning: unused variable ‘result’ [-Wunused-variable] int result = close(connection); ^~ /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp: In member function ‘size_t System::TcpConnection::read(uint8_t, size_t)’: /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp:71:26: error: logical ‘and’ of equal expressions [-Werror=logical-op] if (errno != EAGAIN && errno != EWOULDBLOCK) { ^ /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp: In member function ‘std::size_t System::TcpConnection::write(const uint8_t, size_t)’: /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp:167:26: error: logical ‘and’ of equal expressions [-Werror=logical-op] if (errno != EAGAIN && errno != EWOULDBLOCK) { ^ cc1plus: all warnings being treated as errors src/CMakeFiles/System.dir/build.make:326: recipe for target 'src/CMakeFiles/System.dir/Platform/Linux/System/TcpConnection.cpp.o' failed make[2]: [src/CMakeFiles/System.dir/Platform/Linux/System/TcpConnection.cpp.o] Error 1 CMakeFiles/Makefile2:600: recipe for target 'src/CMakeFiles/System.dir/all' failed make[1]: [src/CMakeFiles/System.dir/all] Error 2 Makefile:94: recipe for target 'all' failed make: *** [all] Error 2

SoraKohaku commented 5 years ago

used 1 question don't double question~

On Sat, Sep 15, 2018 at 5:39 PM CryptoPalestine notifications@github.com wrote:

I'm recieving this problem what seems the problem, Please Help asap

/home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp: In destructor ‘System::TcpConnection::TcpConnection()’: /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp:35:9: warning: unused variable ‘result’ [-Wunused-variable] int result = close(connection); ^ /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp: In member function ‘size_t System::TcpConnection::read(uint8_t, size_t)’: /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp:71:26: error: logical ‘and’ of equal expressions [-Werror=logical-op] if (errno != EAGAIN && errno != EWOULDBLOCK) { ^ /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp: In member function ‘std::size_t System::TcpConnection::write(const uint8_t, size_t)’: /home/dirhamzayed/DirhamZayed/src/Platform/Linux/System/TcpConnection.cpp:167:26: error: logical ‘and’ of equal expressions [-Werror=logical-op] if (errno != EAGAIN && errno != EWOULDBLOCK) { ^ cc1plus: all warnings being treated as errors src/CMakeFiles/System.dir/build.make:326: recipe for target 'src/CMakeFiles/System.dir/Platform/Linux/System/TcpConnection.cpp.o' failed make[2]: [src/CMakeFiles/System.dir/Platform/Linux/System/TcpConnection.cpp.o] Error 1 CMakeFiles/Makefile2:600: recipe for target 'src/CMakeFiles/System.dir/all' failed make[1]: [src/CMakeFiles/System.dir/all] Error 2 Makefile:94: recipe for target 'all' failed make: *** [all] Error 2

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cryptonotefoundation/cryptonote/issues/95#issuecomment-421541597, or mute the thread https://github.com/notifications/unsubscribe-auth/AK51tYwCsdSzUIYlWRfj-uwrLZNdZEfsks5ubLzXgaJpZM4Q8HBT .

-- Nur1Labs©2010

Site Info -> Here https://nur1labs.com/

AriA : amf8a9ondahtxisA3GWLK8jvhhjnNBR9bk

BLockChainsB commented 4 years ago

Hi gang first my name is Marc-Andre Robert alias Picsou or McDuck the Hashing-b briefly I also encountered this little problem and I tried 144 different code before reaching a functional one and finally telling myself that it should write "make -j" as the first command briefly I very much hope that it will be useful for you brief on my side I have more evolved in half a day when 4 days none stop, GOOD LUCK every body from Hashing-b for Bitcuty Coin Cryptonote Blockchain, Hashing-b and Cryptonote is solid I will add as many tools as possible for the creation of a coin and or a Cryptonote token of course if you see Bitcuty in the Cryptonote team use it as coin for your token peace my friend !!!

BLockChainsB commented 4 years ago
short here are the make options ("https://www.computerhope.com/unix/umake.htm") -b, -m These options are ignored, but included for compatibility with other versions of make.
-B, --always-make Unconditionally make all targets.
-C dir, --directory=dir Change to directory dir before reading the makefiles or doing anything else. If multiple -C options are specified, each is interpreted relative to the previous one: -C / -C etc is equivalent to -C /etc. This is typically used with recursive invocations of make.
-d Print debugging information in addition to normal processing. The debugging information says which files are being considered for remaking, which file-times are being compared and with what results, which files actually need to be remade, which implicit rules are considered and that are applied; everything interesting about how make decides what to do.
--debug[=FLAGS] Print debugging information in addition to normal processing. If the FLAGS are omitted, then the behavior is the same as if -d was specified. FLAGS may be a for all debugging output (same as using -d), b for basic debugging, v for more verbose basic debugging, i for showing implicit rules, j for details on invocation of commands, and m for debugging while remaking makefiles.
-e, --environment-overrides Give variables taken from the environment precedence over variables from makefiles.
-f file, --file=file, --makefile=file Use file as a makefile.
-i, --ignore-errors Ignore all errors in commands executed to remake files.
-I dir, --include-dir=dir Specifies a directory dir to search for included makefiles. If several -I options are used to specify several directories, the directories are searched in the order specified. Unlike the arguments to other flags of make, directories given with -I flags may come directly after the flag: -Idir is allowed, as well as -I dir. This syntax is allowed for compatibility with the C preprocessor's -I flag.
-j [jobs], --jobs[=jobs] Specifies the number of jobs (commands) to run simultaneously. If there is more than one -j option, the last one is effective. If the -j option is given without an argument, make will not limit the number of jobs that can run simultaneously.
-k, --keep-going Continue as much as possible after an error. While the target that failed (and those that depend on it) cannot be remade, the other dependencies of these targets can be processed all the same.
-l [load], --load-average[=load] Specifies that no new jobs (commands) should be started if there are others jobs running and the load average is at least load (a floating-point number). With no argument, removes a previous load limit.
-L, --check-symlink-times Use whichever is the latest modification time between symlinks and target.
-n, --just-print, --dry-run, --recon Print the commands that would be executed, but do not execute them.
-o file, --old-file=file, --assume-old=file Do not remake the file file even if it is older than its dependencies, and do not remake anything on account of changes in file. Essentially the file is treated as very old and its rules are ignored.
-p, --print-data-base Print the database (rules and variable values) that results from reading the makefiles; then execute as usual or as otherwise specified. This also prints the version information given by the -v switch (see below). To print the database without trying to remake any files, use make -p -f/dev/null.
-q, --question "Question mode." Do not run any commands, or print anything; just return an exit status that is zero if the specified targets are already up to date, nonzero otherwise.
-r, --no-builtin-rules Eliminate use of the built-in implicit rules. Also, clear out the default list of suffixes for suffix rules.
-R, --no-builtin-variables Don't define any built-in variables.
-s, --silent, --quiet Silent operation; do not print the commands as they are executed.
-S, --no-keep-going, --stop Cancel the effect of the -k option. This is never necessary except in a recursive make where -k might be inherited from the top-level make via MAKEFLAGS or if you set -k in MAKEFLAGS in your environment.
-t, --touch Touch files (mark them up to date without really changing them) instead of running their commands. This is used to pretend that the commands were done, to fool future invocations of make.
-v, --version Print the version of make; also a Copyright, a list of authors and a notice that there is no warranty.
-w, --print-directory Print a message containing the working directory before and after other processing. This may be useful for tracking down errors from complicated nests of recursive make commands.
--no-print-directory Turn off -w, even if it was turned on implicitly.
-W file, --what-if=file, --new-file=file, --assume-new=file Pretend that the target file has just been modified. When used with the -n flag, this shows you what would happen if you were to modify that file. Without -n, it is almost the same as running a touch command on the given file before running make, except that the modification time is changed only internally within make.
--warn-undefined-variables Warn when an undefined variable is referenced.
BLockChainsB commented 4 years ago

PEACE AND ONE LOVE FOR GITHUB AND CRYPTONOTE AND UBUNTU AND HASHING-B FINANCIAL SOCIETY DEPARTMENT BLOCKCHAIN

BLockChainsB commented 4 years ago

for me the best is make -j2 -e --include-dir=include/CryptoNoteConfig.h test-release test-debug build-test build-release build-debug -k -i ${CORRECTION} ${CONFIGURE_FILE} ${SET} ${BUILD} ${DEBUG} & make -B & .env.installed: touch $@ install: .env.installed & make set Bitcuty/* set Peace your friend Picsou(McDuck) the Hashing-b Financial Society Department Blockchain for Bitcuty Coin Cryptonote Blockchain