[CS-FSLUG] ON topic: gcc help; was: off topic? gcc help

[warm38 at juno.com]

> Date: Fri, 16 Jul 2010 16:29:54 -0500
> From: Tim Young <Tim.Young at LightSys.org>
> Subject: Re: [CS-FSLUG] off topic? gcc help
> 
>   Hi there,
> Your error message means that, when you ran the configure, you did 
> not tell it what the target was (or did not have a target that it 
> understood).
> 
> On the first link you sent, it had this example:
> 
> /        configure --target=$TARGET  --prefix=$PREFIX  
> --disable-nls/
> 
> Where, in a section above, the variables TARGET and PREFIX are 
> configured:
> /
> /
> 
> /        export  PREFIX=/usr/local/cross
>         export  TARGET=i586-elf/

The instructions I was GIVEN was "configure --target=xxx
--prefix=/opt/xxx/"
I changed the target to "xxx-elf" and got further. HOORAY!
But it still died.

And if you notice it has no indication of program, line, or nastygram. 
8-b
------- begin -------
wasmith at linux-box:~/binutils-xxx$ make
make[1]: Entering directory `/home/wasmith/binutils-xxx'
make[2]: Entering directory `/home/wasmith/binutils-xxx/libiberty'
if [ x"" != x ] && [ ! -d pic ]; then \
   mkdir pic; \
 else true; fi
touch stamp-picdir
CONFIG_FILES= CONFIG_HEADERS=config.h:../../binutils/libiberty/config.in
/bin/bash ./config.status
config.status: creating config.h
config.status: executing default commands

...

echo ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./alloca.o ./argv.o
./choose-temp.o ./concat.o ./cp-demint.o ./dyn-string.o ./fdmatch.o
./fibheap.o ./filename_cmp.o ./floatformat.o ./fnmatch.o
./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o ./getruntime.o
./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o ./make-relative-prefix.o
./make-temp-file.o ./objalloc.o ./obstack.o ./partition.o ./pexecute.o
./physmem.o ./pex-common.o ./pex-one.o ./pex-unix.o ./safe-ctype.o
./sort.o ./spaces.o ./splay-tree.o ./strerror.o ./strsignal.o
./unlink-if-ordinary.o ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o
./xstrdup.o ./xstrerror.o ./xstrndup.o > required-list
make[3]: Entering directory
`/home/wasmith/binutils-xxx/libiberty/testsuite'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory
`/home/wasmith/binutils-xxx/libiberty/testsuite'
make[2]: Leaving directory `/home/wasmith/binutils-xxx/libiberty'
make[2]: Entering directory `/home/wasmith/binutils-xxx/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/wasmith/binutils-xxx/intl'
make[2]: Entering directory `/home/wasmith/binutils-xxx/bfd'
Making info in doc
make[3]: Entering directory `/home/wasmith/binutils-xxx/bfd/doc'
restore=: && backupdir=".am$$" && \
 rm -rf $backupdir && mkdir $backupdir && \
 if (/home/wasmith/binutils/missing makeinfo --split-size=5000000
--split-size=5000000 --version) >/dev/null 2>&1; then \
   for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9]
bfd.i[0-9][0-9]; do \
     if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
   done; \
 else :; fi && \
 if /home/wasmith/binutils/missing makeinfo --split-size=5000000
--split-size=5000000   -I ../../../binutils/bfd/doc \
  -o bfd.info `test -f 'bfd.texinfo' || echo
'../../../binutils/bfd/doc/'`bfd.texinfo; \
 then \
   rc=0; \
 else \
   rc=$?; \
   $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
 fi; \
 rm -rf $backupdir; exit $rc
WARNING: `makeinfo' is missing on your system.  You should only need it
if
         you modified a `.texi' or `.texinfo' file, or any other file
         indirectly affecting the aspect of the manual.  The spurious
         call might also be the consequence of using a buggy `make' (AIX,
         DU, IRIX).  You might want to install the `Texinfo' package or
         the `GNU make' package.  Grab either from any GNU archive site.
make[3]: *** [bfd.info] Error 1
make[3]: Leaving directory `/home/wasmith/binutils-xxx/bfd/doc'
Making info in po
make[3]: Entering directory `/home/wasmith/binutils-xxx/bfd/po'
make[3]: Nothing to be done for `info'.
make[3]: Leaving directory `/home/wasmith/binutils-xxx/bfd/po'
make[3]: Entering directory `/home/wasmith/binutils-xxx/bfd'
make[3]: Nothing to be done for `info-am'.
make[3]: Leaving directory `/home/wasmith/binutils-xxx/bfd'
make[2]: *** [info-recursive] Error 1
make[2]: Leaving directory `/home/wasmith/binutils-xxx/bfd'
make[1]: *** [all-bfd] Error 2
make[1]: Leaving directory `/home/wasmith/binutils-xxx'
make: *** [all] Error 2
wasmith at linux-box:~/binutils-xxx$ 
------- end -------

any suggestions here?  
I'm running iUbuntu 10.04 (per Fred Miller) and Synaptic Package manager
says I've got everything makeinfo and texinfo that I gonna get. I have
make > version 8, so what other "gnu make" would there be?

I had to go out and get the xz compression tool to be able to look at the
GCC standard version of the compiler to compare and it all looks OK to
me.

So, other than something between my two ears, what [else] am I missing?


> The "TARGET" variable is what is important.
> Basically, the cross-compiler knows how to build gcc for a ton of 
> different architectures, but only those architectures.  If nobody 
> has 
> ever built gcc for that chip, you are in for a rough ride.  :(  But, 
> 
> if they already have the info for that architecture, then giving it 
> 
> the complete information in the "TARGET" variable should get you 
> started.
> 
> The file, bfd/config.bfd should contain a list of known 
> architectures.  Hopefully one of those will be close enough to the 
> chip you are trying to build gcc for.

Yep. the chip is there on the bfd list "xxx-*-elf", but the compiler is
not yet released and neither is the improved version of the chip.
I'm uncomfortable giving out any info on it for now.  The chip's [old]
version is on their web site, but I still feel funny talking about it
without their OK.
And I dont really wanna admit my ignorance out loud saying, "I'm getting
some help from friends who do this stuff a lot more often than me, so you
really should have hired them."  I dunno.. that sounds kinda .... dum. 
Knowhuddamean?


> My time availability is rather sporadic at the moment, which is why 
> I 
> am keeping this discussion on the list instead of taking it 
> off-list.  I know a few folks on the list have compiled things 
> before, so someone may be able to jump in if I cannot.  :)
> 
> While a lot of Linux is set up through package managers these days, 
> 
> there are still a number of cases where you need to use make, 
> configure, etc.  So these skills are fairly "on topic" for this 
> email-list in my book.

Now THAT is good to know!  So I changed my 'subject'

>      - Tim
> 

> From: "Ed Hurst" <ehurst at soulkiln.org>
> 
> Moderator says, "Yes, yes indeedy!"
> 
> -- 
> Ed Hurst

And that makes it official!   8-)
____________________________________________________________
Business Analyst Skills
Learn Critical Business Analyst Skills - 100% Online Certificate!
http://thirdpartyoffers.juno.com/TGL3141/4c42148358ef837918fst01vuc