2018-01-19 9:23 GMT+01:00 Abou Al Montacir :
> To be clear: It's not just a matter of having correct /etc/fpc.cfg --
> the fpmake also needs to know the root location of FPC units. (You
> would have to ask fpmake authors why they did it like this.) But that
> is why we have this complication with $
Hi Michalis,
On Thu, 2018-01-18 at 20:56 +0100, Michalis Kamburelis wrote:
> 2018-01-18 14:44 GMT+01:00 Abou Al Montacir :
> > Doing
> >
> > ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4"
> >
> > Why do we need this? FPC should use the /etc/fpc.cfg to get this, why do we
> > need to explicitly p
Hi Michalis,
On Thu, 2018-01-18 at 22:25 +0100, Michalis Kamburelis wrote:
> 2018-01-18 20:56 GMT+01:00 Michalis Kamburelis :
> > So, we should get to the point where CGE (or any other package
> > using fpmake) can be compiled by simple
> >
> > ~~~
> > unset FPCDIR
> > fpc fpmake.pp
> > ./fpmake #
2018-01-18 20:56 GMT+01:00 Michalis Kamburelis :
> So, we should get to the point where CGE (or any other package
> using fpmake) can be compiled by simple
>
> ~~~
> unset FPCDIR
> fpc fpmake.pp
> ./fpmake # without any additional options like --globalunitdir
> ~~~
>
I created a "simplest possible
2018-01-18 14:44 GMT+01:00 Abou Al Montacir :
> Doing
>
> ./fpmake --globalunitdir="/usr/lib/fpc/3.0.4"
>
> Why do we need this? FPC should use the /etc/fpc.cfg to get this, why do we
> need to explicitly pass this?
>
Hi Abou,
I think you're very right here -- the option "--globalunitdir XXX"
s
clone 887575 -1
assign -1 src:fpc
retitle -1 fpc MA setup breaks some reverse dependency builds
found -1 3.0.4+dfsg-13
block 887575 by -1
thanks
Hi
On 18-01-18 14:44, Abou Al Montacir wrote:
> On Thu, 2018-01-18 at 06:43 +0100, Michalis Kamburelis wrote:
>> The problem is caused by the different
Hi Michalis,
On Thu, 2018-01-18 at 06:43 +0100, Michalis Kamburelis wrote:
> The problem is caused by the different directories used by new FPC
> 3.0.4 packages (compared to previous versions of FPC in Debian).
I must admit that I was expecting many packages to break as the change is too
big.But I
The problem is caused by the different directories used by new FPC
3.0.4 packages (compared to previous versions of FPC in Debian).
Doing
./fpmake --globalunitdir="/usr/lib/fpc/3.0.4"
doesn't work, since /usr/lib/fpc/3.0.4 does not exist. This works:
./fpmake --globalunitdir="/usr/lib/x86_6
Source: castle-game-engine
Version: 6.2+dfsg1-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/castle-game-engine.html
...
--- Building
dh_testdir
# Build the real engine
/usr/bin/make all
make[1]: Entering directory '/build/1st/castle-game-engine-6.2+dfsg1'
9 matches
Mail list logo
