Error when using Solidity: "solc: no build results found"

GiorgiButbaiaGiorgiButbaia Member Posts: 1
edited February 2016 in Solidity
I've encountered the following problem during compilation: when executing eth.compile.solidity() method, It throws/outputs the following error:
"solc: no build results found
at InvalidResponse (:-81662:-54)
at send (:-156322:-54)
at solidity (:-133322:-54)
at :1:19"
I'm using geth downloaded from the following link Go master branch/
With solc or solidity compiler separately installed from
How to solve that problem? To be more specific, according to the following github bug report: , this behavior is caused by version mismatch, therefore my question is - where can I find correct version?

Thanks :smile:


  • fultonmfultonm Member Posts: 2
    Also having this problem. Running eth.getCompilers() in geth console returns ["Solidity"], but my Node.js code says
    Error: solc: no build results found
    at Object.module.exports.InvalidResponse
  • mathieumathieu Member Posts: 2
    Same problem here!, any solution so far?
  • socrates399socrates399 Member Posts: 1
    I am having the exact same problem. I am including a trace to see if anyone has ideas. I can't really get the airplane off the ground, so to speak...

    D:\archive\prog\ethereum\Geth-Win64-latest>geth --networkid 54321 --genesis genesis.json --datadir .ethereum_experiment console
    I0506 16:50:03.380287 13936 database.go:71] Alloted 16MB cache to .ethereum_experiment\chaindata
    I0506 16:50:03.414806 13936 database.go:71] Alloted 16MB cache to .ethereum_experiment\dapp
    I0506 16:50:03.431311 13936 backend.go:314] Protocol Versions: [63 62 61], Network Id: 54321
    I0506 16:50:03.431812 13936 genesis.go:89] Genesis block already in chain. Writing canonical number
    I0506 16:50:03.431812 13936 backend.go:326] Successfully wrote genesis block. New genesis hash = bb7de14b2509aeff30096e412ba22e8a9a86c2cd734ba8fd5a0d6f91e5e4d1bf
    I0506 16:50:03.432312 13936 backend.go:362] Blockchain DB Version: 3
    I0506 16:50:03.432312 13936 blockchain.go:214] Last header: #0 [bb7de14b…] TD=1048576
    I0506 16:50:03.432812 13936 blockchain.go:215] Last block: #0 [bb7de14b…] TD=1048576
    I0506 16:50:03.432812 13936 blockchain.go:216] Fast block: #0 [bb7de14b…] TD=1048576
    I0506 16:50:03.435815 13936 cmd.go:115] Starting Geth/v1.3.6/windows/go1.5.1
    I0506 16:50:03.436316 13936 server.go:311] Starting Server
    I0506 16:50:05.495355 13936 nat.go:111] mapped network port udp:30303 -> 30303 (ethereum discovery) using UPNP IGDv1-IP1
    I0506 16:50:05.589213 13936 udp.go:212] Listening, enode://caa503a9c083524e25149ce2363805c9fccddad96003466f8b77e039b0e594266[email protected]
    I0506 16:50:05.589712 13936 server.go:552] Listening on [::]:30303
    I0506 16:50:05.589712 13936 backend.go:526] Server started
    I0506 16:50:05.590712 13936 ipc.go:112] IPC service started (\\.\pipe\geth.ipc)
    I0506 16:50:05.591712 13936 nat.go:111] mapped network port tcp:30303 -> 30303 (ethereum p2p) using UPNP IGDv1-IP1
    instance: Geth/v1.3.6/windows/go1.5.1
    datadir: .ethereum_experiment
    coinbase: 0x4c6dfd596afe1ce8c01cec00e2042f04f159957e
    at block: 0 (Wed, 31 Dec 1969 16:00:00 PST)
    modules: admin:1.0 db:1.0 debug:1.0 eth:1.0 miner:1.0 net:1.0 personal:1.0 shh:1.0 txpool:1.0 web3:1.0
    > web3.eth.getCompilers();
    I0506 16:50:12.735747 13936 solidity.go:114] solc, the solidity compiler commandline interface
    Version: 0.3.0-1f9578ce/Release-Windows/msvc/JIT linked to libethereum-

    path: C:\Program Files\Ethereum\solc.exe
    > source = "contract test { function multiply(uint a) returns(uint d) { return a * 7; } }"
    "contract test { function multiply(uint a) returns(uint d) { return a * 7; } }"
    > contract = eth.compile.solidity(source).test
    solc: no build results found
    at InvalidResponse (:-81662:-45)
    at send (:-156322:-45)
    at solidity (:-133322:-45)
    at :1:12


    Also, my geth version is 1.3.6 and as far as I can infer, geth "picked up" the location of solc.exe from the PATH. I didn't do any explicit linking.

    Any help appreciated

Sign In or Register to comment.