Andreas Tille <[EMAIL PROTECTED]> writes:
> On Fri, 11 Jul 2008, Manuel Prinz wrote:
>
>> With these fixes it still did not build on my system. I needed to change
>> the Build-Depends on lib64z1-dev into zlib1g-dev to get it to build in a
>> clean pbuilder chroot.
>
> Well, I guess that lib64z1-de
On Thu, Jul 10, 2008 at 11:37:10AM +0200, Andreas Tille wrote:
>> Do you have the right kernel and libc installed?
>
> What is "the right" kernel / libc???
>
> $ uname -a
> Linux wr-linux02 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
> GNU/Linux
>
> It was installed via the the Debian ke
On Fri, Jul 11, 2008 at 02:40:17PM +0200, Andreas Tille wrote:
> On Fri, 11 Jul 2008, Manuel Prinz wrote:
> >With these fixes it still did not build on my system. I needed to change
> >the Build-Depends on lib64z1-dev into zlib1g-dev to get it to build in a
> >clean pbuilder chroot.
> Well, I gue
On Fri, 11 Jul 2008, Manuel Prinz wrote:
With these fixes it still did not build on my system. I needed to change
the Build-Depends on lib64z1-dev into zlib1g-dev to get it to build in a
clean pbuilder chroot.
Well, I guess that lib64z1-dev will not exist for amd64 and that this
whole mess is
Hi Andreas!
Am Dienstag, den 08.07.2008, 14:26 +0200 schrieb Andreas Tille:
> On Mon, 7 Jul 2008, William Pitcock wrote:
>
> > If you do build-depends on gcc-multilib and g++-multilib, it should fix
> > this problem.
>
> As I said it fixes the build problem - but now I have a package with a
> no
On Thu, 10 Jul 2008, Goswin von Brederlow wrote:
$ /usr/bin/maq
-bash: /usr/bin/maq: cannot execute binary file
That indicates your kernel can not execute that binary.
$ ldd /usr/bin/maq
ldd: exited with unknown exit code (126)
Usualy means the ld is missing, i.e. libc6 package missing.
Andreas Tille <[EMAIL PROTECTED]> writes:
> On Mon, 7 Jul 2008, William Pitcock wrote:
>
>> If you do build-depends on gcc-multilib and g++-multilib, it should fix
>> this problem.
>
> As I said it fixes the build problem - but now I have a package with a
> not working executable. I guess it is a
On Mon, 7 Jul 2008, William Pitcock wrote:
If you do build-depends on gcc-multilib and g++-multilib, it should fix
this problem.
As I said it fixes the build problem - but now I have a package with a
not working executable. I guess it is also a simple 64 bit problem which
might be easily solv
On Mon, 7 Jul 2008, William Pitcock wrote:
If you do build-depends on gcc-multilib and g++-multilib, it should fix
this problem.
Ahhh, thanks - this was a quick and very helpful hint ...
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
Hi,
If you do build-depends on gcc-multilib and g++-multilib, it should fix
this problem.
William
On Mon, 2008-07-07 at 22:56 +0200, Andreas Tille wrote:
> Hi,
>
> as I described at the Debian Med mailing list [1] I have some
> trouble with a multiarch package. Charles Plessy and me prepared
>
10 matches
Mail list logo