This is the mail archive of the crossgcc@sourceware.org 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: [discuss] Problem building cross compiler for x86_64


On 1/23/06, Manish Katiyar <mkatiyar@gmail.com> wrote:
> Thanks Dan,
>         your mail prevented me from doing the whole stuff again. got
> rid of the GPL issue.

Good!

> One last trouble for you guys.......when I just
> copied the whole RESULT_TOP directory to a different 32 bit machine to
> test if everything is working fine i ended up with errors.

How did you copy it?   You have to use cp -a or tar or mv;
plain old cp will screw up symlinks.

Also, perhaps the tools you're building are old enough that
they don't support being relocated after they are built.
If that's the case, then you can use
http://kegel.com/crosstool/current/fix-embedded-paths.c
to fix up the embedded paths after the move -- as long as the
new absolute path is shorter than the original.
See crosstool.spec.in for an example of its use.

> I tried creating the rpms using the cross tool. The source rpm was
> created successfully
>
> [katiyar@nasvm SRPMS]$ rpm -qp crosstool-gcc-3.3.3-glibc-2.3.2-0.38-1.src.rpm -l
> binutils-2.15.tar.gz
> crosstool-0.38.tar.gz
> crosstool-gcc-3.3.3-glibc-2.3.2.spec
> gcc-3.3.3.tar.gz
> glibc-2.3.2.tar.gz
> glibc-linuxthreads-2.3.2.tar.gz
> linux-2.4.26.tar.gz
>
> But when I tried creating the binaries , after doing lot of builds it
> ended up with errors as
>
> RPM build errors:
>     Symlink points to BuildRoot:
> /usr/crosstool/gcc-3.3.3-glibc-2.3.2/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sys-root/lib
> -> /var/tmp/crosstool-gcc-3.3.3-glibc-2.3.2-0.38-1-root/usr/crosstool/gcc-3.3.3-glibc-2.3.2/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sys-root/lib64

I haven't run into that myself, possibly because I've never built
an rpm for gcc-3.3.3.

> My lead is OK if I can give him in a tar ball. So if you guys can just
> help me to figure out which files do i need to tar to make the
> compiler working on a different 32 bit machine,

The whole installed tree.
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv

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


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