Build gn occurs erros on mips64el platform
Reported by
wangqing...@loongson.cn,
Aug 31 2017
|
|||
Issue description
Chrome Version (from the about:version page): 62.0.3202.0
Is this the most recent version: latest
OS + version: Fedora21
CPU architecture (32-bit / 64-bit): 64-bit
What steps will reproduce the problem?
(1) clone chromium src.
(2) entry src/.
(3) run: python tools/gn/bootstrap/bootstrap.py --gn-gen-args "${GN_CONFIG[*]}"
occurs errors:
[367/367] LINK gn
FAILED: gn
c++ -pthread -o gn -Wl,--start-group tools/gn/gn_main.o libevent.a base.a xdg_user_dirs.a gn_lib.a dynamic_annotations.a -Wl,--end-group -lrt -latomic
base/task_scheduler/task_scheduler_impl.o:在函数‘base::internal::TaskSchedulerImpl::Start(base::TaskScheduler::InitParams const&)’中:
task_scheduler_impl.cc:(.text+0x27c):对‘base::GetFieldTrialParamValue(std::string const&, std::string const&)’未定义的引用
task_scheduler_impl.cc:(.text+0x288):对‘base::GetFieldTrialParamValue(std::string const&, std::string const&)’未定义的引用
base/task_scheduler/task_scheduler_impl.o:在函数‘base::internal::TaskSchedulerImpl::CreateTaskRunnerWithTraits(base::TaskTraits const&)’中:
task_scheduler_impl.cc:(.text+0xb28):对‘base::internal::SchedulerWorkerPool::CreateTaskRunnerWithTraits(base::TaskTraits const&)’未定义的引用
task_scheduler_impl.cc:(.text+0xb40):对‘base::internal::SchedulerWorkerPool::CreateTaskRunnerWithTraits(base::TaskTraits const&)’未定义的引用
base/task_scheduler/task_scheduler_impl.o:在函数‘base::internal::TaskSchedulerImpl::CreateSequencedTaskRunnerWithTraits(base::TaskTraits const&)’中:
task_scheduler_impl.cc:(.text+0xb98):对‘base::internal::SchedulerWorkerPool::CreateSequencedTaskRunnerWithTraits(base::TaskTraits const&)’未定义的引用
task_scheduler_impl.cc:(.text+0xbb0):对‘base::internal::SchedulerWorkerPool::CreateSequencedTaskRunnerWithTraits(base::TaskTraits const&)’未定义的引用
base/task_scheduler/task_scheduler_impl.o:在函数‘base::internal::TaskSchedulerImpl::PostDelayedTaskWithTraits(tracked_objects::Location const&, base::TaskTraits const&, base::OnceCallback<void ()>, base::TimeDelta)’中:
task_scheduler_impl.cc:(.text+0xca4):对‘base::internal::SchedulerWorkerPool::PostTaskWithSequence(std::unique_ptr<base::internal::Task, std::default_delete<base::internal::Task> >, scoped_refptr<base::internal::Sequence>)’未定义的引用
task_scheduler_impl.cc:(.text+0xcb0):对‘base::internal::SchedulerWorkerPool::PostTaskWithSequence(std::unique_ptr<base::internal::Task, std::default_delete<base::internal::Task> >, scoped_refptr<base::internal::Sequence>)’未定义的引用
base/task_scheduler/scheduler_worker_pool_impl.o:在函数‘base::internal::SchedulerWorkerPoolImpl::SchedulerWorkerDelegateImpl::OnMainEntry(base::internal::SchedulerWorker*)’中:
scheduler_worker_pool_impl.cc:(.text+0x590):对‘base::internal::SchedulerWorkerPool::BindToCurrentThread()’未定义的引用
scheduler_worker_pool_impl.cc:(.text+0x594):对‘base::internal::SchedulerWorkerPool::BindToCurrentThread()’未定义的引用
scheduler_worker_pool_impl.cc:(.text+0x59c):对‘base::internal::SetBlockingObserverForCurrentThread(base::internal::BlockingObserver*)’未定义的引用
scheduler_worker_pool_impl.cc:(.text+0x5a0):对‘base::internal::SetBlockingObserverForCurrentThread(base::internal::BlockingObserver*)’未定义的引用
scheduler_worker_pool_impl.cc:(.text+0x6a8):对‘base::internal::SchedulerWorkerPool::BindToCurrentThread()’未定义的引用
base/task_scheduler/scheduler_worker_pool_impl.o:在函数‘base::internal::SchedulerWorkerPoolImpl::SchedulerWorkerPoolImpl(std::string const&, base::ThreadPriority, base::internal::TaskTracker*, base::internal::DelayedTaskManager*)’中:
scheduler_worker_pool_impl.cc:(.text+0x1408):对‘base::internal::SchedulerWorkerPool::SchedulerWorkerPool(base::internal::TaskTracker*, base::internal::DelayedTaskManager*)’未定义的引用
scheduler_worker_pool_impl.cc:(.text+0x1430):对‘base::internal::SchedulerWorkerPool::SchedulerWorkerPool(base::internal::TaskTracker*, base::internal::DelayedTaskManager*)’未定义的引用
collect2: 错误:ld 返回 1
ninja: build stopped: subcommand failed.
Command '['ninja', '-C', '/tmp/tmpvgL8B6', 'gn']' returned non-zero exit status 1
,
Sep 7 2017
Unable to triage this issue from TE-End, hence adding "TE-NeedsTriageHelp" label for further triage.
,
Sep 7
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by wangqing...@loongson.cn
, Aug 31 2017