Chief Delphi - Alternate GCC Toolchain

Page 7 of 11

Show 100 post(s) from this thread on one page

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)

- - Alternate GCC Toolchain (http://www.chiefdelphi.com/forums/showthread.php?t=109385)

William Kunkel

16-02-2013 15:53

Re: Alternate GCC Toolchain

I'm sorry, I don't full understand what you're telling me to do. I'm not very familiar with the gcc build process. I've just been following the instructions rbmj posted at the beginning of this thread (although they had several issues which I had to correct). Are there other things I ought to be doing?

codes02

16-02-2013 16:12

Re: Alternate GCC Toolchain

What are the contents of gcc-master/gcc/DATESTAMP and gcc-master/gcc/BASE-VER?

the contents of these files gives us a good idea about what version of gcc you are trying to compile
the "gcc-master" portion is taken from the command outputs you have previously posted

Edit: Also, to really help, we need to know the complete steps you've taken in trying to build it (you mention you changed some things in rbmj's instructions).

Edit2: also, I'm only asking you for the version info so I can tell you to use a newer version. If you're not trying to build a recent _snapshot_ of gcc-4.8, failure is likely.

Edit3: FYI, I've used 4.8-20130210 successfully in the build script I posted http://www.chiefdelphi.com/forums/sh...1&postcount=86

Edit4: Looking back at rbmj's original instructions, he uses an archive of the current vcs version (via the git mirror on github), so it should be the latest version. This just means you probably missed something with the headers. I've found that doing the copy & symlink dance is completely unneeded, and omit it in my build script.

William Kunkel

16-02-2013 19:37

Re: Alternate GCC Toolchain

Sorry it took so long to respond. The sequence of commands I ran (cleaned up a bit without ls's and such) was the following. I added comments to every line I modified.

Code:

mkdir gcc-install-tmp

cd gcc-install-tmp



sudo mkdir -p /usr/powerpc-wrs-vxworks/wind_base

sudo mkdir -p /usr/powerpc-wrs-vxworks/include



sudo echo 'export WIND_BASE=/usr/powerpc-wrs-vxworks/wind_base' >> /etc/profile



source /etc/profile



wget https://github.com/mirrors/gcc/archive/master.zip

wget http://ftp.gnu.org/gnu/binutils/binutils-2.22.tar.bz2

wget ftp://ftp.ni.com/pub/devzone/tut/updated_vxworks63gccdist.zip



# The file downloaded from github is called "master.zip",

# I'm not sure why he had gcc-master.zip

unzip master.zip



tar -jxvf binutils-2.22.tar.bz2

unzip updated_vxworks63gccdist.zip



mkdir -p $WIND_BASE/target



sudo cp -R gccdist/WindRiver/vxworks-6.3/host/. $WIND_BASE/host



# I switched these next two lines, because otherwise I'm trying to create

# a link to a file that isn't there yet

sudo cp -R gccdist/WindRiver/vxworks-6.3/target/h/. /usr/powerpc-wrs-vxworks/sys-include

sudo ln -s /usr/powerpc-wrs-vxworks/sys-include $WIND_BASE/target/h



sudo ln -s sys-include/wrn/coreip /usr/powerpc-wrs-vxworks/include



mkdir binutils-build

cd binutils-build



../binutils-2.22/configure --prefix=/usr --target=powerpc-wrs-vxworks --disable-nls

make -j4

sudo make install



cd ..

mkdir gcc-build

cd gcc-build



../gcc-master/configure \

  --prefix=/usr \

  --target=powerpc-wrs-vxworks \

  --with-gnu-as \

  --with-gnu-ld \

  --with-headers \

  --disable-shared \

  --disable-libssp \

  --disable-multilib \

  --with-float=hard \

  --enable-languages=c,c++ \

  --enable-threads=vxworks \

  --without-gconv \

  --disable-libgomp \

  --disable-nls \

  --disable-libmudflap \

  --with-cpu-PPC603 \

  --disable-symvers



# And this is where it fails

make -j4

The contents of gcc-master/gcc/DATESTAMP is:

Quote:

20130215

And the contents of gcc-master/gcc/BASE-VER is:

Quote:

4.8.0

codes02

16-02-2013 20:44

Re: Alternate GCC Toolchain

Your GCC is plenty recent (as I belatedly realized).

It's probably something to do with the copying and symlinking sillyness. I haven't set my own install up like that, rather, I let gcc's configure copy $WIND_BASE/target/h to $PREFIX/sys-include.

You could try that

Code:

export WIND_BASE=$(realpath -m gccdist/WindRiver/vxworks-6.3)

# configure gcc with an argument to --with-headers

--with-headers="$WIND_BASE/target/h"

Keep in mind that I've not tested anything that is built with the resulting toolchain (as I don't have a cRIO).

Edit: Make sure that you clear out /usr/powerpc-wrs-vxworks (your PREFIX) completely before trying again. Left over directory setups and files can cause issues.

William Kunkel

17-02-2013 12:59

Re: Alternate GCC Toolchain

Alright, I tried your suggestion. It got farther this time but now it's failing with this error:

Quote:

In file included from /home/maraschinopanda/alt-gcc/gcc-build/gcc/include-fixed/syslimits.h:7:0,
from /home/maraschinopanda/alt-gcc/gcc-build/gcc/include-fixed/limits.h:34,
from ../../../gcc-master/libgcc/libgcc2.c:1731:
/home/maraschinopanda/alt-gcc/gcc-build/gcc/include-fixed/limits.h:168:61: error: no include path in which to search for limits.h
#include_next <limits.h> /* recurse down to the real one */
^

codes02

17-02-2013 19:06

Re: Alternate GCC Toolchain

Did you completely remove PREFIX before reattempting the build?
Did you completely remove the build directory before rebuilding?
What was your complete configure line for gcc?

Edit: I tried building the current -9999/head/"master" of gcc via my buildscript and had no issues, I suspect that in your case one of the following is the problem:

--with-headers isn't right, potentially due to WIND_BASE not being set properly
some files/symlinks where left in PREFIX and are messing things up

William Kunkel

17-02-2013 23:11

Re: Alternate GCC Toolchain

I completely removed the PREFIX and build directories. I just pulled from the compressed files I downloaded again, to be safe. The configure line I had was:

Code:

../gcc-master/configure \

  --prefix=/usr \

  --target=powerpc-wrs-vxworks \

  --with-gnu-as \

  --with-gnu-ld \

  --with-headers="$WIND_BASE/target/h" \

  --disable-shared \

  --disable-libssp \

  --disable-multilib \

  --with-float=hard \

  --enable-languages=c,c++ \

  --enable-threads=vxworks \

  --without-gconv \

  --disable-libgomp \

  --disable-nls \

  --disable-libmudflap \

  --with-cpu-PPC603 \

  --disable-symvers

And I had set $WIND_BASE to

Code:

$(realpath -m gccdist/WindRiver/vxworks-6.3)

per your post.

I also changed my make command from

Code:

make -j4

to
[CODE
]make -j4 inhibit_libc=true
[/code]
per your earlier suggestion.

The only useful information I have found about this was that it can sometimes be caused by missing glibc, but I do have the most recent version Gentoo considers stable.

Thanks for all the help so far!

codes02

17-02-2013 23:51

Re: Alternate GCC Toolchain

Just to be sure, you're letting the $(realpath ... ) bit expand when it is assigned to WIND_BASE, right? Meaning that you aren't using single quotes around it, and `echo $WIND_BASE` gives something like '/home/maraschinopanda/alt-gcc/gccdist/WindRiver/vxworks-6.3'?

Can you check that `ls $WIND_BASE` works from the directory you're calling gcc's configure from?

Also, I recommend not using /usr as your prefix (especially not when testing), as it is actually used by other programs and removing it will break your system. I prefer using ~/x-tools/wrs (I have some shell setup scripts that add all of ~/x-tools/*/bin to my path). Any unused path is fine (an one in your homedir has the benefit of not needing to install with root privileges).

Edit: Note that the glibc you have installed on your system is _not_ going to cause your issue, the compiler for vxworks that you are building does _not_ use glibc at all.

William Kunkel

18-02-2013 02:49

Re: Alternate GCC Toolchain

I didn't think glibc was the problem, but I thought it was worth mentioning. I didn't remove /usr itself, of course, but I did remove all of the changes the build made. However, I can see why it might be better to use another prefix. I did make certain that $WIND_BASE was doing what I expected. I could try recompiling with a temporary prefix.

rbmj	18-02-2013 19:01

Re: Alternate GCC Toolchain

Quote:

Originally Posted by MaraschinoPanda (Post 1234369)

Hi everybody! I've been trying to get this built on my Gentoo box, but I've run into issues, and googling hasn't turned up anything. It compiles a few things, then I run into this:

Then the error cascades and make exits error code 2. Unfortunately, I don't know enough about GCC to diagnose the issue. Any pointers?

That's an issue with include directories.

GCC wants <header dir>/wrn/coreip in the search path. The way this is solved is by putting the headers in /usr/powerpc-wrs-vxworks/sys-include and then symlinking /usr/powerpc-wrs-vxworks/include to sys-include/wrn/coreip

If you don't set WIND_BASE you'll get the "cannot compute suffix of object files" error (most likely) at configure time.

codes02

18-02-2013 19:23

Re: Alternate GCC Toolchain

Quote:

Originally Posted by rbmj (Post 1235865)

GCC wants <header dir>/wrn/coreip in the search path. The way this is solved is by putting the headers in /usr/powerpc-wrs-vxworks/sys-include and then symlinking /usr/powerpc-wrs-vxworks/include to sys-include/wrn/coreip

I am almost certain this is not correct. I've built gcc fine without any symlinking mess. I suspect MaraschinoPanda's problem has a different solution (though by all means, try this one).

rbmj	18-02-2013 20:19

Re: Alternate GCC Toolchain

Quote:

Originally Posted by codes02 (Post 1235875)

I am almost certain this is not correct. I've built gcc fine without any symlinking mess. I suspect MaraschinoPanda's problem has a different solution (though by all means, try this one).

It is correct.

GCC wants to see wrn/coreip. There are many ways you can do this. You don't need to symlink. But it's easier. There are other hacks around it, but that's the simplest way, and it works nicest with fixincludes.

codes02

18-02-2013 20:43

Re: Alternate GCC Toolchain

limits.h is in target/h, not target/h/wrn/coreip , so symlinking in wrn/coreip will not help at all for this error.

rbmj	18-02-2013 20:52

Re: Alternate GCC Toolchain

Quote:

Originally Posted by codes02 (Post 1235914)

limits.h is in target/h, not target/h/wrn/coreip , so symlinking in wrn/coreip will not help at all for this error.

I was referring to:

Quote:

Code:

/home/maraschinopanda/alt-gcc/gcc-build/gcc/include-fixed/ioLib.h:148:21: fatal error: net/uio.h: No such file or directory

#include <net/uio.h>

wlmeng11

19-02-2013 00:07

Re: Alternate GCC Toolchain

Hi!
I built this successfully on Arch Linux x64 with the instruction in the OP save for the unzip command having the wrong name (should be "unzip master.zip" ) and building gcc-build with "make -j4 inhibit_libc=true".

I haven't tested on a robot yet, but successfully compiled jmesmon's test program.
https://github.com/jmesmon/frc-min

I will try to make a PKGBUILD for this in the Arch Linux AUR if I can.

All times are GMT -5. The time now is 20:08.

Page 7 of 11

Show 100 post(s) from this thread on one page