Hi Jan and Dago,
Yes, that was it.  The recipe now builds.

Thanks,
Jake


On 01/03/18 01:39, Jan Holzhueter via maintainers wrote:
Hi,
try with NOGITPATCH += 1
git stuff might be broken maybe?




Am 03.01.18 um 10:34 schrieb Dagobert Michelsen via maintainers:
Hi Jake,

Am 03.01.2018 um 04:31 schrieb Jake Goerzen <[email protected]>:
I have a recipe I can build unstable9x successfully, but on unstable9s it gets 
stuck at applying patch…
I can reproduce this. It looks like an issue in the gluecode during fork:

unstable9s% pstack 27002
27002:  git am --ignore-space-change --ignore-whitespace /home/dam/mgar/pkg/to
  ff3dcba4 lwp_park (0, 0, 0)
  ff3d3d3c s9_lwp_park (0, 0, 0, 0, 0, 0) + 6c
  ff3dcb08 s9_handler (0, 0, 0, 0, 0, 0) + 90
  fec811bc mutex_lock_queue (fec98c04, 0, fed82408, 0, 0, 0) + 104
  fec818cc mutex_lock_internal (0, 0, fec90000, 0, 0, 0) + 610
  fed58a28 atfork_append (0, 0, fedd6044, fed82404, fed82408, 0) + 4
  fed58b94 pthread_atfork (0, 0, fedd6044, ffe77590, 188800, 188a2c) + 24
  fedd6114 solaris_locking_setup (fedd6044, 0, fedd5fe0, 400, fef5f140, 400) + 
90
  fed58d70 run_postfork_child (fed823f0, fed82408, 2526c, fec7cfa8, 5, 0) + 24
  fec7cfa8 fork1    (1, 1afc8, 0, 0, 0, 0) + f4
  fec7d05c fork     (0, 4, ffbff3c0, 223544, 1b5d80, 0) + 28
  00151534 start_command (ffbff4a4, 0, 9, 0, 0, 0) + 220
  00151b80 run_command (ffbff4a4, 0, 20, 0, 8, 8) + 4
  00151cac run_command_v_opt (ffbff660, 28, 1e6c00, 223544, 1b5d80, 0) + 14
  000212a8 ???????? (ffbff660, ffffffff, 1fc000, 223544, 1aadd0, 0)
  00021308 ???????? (ffbff63c, ffbff640, ffbffa73, 1dadc8, 0, 1b5000)
  00021448 main     (ffbff660, ffbff63c, 1fc818, 1b6fe8, ffbff640, ffbff7a4) + 
f8
  0001f840 _start   (0, ffbff65c, 1, ff3dca78, ff3ee850, ff3ee000) + 108


Maybe there is a patch, but I am a bit reluctant as this ususally means raising 
libc-level.


Best regards

   — Dago


Reply via email to