Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2012-09

Fwd: Access violation when building the trunk

9 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Jonas Maebe

Message sent to the wrong address (fpc-devel-bounces instead of fpc-devel)

Earlier message 30 lines
From: "Gennadiy Poryev" Date: 2 Sep 2012 11:27:34 GMT+02:00 To: Subject: Access violation when building the trunk Hi. My setup involves building native x64 2.6.0 compiler using 2.6.0 crosscompiler from i386. This is just for convenience. And it succeeded. Then I was routinely building the latest trunk using the above mentioned native x64 2.6.0 as the starting compiler. It worked well some weeks prior, but now this happens: [ 1%] Skipped package a52 which has been disabled for target arm-wince [ 2%] Skipped package amunits which has been disabled for target arm-wince [ 3%] Skipped package aspell which has been disabled for target arm-wince [ 4%] Skipped package bfd which has been disabled for target arm-wince [ 5%] Skipped package cairo which has been disabled for target arm-wince [ 6%] Skipped package cdrom which has been disabled for target arm-wince Start compiling package chm for target arm-wince. The installer encountered the following error: Access violation make[2]: *** [all] Error 1 make[2]: Leaving directory `C:/Dev/FPC/sources/packages' make[1]: *** [packages_all] Error 2 make[1]: Leaving directory `C:/Dev/FPC/sources' make: *** [build-stamp.arm-wince] Error 2 And I have no clue how to produce more verbose/debug data. Any suggestions? // Gennadiy.

Reply by email

Gennadiy Poryev

Hi.

My setup involves building native x64 2.6.0 compiler using 2.6.0 crosscompiler from i386. This is just for convenience. And it succeeded. Then I was routinely building the arm-wince cross-compiler from the latest trunk using the above mentioned native x64 2.6.0 as the starting compiler. This method worked well some weeks prior, but now this happens:

[ 1%] Skipped package a52 which has been disabled for target arm-wince [ 2%] Skipped package amunits which has been disabled for target arm-wince [ 3%] Skipped package aspell which has been disabled for target arm-wince [ 4%] Skipped package bfd which has been disabled for target arm-wince [ 5%] Skipped package cairo which has been disabled for target arm-wince [ 6%] Skipped package cdrom which has been disabled for target arm-wince Start compiling package chm for target arm-wince.
The installer encountered the following error:
Access violation
make[2]: *** [all] Error 1
make[2]: Leaving directory `C:/Dev/FPC/sources/packages' make[1]: *** [packages_all] Error 2
make[1]: Leaving directory `C:/Dev/FPC/sources'
make: *** [build-stamp.arm-wince] Error 2

And I have no clue how to produce more verbose/debug data. Any suggestions?

// Gennadiy.

Reply by email

Jonas Maebe
to Gennadiy Poryev
Gennadiy Poryev wrote 10 lines
The installer encountered the following error: Access violation make[2]: *** [all] Error 1 make[2]: Leaving directory `C:/Dev/FPC/sources/packages' make[1]: *** [packages_all] Error 2 make[1]: Leaving directory `C:/Dev/FPC/sources' make: *** [build-stamp.arm-wince] Error 2 And I have no clue how to produce more verbose/debug data. Any suggestions?

It's probably a bug in fpmake. You should be able to work around it by removing FPMAKEOPT="-T X".

Jonas

Reply by email

Gennadiy Poryev
to Jonas Maebe: It's probably a bug in fpmake. You should be able to work around it by removing…
Show quoted text 13 lines
> The installer encountered the following error: > Access violation > make[2]: *** [all] Error 1 > make[2]: Leaving directory `C:/Dev/FPC/sources/packages' > make[1]: *** [packages_all] Error 2 > make[1]: Leaving directory `C:/Dev/FPC/sources' > make: *** [build-stamp.arm-wince] Error 2 > > And I have no clue how to produce more verbose/debug data. > Any suggestions? It's probably a bug in fpmake. You should be able to work around it by removing FPMAKEOPT="-T X".

It'd be helpful if you point out where to find that. Quick search for FPMAKEOPT= did not yield anything.

Reply by email

Jonas Maebe
to Gennadiy Poryev

Gennadiy Poryev wrote on Mon, 03 Sep 2012:

Show quoted text 16 lines
> > The installer encountered the following error: > > Access violation > > make[2]: *** [all] Error 1 > > make[2]: Leaving directory `C:/Dev/FPC/sources/packages' > > make[1]: *** [packages_all] Error 2 > > make[1]: Leaving directory `C:/Dev/FPC/sources' > > make: *** [build-stamp.arm-wince] Error 2 > > > > And I have no clue how to produce more verbose/debug data. > > Any suggestions? > > It's probably a bug in fpmake. You should be able to work around it by > removing FPMAKEOPT="-T X". It'd be helpful if you point out where to find that. Quick search for FPMAKEOPT= did not yield anything.

FPMAKEOPT= is an option you can specify to "make" when building FPC. If you are not explicitly specifying it, then it's not active. In that case, I don't know what the cause is of the crash you are experiencing (other than that it's presumably also casued by r22275).

Jonas

Reply by email

Gennadiy Poryev
to Jonas Maebe
Show quoted text 21 lines
>> > The installer encountered the following error: >> > Access violation >> > make[2]: *** [all] Error 1 >> > make[2]: Leaving directory `C:/Dev/FPC/sources/packages' >> > make[1]: *** [packages_all] Error 2 >> > make[1]: Leaving directory `C:/Dev/FPC/sources' >> > make: *** [build-stamp.arm-wince] Error 2 >> > >> > And I have no clue how to produce more verbose/debug data. >> > Any suggestions? >> >> It's probably a bug in fpmake. You should be able to work around it >> by removing FPMAKEOPT="-T X". > > It'd be helpful if you point out where to find that. Quick search for > FPMAKEOPT= did not yield anything. FPMAKEOPT= is an option you can specify to "make" when building FPC. If you are not explicitly specifying it, then it's not active. In that case, I don't know what the cause is of the crash you are experiencing (other than that it's presumably also casued by r22275).

Is there a way to locally prevent this particular package from being compiled and included in installation? I don't use it anyway.

Reply by email

Jonas Maebe
to Gennadiy Poryev

Gennadiy Poryev wrote on Mon, 03 Sep 2012:

Is there a way to locally prevent this particular package from being compiled and included in installation? I don't use it anyway.

You can edit packages/fpmake_proc.inc and fpmake_add.inc. I doubt it will help though. The problem is probably not caused by that package in particular, but by a generic bug in fpmake that will probably also be triggered while compiling other packages. It may even not always be the same package that triggers it.

Jonas

Reply by email

Gennadiy Poryev
to Jonas Maebe
Show quoted text 7 lines
> Is there a way to locally prevent this particular package from being > compiled and included in installation? I don't use it anyway. You can edit packages/fpmake_proc.inc and fpmake_add.inc. I doubt it will help though. The problem is probably not caused by that package in particular, but by a generic bug in fpmake that will probably also be triggered while compiling other packages. It may even not always be the same package that triggers it.

Finally I've replaced 2.6.0's fpcmake.exe with the one from 2.7.1 and it turned out to be much more talkative ( http://bugs.freepascal.org/view.php?id=22784 ) than just throwing "Access violation".

Thanks for the hint :)

Reply by email