Jump to content

vivekjindal20

Members
  • Content Count

    8
  • Joined

  • Last visited

  1. Build was complete and problem was resolved. Please mark as resolved and add the tag Metro?
  2. I did some research, mmxext is a part of mmx hence applied automatically and I think I need to pass more CFLAGS. I restarted my build again with below flags. CFLAGS="-march=broadwell -mabm -mno-adx -mno-aes -mno-avx -mno-avx2 -mno-bmi -mno-bmi2 -mno-f16c -mno-fma -mno-xsave -mno-xsaveopt -O2 -pipe" CXXFLAGS="${CFLAGS}" FFLAGS="${CFLAGS}" FCFLAGS="${CFLAGS}" CPU_FLAGS_X86="mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3"
  3. I told Metro (inserted cp commands in steps/unpack.spec file) to copy my customized make.defaults file to overwrite in intel64-broadwell directory just after git sync command. All went well, stage3 was built successfully with my customized CPU flags but 1 problem happened. Somehow 1 flag extra was automatically added. What I told Metro: "mmx popcnt sse sse2 sse4_1 sse4_2 ssse3" What came out in build.json: "mmx popcnt sse sse2 sse4_1 sse4_2 ssse3 mmxext" Please suggest. What am I missing?
  4. I need to make some corrections on what I said here. Metro doesn't use running system's portage infrastructure. Metro downloads fresh portage snapshot and extracts it into working directory as specified in ~/.metro. Changes have to be made there, for instance: /var/tmp/metro/work/funtoo-stable/stage1-intel64-broadwell-funtoo-stable-2016-12-02/usr/portage/profiles/funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-broadwell In that case re-running emerge --sync would be harmless as well.
  5. I was reading the metro etc files. From common.conf it is obvious that Metro uses the path I stated above. I going to make changes and will share the results.
  6. Thank you Oleg. You have determined the root cause. My last question is, how can I tell Metro to use specific flags? I think here, right? /usr/portage/profiles/funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/intel64-broadwell/make.defaults
  7. I used metro remote build guide. Followed steps in funtoo.org/Metro. Here is my resultant directory structure. funtooded funtoo-stable # find . . ./snapshots ./snapshots/portage-2016-11-30.tar.xz ./snapshots/portage-latest.tar.xz ./snapshots/portage-2016-12-01.tar.xz ./x86-64bit ./x86-64bit/intel64-broadwell ./x86-64bit/intel64-broadwell/.control ./x86-64bit/intel64-broadwell/.control/strategy ./x86-64bit/intel64-broadwell/.control/strategy/build ./x86-64bit/intel64-broadwell/.control/strategy/seed ./x86-64bit/intel64-broadwell/.control/.multi_progress ./x86-64bit/intel64-broadwell/.contro
  8. Hi, I am trying to install funtoo on my chromebook. I have Intel Celeron 3215. I am also running funtoo on my Linode. I noticed that funtoo wasn't providing the broadwell stage3 tarballs so I decided to use Metro and build a broadwell tarball. (I already tried to use haswell tarball, same problem "Illegal Instruction"). Once my broadwell tarball was ready I decided to use that one. I am getting the same error on that one too ("Illegal Instruction"). Did my Metro built tarball came out wrong? Please help. Additional information: file ./bin/bash ./bin/bash: ELF 64-bit LSB
×
×
  • Create New...