This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Trouble putting together a glibc-2.3.5 addon for ColdFire


>>> >Is there a glibc-ports-3.3.5 directory anywhere in the
>>> >source or build directories?
>>> >   cd /home/peter/work/cvs-logic/logic/ColdFire/LinuxTools/crosstool
>>> >   find . -name glibc-ports-3.3.5
>>>
>>> [peter@thunk glibc-2.3.5]$ pwd
>>> /home/peter/work/cvs-logic/logic/ColdFire/LinuxTools/crosstool/build/m68k-l
>>>inux/gcc-3.4.3-glibc-2.3.5/glibc-2.3.5 [peter@thunk glibc-2.3.5]$ find .
>>> -name glibc-ports-2.3.5
>>> ./glibc-ports-2.3.5
>>> [peter@thunk glibc-2.3.5]$
>>>
>>> So yes, the ports directory is just under the glibc-2.3.5 source dir
>>> that the ports/README says to put it.

I think I may have figured it out from Looking at
glibc-ports-2.3.5/Makefile which has 'subdir = ports' in it.  I'm
building a toolchain to be sure.

If so then the README in glibc-ports-2.3.5.tar.bz2 should be more
adamant about the directory having to be named 'ports'.  This wouldn't
be so misleading if glibc-ports-2.3.5.tar.bz2 followed the linuxthread
add-on convention of naming the directory in the tarball to be the
directory of the addon, which in this case is 'ports', not
'glibc-ports-2.3.5'.... 

-- 
Peter Barada
peter@the-baradas.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]