[gentoo-amd64] crossdev x86 to x86_64

[gentoo-amd64] crossdev x86 to x86_64

[Daniel Iliev]

I tried to use a x86 pc to aid the compiling of packages for amd64 via
distcc. I followed the official "DistCC Cross-compiling Guide" [1] but I
had no luck. Is it possible at all, am I doing something wrong or there
is a bug?

[1] http://www.gentoo.org/doc/en/cross-compiling-distcc.xml


The i686 pc gives:

localhost ~ # crossdev -t x86_64-pc-linux-gnu
 * You need to set PORTDIR_OVERLAY in your make.conf.
 * A standard setting is /usr/local/portage
localhost ~ # echo PORTDIR_OVERLAY=/usr/local/portage >> /etc/make.conf
localhost ~ # crossdev -t x86_64-pc-linux-gnu
!!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage'
!!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage'

localhost ~ # mkdir /usr/local/portage
localhost ~ # crossdev -t x86_64-pc-linux-gnu
--------------------------------------------------------------------------------
 * Host Portage ARCH:     x86
 * Target Portage ARCH:   amd64
 * Target System:         x86_64-pc-linux-gnu
 * Stage:                 4 (C/C++ compiler)

 * binutils:              binutils-[latest]
 * gcc:                   gcc-[latest]
 * headers:               linux-headers-[latest]
 * libc:                  glibc-[latest]

 * PORTDIR_OVERLAY:       /usr/local/portage
 * PORT_LOGDIR:           /var/log/portage
 * PKGDIR:                /usr/portage/packages/cross/x86_64-pc-linux-gnu
 * PORTAGE_TMPDIR:        /tmp/cross/x86_64-pc-linux-gnu
  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~ 
-  _  -
 * Forcing the latest versions of binutils-config/gcc-config
...          [ ok ]
 * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log
 * Emerging cross-binutils ...

 * binutils failed :(
 * If you file a bug, please attach the following logfiles:
 * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log
 * /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log



-- 
Best regards,
Daniel


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] crossdev x86 to x86_64

[Lorenzo Milesi]

>  * Emerging cross-binutils ...
>
>  * binutils failed :(
>  * If you file a bug, please attach the following logfiles:
>  * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log
>  * /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log

I did it some time ago, then gave up because of many packages failing
compilation (netkit-telnetd was the latest).

Have a look at bugs.gentoo.org, I remember I had to get a patch to
build the x86 host.

ciao
maxxer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] crossdev x86 to x86_64

[Daniel Iliev]

Lorenzo Milesi wrote:
>>  * Emerging cross-binutils ...
>>
>>  * binutils failed :(
>>  * If you file a bug, please attach the following logfiles:
>>  * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log
>>  * /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log
>
> I did it some time ago, then gave up because of many packages failing
> compilation (netkit-telnetd was the latest).
>
> Have a look at bugs.gentoo.org, I remember I had to get a patch to
> build the x86 host.
>
> ciao
> maxxer


If it is a known bug-case, I'll just leave it alone until devs do their
magic. The vise-versa case works w/o problem: I'm using crossdev on
amd64 to compile i686 packages via distcc.


-- 
Best regards,
Daniel


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] crossdev x86 to x86_64

[Lorenzo Milesi]

On 11/10/06, Daniel Iliev <danny@ilievnet.com> wrote:
> If it is a known bug-case, I'll just leave it alone until devs do their
> magic. The vise-versa case works w/o problem: I'm using crossdev on
> amd64 to compile i686 packages via distcc.

hmm... I did it some months ago, and it's still there... I think if
you want cross compile you'd better have a look at the patch :-)

cheers
maxxer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] crossdev x86 to x86_64

[Michael Weyershäuser]

[-- Attachment #1: Type: text/plain, Size: 2431 bytes --]

Daniel Iliev wrote:
> I tried to use a x86 pc to aid the compiling of packages for amd64 via
> distcc. I followed the official "DistCC Cross-compiling Guide" [1] but I
> had no luck. Is it possible at all, am I doing something wrong or there
> is a bug?
> 
> [1] http://www.gentoo.org/doc/en/cross-compiling-distcc.xml
> 
I'm running such a setup for about 6 months now and I have never run
into any package not compiling due to the crossdev environment (and I
compile quite a lot of packages as an amd64 AT). So this should in
general work without any trouble or patches.
> 
> The i686 pc gives:
> 
> localhost ~ # crossdev -t x86_64-pc-linux-gnu
>  * You need to set PORTDIR_OVERLAY in your make.conf.
>  * A standard setting is /usr/local/portage
> localhost ~ # echo PORTDIR_OVERLAY=/usr/local/portage >> /etc/make.conf
> localhost ~ # crossdev -t x86_64-pc-linux-gnu
> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage'
> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage'
> 
> localhost ~ # mkdir /usr/local/portage
> localhost ~ # crossdev -t x86_64-pc-linux-gnu
> --------------------------------------------------------------------------------
>  * Host Portage ARCH:     x86
>  * Target Portage ARCH:   amd64
>  * Target System:         x86_64-pc-linux-gnu
>  * Stage:                 4 (C/C++ compiler)
> 
>  * binutils:              binutils-[latest]
>  * gcc:                   gcc-[latest]
>  * headers:               linux-headers-[latest]
>  * libc:                  glibc-[latest]
> 
>  * PORTDIR_OVERLAY:       /usr/local/portage
>  * PORT_LOGDIR:           /var/log/portage
>  * PKGDIR:                /usr/portage/packages/cross/x86_64-pc-linux-gnu
>  * PORTAGE_TMPDIR:        /tmp/cross/x86_64-pc-linux-gnu
>   _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~ 
> -  _  -
>  * Forcing the latest versions of binutils-config/gcc-config
> ...          [ ok ]
>  * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log
>  * Emerging cross-binutils ...
> 
>  * binutils failed :(
>  * If you file a bug, please attach the following logfiles:
>  * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log
>  * /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log

If this was a bug I would close it as RESOLVED NEEDINFO right now.
Please attach these two log files if you want anybody to be able to help
you ;)



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

Re: [gentoo-amd64] crossdev x86 to x86_64

[Daniel Iliev]

Michael Weyershäuser wrote:
> Daniel Iliev wrote:
>   
>> I tried to use a x86 pc to aid the compiling of packages for amd64 via
>> distcc. I followed the official "DistCC Cross-compiling Guide" [1] but I
>> had no luck. Is it possible at all, am I doing something wrong or there
>> is a bug?
>>
>> [1] http://www.gentoo.org/doc/en/cross-compiling-distcc.xml
>>
>>     
> I'm running such a setup for about 6 months now and I have never run
> into any package not compiling due to the crossdev environment (and I
> compile quite a lot of packages as an amd64 AT). So this should in
> general work without any trouble or patches.
>   
>> The i686 pc gives:
>>
>> localhost ~ # crossdev -t x86_64-pc-linux-gnu
>>  * You need to set PORTDIR_OVERLAY in your make.conf.
>>  * A standard setting is /usr/local/portage
>> localhost ~ # echo PORTDIR_OVERLAY=/usr/local/portage >> /etc/make.conf
>> localhost ~ # crossdev -t x86_64-pc-linux-gnu
>> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage'
>> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage'
>>
>> localhost ~ # mkdir /usr/local/portage
>> localhost ~ # crossdev -t x86_64-pc-linux-gnu
>> --------------------------------------------------------------------------------
>>  * Host Portage ARCH:     x86
>>  * Target Portage ARCH:   amd64
>>  * Target System:         x86_64-pc-linux-gnu
>>  * Stage:                 4 (C/C++ compiler)
>>
>>  * binutils:              binutils-[latest]
>>  * gcc:                   gcc-[latest]
>>  * headers:               linux-headers-[latest]
>>  * libc:                  glibc-[latest]
>>
>>  * PORTDIR_OVERLAY:       /usr/local/portage
>>  * PORT_LOGDIR:           /var/log/portage
>>  * PKGDIR:                /usr/portage/packages/cross/x86_64-pc-linux-gnu
>>  * PORTAGE_TMPDIR:        /tmp/cross/x86_64-pc-linux-gnu
>>   _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~ 
>> -  _  -
>>  * Forcing the latest versions of binutils-config/gcc-config
>> ...          [ ok ]
>>  * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log
>>  * Emerging cross-binutils ...
>>
>>  * binutils failed :(
>>  * If you file a bug, please attach the following logfiles:
>>  * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log
>>  * /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log
>>     
>
> If this was a bug I would close it as RESOLVED NEEDINFO right now.
> Please attach these two log files if you want anybody to be able to help
> you ;)
>
>
>   


I saw an update for gcc and after emerging it I decided to try again.
Four steps forward but the final goal is not achieved yet.


crossdev -t x86_64-pc-linux-gnu
--------------------------------------------------------------------------------
 * Host Portage ARCH:     x86
 * Target Portage ARCH:   amd64
 * Target System:         x86_64-pc-linux-gnu
 * Stage:                 4 (C/C++ compiler)

 * binutils:              binutils-[latest]
 * gcc:                   gcc-[latest]
 * headers:               linux-headers-[latest]
 * libc:                  glibc-[latest]

 * PORTDIR_OVERLAY:       /usr/local/portage
 * PORT_LOGDIR:           /var/log/portage
 * PKGDIR:                /usr/portage/packages/cross/x86_64-pc-linux-gnu
 * PORTAGE_TMPDIR:        /tmp/cross/x86_64-pc-linux-gnu
  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~  -  _  -  ~ 
-  _  -
 * Forcing the latest versions of binutils-config/gcc-config
...          [ ok ]
 * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log
 * Emerging cross-binutils
...                                            [ ok ]
 * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-gcc-stage1.log
 * Emerging cross-gcc-stage1
...                                          [ ok ]
 * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-linux-headers.log
 * Emerging cross-linux-headers
...                                       [ ok ]
 * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-glibc.log
 * Emerging cross-glibc ...

 * glibc failed :(
 * If you file a bug, please attach the following logfiles:
 * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log
 * /var/log/portage/cross-x86_64-pc-linux-gnu-glibc.log


The last file is attached in this email message as a bzip2 archive. At
its end this log file reads:

>checking for forced unwind support... no
>configure: error: forced unwind support is required


Unfortunately I have no idea what this means. Any suggestions, please?

-- 
Best regards,
Daniel


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] crossdev x86 to x86_64

[Daniel Iliev]

[-- Attachment #1: Type: text/plain, Size: 99 bytes --]


I'm sorry for this. I forgot to attach the log-file.

Here it goes.


-- 
Best regards,
Daniel




[-- Attachment #2: cross-x86_64-pc-linux-gnu-glibc.log.bz2 --]
[-- Type: application/x-bzip, Size: 5955 bytes --]