Project

General

Profile

Actions

Bug #41950

closed

crimson compile

Added by YongSheng Zhang over 4 years ago. Updated over 4 years ago.

Status:
Can't reproduce
Priority:
Normal
Assignee:
-
Category:
-
Target version:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Can i know crimson-old use what version Seastar code at ceph-15 version?

When compile, output following option:

 [ 11%] Completed 'rocksdb_ext'
[ 11%] Built target rocksdb_ext

Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file libs/context/src/asm/jump_arm_aapcs_elf_gas.S.rej
patching file libs/context/src/asm/make_arm_aapcs_elf_gas.S
Reversed (or previously applied) patch detected!  Assume -R? [n] R
Apply anyway? [n] R
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file libs/context/src/asm/make_arm_aapcs_elf_gas.S.rej
patching file libs/context/src/asm/ontop_arm_aapcs_elf_gas.S
Reversed (or previously applied) patch detected!  Assume -R? [n] R
Apply anyway? [n] R

I will how to select ?

Do crimson-old only support menstore currently?

Actions #1

Updated by Kefu Chai over 4 years ago

  • Description updated (diff)
Actions #2

Updated by Kefu Chai over 4 years ago

  • Tracker changed from Backport to Bug
  • % Done set to 0
  • Regression set to No
  • Severity set to 3 - minor

i assume that you were trying to compile crimson-osd not crimson-old. please check the submodule of seastar to understand which seasrtar you need to use for compiling crimson-osd.

regarding to the build failure, i think the reason is that you compiled ceph before, and the local boost tree has already been applied the patch. you could just nuke your tree, and try again.

Actions #3

Updated by Kefu Chai over 4 years ago

  • Status changed from New to Can't reproduce
Actions

Also available in: Atom PDF