Bug#342248: [m68k headers] binaries are i386 - cannot execute binary file

2006-07-16 Thread Arnaud Fontaine
unblock 360739 by 342248
thanks

Hello,

It is  fixed AFAIK. Squashfs FTBFS  but not for the  same reason. Thanks
for your work.  If Max agrees, it  is maybe the time to  close this bug,
right ?

Regards,
Arnaud Fontaine


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342248: [m68k headers] binaries are i386 - cannot execute binary file

2005-12-15 Thread Max Vozeler
On Thu, Dec 15, 2005 at 02:39:45PM +0100, Sven Luther wrote:
> Are you sure you are using the per-flavour header packages
> (linux-headers-2.6.14-2- ?

The package build-depends on linux-headers-2.6.14-2-all and 
uses the per-flavour headers for the actual build.

> Also, do you know about the external build module plan ? It is as follows :
> 
>   1) build-depend on linux-headers-2.6.14 or linux-headers-2.6.14-2-all.
>
>   2) look at /usr/src/linux-headers-2.6.14-2/flavours for a list of supported
>   flavours.
> 
>   3) for f in `cat /usr/src/linux-headers-2.6.14-2/flavours`; do 
> ...
> make ... KSRC=/lib/modules/2.6.14-2-$f
>   ...
>  done

Yes, this is basically what loop-aes-modules does. Except, I'm
extracting the available flavours from [1] at build-time of the
source package, because I want to include the package entries in
debian/control before upload and sometimes exclude flavours.

[1] /usr/src/linux-headers-2.6.14/debian/arch/*/defines 

cheers,
Max


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342248: [m68k headers] binaries are i386 - cannot execute binary file

2005-12-15 Thread Sven Luther
On Thu, Dec 15, 2005 at 02:09:47PM +0100, Max Vozeler wrote:
> Hi Christian,
> 
> On Thu, Dec 15, 2005 at 08:12:05AM +0100, Christian T. Steigies wrote:
> > On Tue, Dec 06, 2005 at 03:48:40PM +0100, Max Vozeler wrote:
> > > Apparently the binaries in m68k -headers were built for i386.
> > 
> > Yes, this may very well be possible, since the m68k linux-* packages
> > were cross-compiled on i386. Since the linux-image-* packages are
> > built in the same run, and they are properly cross-compiled for m68k
> > and actually work (at least) on (my) m68k boxes, this must be a bug in
> > the linux-headers build rules, they should be cross-compiled, too.
> 
> Thanks for looking into this.
> 
> > > This breaks builds of external modules as they try to execute eg.
> > > scripts/basic/fixdep on m68k.
> > 
> > Do you have any external modules for m68k that are not part of the kernel?
> > Who is supplying those?
> 
> It's not specific to m68k actually. The module in question is the
> loop-AES extended loopback encryption module maintained by Jari Ruusu
> <[EMAIL PROTECTED]>. I'm trying to build it for all 
> archs that have 2.6 -di kernels in the archive.

Are you sure you are using the per-flavour header packages
(linux-headers-2.6.14-2- ?

Also, do you know about the external build module plan ? It is as follows :

  1) build-depend on linux-headers-2.6.14 or linux-headers-2.6.14-2-all.

  2) look at /usr/src/linux-headers-2.6.14-2/flavours for a list of supported
  flavours.

  3) for f in `cat /usr/src/linux-headers-2.6.14-2/flavours`; do 
...
make ... KSRC=/lib/modules/2.6.14-2-$f
...
 done

Friendly,

Sven Luther



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342248: [m68k headers] binaries are i386 - cannot execute binary file

2005-12-15 Thread Max Vozeler
Hi Christian,

On Thu, Dec 15, 2005 at 08:12:05AM +0100, Christian T. Steigies wrote:
> On Tue, Dec 06, 2005 at 03:48:40PM +0100, Max Vozeler wrote:
> > Apparently the binaries in m68k -headers were built for i386.
> 
> Yes, this may very well be possible, since the m68k linux-* packages
> were cross-compiled on i386. Since the linux-image-* packages are
> built in the same run, and they are properly cross-compiled for m68k
> and actually work (at least) on (my) m68k boxes, this must be a bug in
> the linux-headers build rules, they should be cross-compiled, too.

Thanks for looking into this.

> > This breaks builds of external modules as they try to execute eg.
> > scripts/basic/fixdep on m68k.
> 
> Do you have any external modules for m68k that are not part of the kernel?
> Who is supplying those?

It's not specific to m68k actually. The module in question is the
loop-AES extended loopback encryption module maintained by Jari Ruusu
<[EMAIL PROTECTED]>. I'm trying to build it for all 
archs that have 2.6 -di kernels in the archive.

cheers,
Max


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342248: [m68k headers] binaries are i386 - cannot execute binary file

2005-12-14 Thread Christian T. Steigies
Hi,
On Tue, Dec 06, 2005 at 03:48:40PM +0100, Max Vozeler wrote:
> Package: linux-2.6
> Version: 2.6.12-10
> Severity: important
> 
> This bug is a bit weird :-)
> 
> Apparently the binaries in m68k -headers were built for i386.

Yes, this may very well be possible, since the m68k linux-* packages were
cross-compiled on i386. Since the linux-image-* packages are built in the
same run, and they are properly cross-compiled for m68k and actually work
(at least) on (my) m68k boxes, this must be a bug in the linux-headers build
rules, they should be cross-compiled, too. Can somebody look into that?

> This breaks builds of external modules as they try to execute eg.
> scripts/basic/fixdep on m68k.

Do you have any external modules for m68k that are not part of the kernel?
Who is supplying those?

Christian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#342248: [m68k headers] binaries are i386 - cannot execute binary file

2005-12-06 Thread Max Vozeler
Package: linux-2.6
Version: 2.6.12-10
Severity: important

This bug is a bit weird :-)

Apparently the binaries in m68k -headers were built for i386.
This breaks builds of external modules as they try to execute eg.
scripts/basic/fixdep on m68k.

  $ dpkg -x linux-headers-2.6.12-1-amiga_2.6.12-10_m68k.deb .
  $ cd usr/src/linux-headers-2.6.12-1-amiga/scripts/basic
  $ file fixdep
  fixdep:ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for 
GNU/Linux 2.2.0, dynamically linked (uses shared libs), stripped

http://experimental.ftbfs.de/fetch.php?&pkg=loop-aes-modules&ver=3.1b%2B6&arch=m68k&stamp=1131026070&file=log&as=raw
  ...
  make[3]: Entering directory `/usr/src/linux-headers-2.6.12-1-amiga'
CC [M]  
/build/buildd/loop-aes-modules-3.1b+6/modules/loop-aes/loop-AES-v3.1b/tmp-d-kbuild/patched-loop.o
  /bin/sh: scripts/basic/fixdep: cannot execute binary file

cheers,
Max


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]