Why this happen when I want to install ns3.4 allinone?

[lizha...@gmail.com]

File "/home/lee/桌面/ns-allinone-3.4/util.py", line 24, in run_command
raise CommandError("Command %r exited with code %i" % (argv,
retval))
util.CommandError: Command ['python', 'scons.py', 'linux-2.6.18']
exited with code 2


I just type in "./build.py". And then after a few lines of compile
output messages, this line of message appeared and the build process
stopped then. Why would this happen? How can I fix it?

[Gustavo Carneiro]

2009/4/2 lizha...@gmail.com <lizha...@gmail.com>

Network Simulation Cradle is not compiling for some reason.  You'd have to copy-paste the compilation error here.

If you want to build without nsc for now, you can just hack the .config file and remove the <nsc ..../> line.

--
Gustavo J. A. M. Carneiro
INESC Porto, Telecommunications and Multimedia Unit
"The universe is always one step beyond logic." -- Frank Herbert

[lizha...@gmail.com]

ok, here are all the output messages after starting to build:

==========================================================================
# Build NSC
Entering directory `nsc-0.5.0'
=> python scons.py linux-2.6.18
scons: Reading SConscript files ...
Checking target architecure...(cached) x86
AttributeError: SConsEnvironment instance has no attribute 'CFile':
File "/home/lee/.local/share/Trash/files/ns-allinone-3.4/nsc-0.5.0/
SConstruct", line 139:
SConscript('globaliser/SConscript')
File "/home/lee/桌面/ns-allinone-3.4/nsc-0.5.0/scons-local-1.0.1/SCons/
Script/SConscript.py", line 596:
return apply(method, args, kw)
File "/home/lee/桌面/ns-allinone-3.4/nsc-0.5.0/scons-local-1.0.1/SCons/
Script/SConscript.py", line 533:
return apply(_SConscript, [self.fs,] + files, subst_kw)
File "/home/lee/桌面/ns-allinone-3.4/nsc-0.5.0/scons-local-1.0.1/SCons/
Script/SConscript.py", line 256:
exec _file_ in call_stack[-1].globals
File "/home/lee/.local/share/Trash/files/ns-allinone-3.4/nsc-0.5.0/
globaliser/SConscript", line 18:
env.CFile(target = 'lexer.lex.cc', source = 'lexer.l')
Traceback (most recent call last):
File "./build.py", line 106, in <module>
sys.exit(main(sys.argv))
File "./build.py", line 85, in main
build_nsc()
File "./build.py", line 14, in build_nsc
run_command(['python', 'scons.py', kernel])

File "/home/lee/桌面/ns-allinone-3.4/util.py", line 24, in run_command
raise CommandError("Command %r exited with code %i" % (argv,
retval))
util.CommandError: Command ['python', 'scons.py', 'linux-2.6.18']
exited with code 2

===========================================================================

just a few lines of output, and it stopped. By the way, what is nsc?
What is it used for?

On 4月2日, 下午9时20分, Gustavo Carneiro <gjcarne...@gmail.com> wrote:
> 2009/4/2 lizhaowe...@gmail.com <lizhaowe...@gmail.com>

[Gustavo Carneiro]

2009/4/2 lizha...@gmail.com <lizha...@gmail.com>

ok, here are all the output messages after starting to build:

The error is in SCons shipped by NSC:

AttributeError: SConsEnvironment instance has no attribute 'CFile':
 

I am not sure how to deal with this.  NSC is a third party software that ns-3 just happens to ship in the tarball.

NSC is used to allow NS-3 to use a linux kernel TCP implementation in simulations.  It is completely optional.

[lizha...@gmail.com]

Thank you very much! After I remove the NSC building part from the
build.py , the building process went through succefully!

> "The universe is always one step beyond logic." -- Frank Herbert- Hide quoted text -
>
> - Show quoted text -

[Björn Lichtblau]

Hi,

it is not really an error in SCons, but this error message just could
need improvment.
I had the same error and NSC compilation worked for me on a fresh Ubuntu
after i installed bison and/or flex packages,
which SCons apparently needs.

Regards

[lizha...@gmail.com]

I'm using ubuntu, too. And my version is 8.04. As Gustavo Carneiro
said in his reply, the NSC is related to the TCP implemention of Linux
kernel, maybe there are some other libs needed for this NSC and the
ubuntu doesn't provide in its install package.

On Apr 3, 5:48 pm, Björn Lichtblau <licht...@informatik.hu-berlin.de>
wrote:

> >> - Show quoted text -- Hide quoted text -

[Raj Bhattacharjea]

http://www.nsnam.org/wiki/index.php/Installation#Prerequisites

In the section about NSC, it mentions that it requires flex and
bison. This is something we didn't consider to document or handle
with the new build environment changes. So, it appears your options
are to either install flex and bison, or to hack the .config file.

On Apr 3, 7:43 am, "lizhaowe...@gmail.com" <lizhaowe...@gmail.com>
wrote:

[Raj Bhattacharjea]

I tried to document this in the wiki:

http://www.nsnam.org/wiki/index.php/Troubleshooting#Scons_NSC_error

More generally, Gustavo, build.py needs a way to programatically
disable features, and shouldn't stop the build of ns-3 if optional
components fail first.

On Apr 3, 11:17 am, Raj Bhattacharjea <rbhattachar...@gmail.com>
wrote:

[Gustavo Carneiro]

2009/4/3 Raj Bhattacharjea <rbhatta...@gmail.com>

I tried to document this in the wiki:

http://www.nsnam.org/wiki/index.php/Troubleshooting#Scons_NSC_error

More generally, Gustavo, build.py needs a way to programatically
disable features, and shouldn't stop the build of ns-3 if optional
components fail first.

I committed a patch to make build.py keep going even if NSC build fails.  I also added a --disable-nsc option.
 

[lizha...@gmail.com]

I couldn't find out the .config file because I didn't know it's a
hiding file. So I didn't hack into the .config file. Instead, I hacked
into the build.py and remove the if-else part in the main function
which contains "nsc" in its comment. And it worked! The building
process just jump over the nsc part and build successfully. Is that
any problem?

On Apr 3, 11:17 pm, Raj Bhattacharjea <rbhattachar...@gmail.com>
wrote:

[Gustavo Carneiro]

2009/4/3 lizha...@gmail.com <lizha...@gmail.com>

I couldn't find out the .config file because I didn't know it's a
hiding file. So I didn't hack into the .config file. Instead, I hacked
into the build.py and remove the if-else part in the main function
which contains "nsc" in its comment. And it worked! The building
process just jump over the nsc part and build successfully. Is that
any problem?

No problem.  Possibly the --with-nsc option will be given to ns-3, but ns-3 won't even try to use NSC until a simulation script especially requests it.  When you run ./waf --regression, inside ns-3.4, it is possible that the NSC regression test will fail, but don't worry about it.