Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Helmut, On Fri, 2021-01-22 at 10:06 +0100, Helmut Grohne wrote: > > We already patch the compiler to call ld.bfd instead of ld, so we can change > > thename as you wish. > > Can you implement just this part and poke me once that has hit unstable?I can > send a patch for the next step then. I

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi, On Thu, Jan 21, 2021 at 08:30:10PM +0100, Abou Al Montacir wrote: > We already patch the compiler to call ld.bfd instead of ld, so we can change > the > name as you wish. Can you implement just this part and poke me once that has hit unstable? I can send a patch for the next step then. >

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Helmut, On Tue, 2021-01-12 at 22:05 +0100, Helmut Grohne wrote: > Hi, > I'm coming late to the party and I only understand a fraction of whatyou > wrote, but the parts I do understand make a lot of sense. Better late than never. I'm surprised by the analysis you made, it is quite deep and

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi, I'm coming late to the party and I only understand a fraction of what you wrote, but the parts I do understand make a lot of sense. On Mon, Nov 28, 2016 at 05:25:14PM -0800, Ben Longbons wrote: > On Mon, Nov 28, 2016 at 12:19 AM, Abou Al Montacir > wrote: > > For now you can use multi-arch

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Paul, > On top of this, the autopkgtest now seems broken (both in Debian and > Ubuntu): > https://ci.debian.net/packages/f/fpc/unstable/amd64/ > http://autopkgtest.ubuntu.com/packages/f/fpc (they were green in bionic) This looks like a make file was not generated. > # Make files are now

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Abou, On 15-12-17 09:26, Paul Gevers wrote: > But I think you didn't fix this in your upload to unstable, so Lintian > is now complaining loudly about all this, as is the MA hinter: > https://lintian.debian.org/maintainer/pkg-pascal-de...@lists.alioth.debian.org.html#fpc > and >

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Paul On Fri, 2017-12-15 at 09:26 +0100, Paul Gevers wrote: > Just curious, why did you upload to unstable without fixing these issues > > first? As I explained in my previous message, this will need to take a decision on either moving files to other packages or to put them in /usr/bin/. I

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Abou, On 11-12-17 10:20, Abou Al Montacir wrote: > This is now done, we now have unit packages co-installable. However, > There is still an issue with fp-compiler package. It contains some > executables that are installed in /usr/bin while is is MA same according > to this report >

Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Paul, On Wed, 2017-12-06 at 22:13 +0100, Paul Gevers wrote: > Hi Abou, > > On 06-12-17 10:26, Abou Al Montacir wrote: > > So for example > > /usr/lib/i386-linux-gnu/fpc/3.0.4/units/fpmkunit > > It is now quite easy to do this after my recent changes. > > > > Is that OK or do we need to do it

Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Abou, On 06-12-17 10:26, Abou Al Montacir wrote: > So for example > /usr/lib/i386-linux-gnu/fpc/3.0.4/units/fpmkunit > It is now quite easy to do this after my recent changes. > > Is that OK or do we need to do it other way, maybe in a simpler manner? For whatever it is worth, that sounds

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi All, On Wed, 2017-11-15 at 15:33 +0100, Abou Al Montacir wrote: ... > Upstream solves this by using a different base dir. We can for instance > replace > /usr/lib/${DEB_PACKAGE_NAME}/${DEB_UPSTREAM_MAIN_VERSION}by/usr/lib/${FPCTARGE >

Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Paul, On Wed, 2017-11-15 at 21:01 +0100, Paul Gevers wrote: > I am perfectly fine with you experimenting in experimental. > > I have a question regarding the patch, as you change generated *.inc > files, can't you generate those in the rules file instead of in the > patch? That's a very good

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Abou, On 14-11-17 23:21, Abou Al Montacir wrote: > I did not upload this as I did not test it extensively and I fear this is a > quite big change that may require manual upload for many arches is not tested > extensively before it is uploaded. I'd prefer to have it in experimental first > also

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Peter and All, On Tue, 2017-11-14 at 23:32 +, peter green wrote: > Going to experimental before unstable with aggressive changes certainly makes > sense. IIRC experimental buildds only use build-depends from experimental when > required to satisfy version constraints, so by changing version

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

On 14/11/17 22:21, Abou Al Montacir wrote: Hi Paul, and All, I've just pushed a commit [1] that I hope will improve the situation of MA support. In this commit I've moved units from ${LIB_DIR}/units/${FPCTARGET}-${FPCARCH} to ${LIB_DIR}/units/${FPCTARGET}-${FPCARCH}/'$${PACKAGE_NAME}' where

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Paul, and All, I've just pushed a commit [1] that I hope will improve the situation of MA support. In this commit I've moved units from ${LIB_DIR}/units/${FPCTARGET}-${FPCARCH} to ${LIB_DIR}/units/${FPCTARGET}-${FPCARCH}/'$${PACKAGE_NAME}' where 

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Paul and All, On Wed, 2016-11-30 at 22:29 +0100, Paul Gevers wrote: > Control: tags 845504 pending patch > > Hi, > > On 29-11-16 20:55, Abou Al Montacir wrote: > > The dependency on linker package could be fixed easily as you said. > But how should we do this in reality? > Depends:  binutils

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Ben & All, On Fri, 2016-12-09 at 20:40 -0800, Ben Longbons wrote: > On Fri, Dec 9, 2016 at 1:46 PM, Paul Gevers wrote: > > I am trying to understand you shell scrip > You may find it easier to just run it and inspect the resulting > `.deb`s, then refer to the script only

Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

On Fri, Dec 9, 2016 at 1:46 PM, Paul Gevers wrote: > I am trying to understand you shell script You may find it easier to just run it and inspect the resulting `.deb`s, then refer to the script only when you want to see where a specific path/package is handled. > Just to make

Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Ben On 03-12-16 03:39, Ben Longbons wrote: > I got it completely working now! I did have to repack > binutils-{i586,x86-64}-linux-gnu though. > > Tested that I can generate both i386 and aarch64 binaries, solely by > specifying `-P`. Still haven't actually tested linking with libc, for > that

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

I got it completely working now! I did have to repack binutils-{i586,x86-64}-linux-gnu though. Tested that I can generate both i386 and aarch64 binaries, solely by specifying `-P`. Still haven't actually tested linking with libc, for that we'll need to do something nasty about /lib32/ (probably

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Okay, I've got it *almost* working: https://gist.github.com/o11c/cf98115ba716ebdd1dc2cc75b290f321 I'm still getting errors from update-alternatives in postinst, but I *think* everything else is right - at least, things that weren't completely wrong before (there are a lot of those). I have

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi, On 29-11-16 02:25, Ben Longbons wrote: > On Mon, Nov 28, 2016 at 12:19 AM, Abou Al Montacir > wrote: >> For now you can use multi-arch to install fp-compiler > > No, you can't (that was the first thing I thought of): > fp-compiler:i386 depends on binutils:i386 rather

Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Control: tags 845504 pending patch Hi, On 29-11-16 20:55, Abou Al Montacir wrote: > The dependency on linker package could be fixed easily as you said. But how should we do this in reality? Depends: binutils | binutils-aarch64-linux-gnu | binutils-alpha-linux-gnu | etc? > For the

Bug#845498: [Pkg-pascal-devel] Bug#845498: Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Hi Ben, Wow, I'm impressed with your analysis, you really hit many points that are real problem for going multiarch. The dependency on linker package could be fixed easily as you said. For the /etc/fpc.cfg, this could be solved by adding liens like: # path to the gcclib#ifdef

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

On Mon, Nov 28, 2016 at 12:19 AM, Abou Al Montacir wrote: > For now you can use multi-arch to install fp-compiler No, you can't (that was the first thing I thought of): fp-compiler:i386 depends on binutils:i386 rather than binutils-i586-linux-gnu, and binutils:i386 isn't

Bug#845498: [Pkg-pascal-devel] Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Dear Ben, Thanks for reporting this bug. We are aware of this limitation and we have a plan for fixing this, but unfortunately we lack man power to put this in place. One of my own goals is to make it possible to compile Android applications as easy as installing a virtual package that polls

Bug#845498: /usr/bin/fpc-3.0.0: Provide cross-compilers

Package: fp-compiler-3.0.0 Version: 3.0.0+dfsg-9 Severity: wishlist File: /usr/bin/fpc-3.0.0 Dear Maintainer, According to `fpc -help`, -P Set target CPU (arm,avr,i386,jvm,m68k,mips,mipsel,powerpc,powerpc64,sparc,x86_64) However, if I try any of those besides the current CPU, I get: