Hi Hoa, Weirdly I get different versions when I run apt show libprotoc-dev vs protoc--version:
$ show libprotoc-dev Package: libprotoc-dev Version: 3.0.0-9.1ubuntu1 Priority: extra Section: libdevel Source: protobuf Origin: Ubuntu Maintainer: Ubuntu Developers <[email protected]> Original-Maintainer: Debian protobuf maintainers <[email protected]> Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 5,257 kB Depends: libprotoc10 (= 3.0.0-9.1ubuntu1), libprotobuf-dev (= 3.0.0-9.1ubuntu1) $ protoc --version libprotoc 3.7.0 I assumed the lastest available protobuf for Linux 18.04 is 3.0.0 so I was surprised to see protoc --version returned 3.7.0. Matthew's workaround worked for me as I just passed a non-existent variable to protobuf. I'm not planning to use the trace simulator so this shouldn't be an issue. Unfortunately, I wasn't able to reproduce the error, maybe it was the way gem5 stores build variables like Matthew said. Now when I run scons I only get a warning: Warning: While checking protoc version: [Errno 2] No such file or directory which I assume means protobuf is still not working. I am also considering upgrade to linux 20.04 and upgrade my packages to see whether that would make a difference. Thanks, Evey ________________________________ From: Hoa Nguyen <[email protected]> Sent: Monday, October 5, 2020 6:38 PM To: gem5 Developer List <[email protected]> Cc: Yijia Liu <[email protected]> Subject: Re: [gem5-dev] Fw: Trouble building 20.1.0.0 EXTERNAL EMAIL: Treat content with extra caution. Hi Evey, Can you please provide more information about the protobuf/protoc version that is installed in the machine, as well as the compiling log? - The protobuf/protoc version can be obtained by running "protoc --version". - The compiling log can be obtained by using the --verbose option of scons. In your case, it would be "scons build/X86/gem5.opt -j 9 --verbose". I'm using libprotoc 3.0.0 and I cannot replicate the error that you have. Regards, Hoa Nguyen On 10/2/20, Yijia Liu via gem5-dev <[email protected]> wrote: > Hello gem5, > > This should be an easy fix, but I've been looking into it for a couple of > hours and couldn't figure out what's off. > > I downloaded v20.1.0.0 and installed all the dependencies. I tried to build > the opt binary with > scons build/X86/gem5.opt -j 9 > > The build failed because of #NDEBUG flag dependent variables weren't in > scope. E.g. > > DPRINTF(EthernetDesc, "Writeback complete curHead %d -> %d\n", > > oldHead, curHead); > > The error was oldHead wasn't in scope, which was defined as: > > #ifndef NDEBUG > > long oldHead = curHead; > > #endif > > In Sconscript, NDEBUG is clearly not defined for opt. I'm not sure where > the build picks up the flag from. > > CPPDEFINES = ['TRACING_ON=1'], > > Can someone please share insight on what might have set the NDEBUG flag, and > how to make sure it's undefined throughout the build? There seem to be a lot > of these conditional definitions so I can't go in and manually change all of > them.d > > Thanks for the help. > > Evey >
_______________________________________________ gem5-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
