Re: elfcopy: not found

why meta mode would be important here? wasn't that just a cache to make incremental builds faster


maybe

ln -svi /usr/bin/{obj,elf}copy

rather?


unsure if it fixed it fully. it did build. i hope that efi loader actually works too now

it likes to override path i guess (for clean env?) so it didn't take that symlink from /root/bin either...


irc said this:

04:50:59 < ketas-> hmm
04:51:01 < ketas-> elfcopy: not found
04:51:38 < ketas-> i haven't built current for a while
04:53:15 < ketas-> if that's that updating entry
04:53:28 < ketas-> i don't know what's the fix
04:54:55 < fbsdslack> <brooks> What are you trying to build?
                      I think you will need elfcopy for stand
                      in which case you may need to build
                      kernel-toolchain first
04:58:53 < ketas-> my mini variant of world+kernel, on 13, i
                   didn't change any config recently, it must
                   be change in current
04:59:12 < ketas-> what is that change?
05:00:57 < ketas-> something in src.conf bite me?
05:02:53 < fbsdslack> <brooks> Unconditionally installing
                      elftools objcopy as elfcopy and using
                      it for EFI because llvm-objcopy doesn’t
                      support PECOFF
05:27:10 < ketas-> hmm
...
06:36:46 < ketas-> where does one even get that,
                   usr.bin/objcopy ?
06:40:50 < fbsdslack> <brooks> yes (it was installed as
                      elfcopy long ago)
06:40:56 < fbsdslack> <brooks> :q
07:21:06 < ketas-> meh, i sleep first i guess
07:21:13 < ketas-> what has it, 14?
07:21:25 < ketas-> 13.5?

unsure about this all. when and where was elfcopy installed?

forum has this topic too

surely it doesn't exist in 13.4

also if it doesn't exist in host (or under that name) and is only needed for building. why doesn't it come from build itself? unless it exists in 14 and all people build 15 on 14


what to think of all this? it's pretty regular 13.4 too. i would be all alone if i would have custom system. but it's pretty stock. my only fault was to try build 15 on 13



On April 8, 2025 5:13:31 AM GMT+03:00, Minsoo Choo <minsoochoo0122@proton.me> wrote:
>
>
>
>
>
>Sent with Proton Mail secure email.
>
>On Monday, April 7th, 2025 at 9:50 PM, Sulev-Madis Silber <freebsd-current-freebsd-org111@ketas.si.pri.ee> wrote:
>
>> --- boot1.efi ---
>> SOURCE_DATE_EPOCH=1704067200 elfcopy -j .peheader -j .text -j .sdata -j .data -j .
>> dynamic -j .dynsym -j .rel.dyn -j .rela.dyn -j .reloc -j .eh_frame --output-target
>> =binary boot1.sym boot1.efi
>> sh: elfcopy: not found
>> 313.12 real 432.90 user 44.54 sys
>> 
>> make[1]: stopped in /root/files/fbsd/current/src
>> 
>> make: stopped in /root/files/fbsd/current/src
>> 29m18.50s real 43m6.42s user 5m47.07s sys
>> 
>> 
>> host is 13. unsure what that is? there's entry, 20250314, in updating but i can't figure out what that is and how to fix it. WITH_LLVM_TARGET_X86=yes maybe? unsure how to fix this on my own
>
>I had the same problem. Back up your src-env.conf and create a new one either empty or only with WITH_META_MODE=yes.
>
>Recompile and restore src-env.conf
>