Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem building toolchain #36

Closed
nandub opened this issue Dec 13, 2013 · 8 comments
Closed

Problem building toolchain #36

nandub opened this issue Dec 13, 2013 · 8 comments
Assignees
Labels

Comments

@nandub
Copy link
Contributor

nandub commented Dec 13, 2013

I was able to change some of the scripts to be able to run this on Mac OS X, but after running for a long while it fails with this error:

./build-all.sh --no-uclibc --elf32 --install-dir /opt/toolchains
Checking out GIT trees ...
Downloading external dependencies...
Linking unified tree ...
START ELF32: Thu Dec 12 21:49:17 CST 2013
Installing in /opt/toolchains
Configuring tools ...
  finished configuring tools
Building tools ...
ERROR: tools build failed.
ERROR: arc-elf32- tool chain build failed.
./build-all.sh --no-uclibc --elf32 --install-dir /opt/toolchains  2543.22s user 1012.95s system 79% cpu 1:14:25.96 total

Where is the build logs files? here ../log-4.8/*.log??

@anthony-kolesov
Copy link
Contributor

Yes, logs are in ../logs-4.8/elf-build-%datetime%.log. Or you can edit build-elf.sh and remove redirection of Make stdout/err to the logfile.

@nandub
Copy link
Contributor Author

nandub commented Dec 13, 2013

Thanks, I rerun again it took a while but now I can see the errors:

The last few lines is displayed below

duplicate symbol _SUBOFHI in:
    libsim.a(cpu5.o)
    libsim.a(mloop7.o)
duplicate symbol _ADDCQI in:
    libsim.a(cpu5.o)
    libsim.a(mloop7.o)
duplicate symbol _ADDCFQI in:
    libsim.a(cpu5.o)
    libsim.a(mloop7.o)
duplicate symbol _ADDOFQI in:
    libsim.a(cpu5.o)
    libsim.a(mloop7.o)
duplicate symbol _SUBCQI in:
    libsim.a(cpu5.o)
    libsim.a(mloop7.o)
duplicate symbol _SUBCFQI in:
    libsim.a(cpu5.o)
    libsim.a(mloop7.o)
duplicate symbol _SUBOFQI in:
    libsim.a(cpu5.o)
    libsim.a(mloop7.o)
duplicate symbol _sim_addr_range_hit_p in:
    nrun.o
    libsim.a(traps.o)
duplicate symbol _sim_addr_range_hit_p in:
    nrun.o
    libsim.a(devices.o)
ld: 696 duplicate symbols for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [run] Error 1
make[1]: *** [all] Error 1
make: *** [all-sim] Error 2

@anthony-kolesov
Copy link
Contributor

Try building with option --no-sim:

./build-all.sh --no-uclibc --elf32 --install-dir /opt/toolchains --no-sim

That will disable CGEN simulator, which causes problems here. We know that CGEN cannot be built on Windows and disable it there by default. Probably the same for Mac... Or maybe this is caused by Clang.

@anthony-kolesov
Copy link
Contributor

Also when you rerun pass those options:

--no-unisrc --no-auto-pull --no-auto-checkout

With those build script will no do operations that should be done only once: building unified source tree (very time costly) and updating Git repositories

@nandub
Copy link
Contributor Author

nandub commented Dec 14, 2013

Thanks, I used the --no-sim parameter to get past the error. Right now I rerunning it again with --no-pdf as the pdf portion failed as well.

@nandub
Copy link
Contributor Author

nandub commented Dec 14, 2013

I have successfully built an arc-elf32 toolchain on my Mac OS X Mountain Lion (10.8.5) I used the following:

./build-all.sh --no-uclibc --elf32 --install-dir /opt/toolchains --no-sim --no-pdf --no-unisrc --no-auto-pull --no-auto-checkout

gcc (ARCompact elf32 toolchain (built 20131214)) 4.8.0
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

@anthony-kolesov
Copy link
Contributor

I suppose this issue has been resolved, so I'm closing it. Let us of any problems.

@nandub
Copy link
Contributor Author

nandub commented Dec 24, 2013

Yes, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants