Re: Getting "objcopy: unsupported e_type" after buildworld

Julio Merino <[email protected]>
Newsgroups gmane.os.freebsd.devel.ppc
Message-ID <CADyfeQUKTwD7ekmn_pV89k=60RM3Pd3ibX0b2uv4L5VZP0=Uig@mail.gmail.com>
I think I've found the problem. And... wow. The compiler that ships with
12.1-RELEASE seems to think it's targeting a little-endian powerpc64
machine... and then libelf gets built the wrong way and mayhem ensues.

I've filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252720 with
the details.

On Thu, Jan 14, 2021 at 5:45 PM Julio Merino <[email protected]> wrote:

> Huh. I just encountered more breakage:
>
> g5:~> pkg info
> pkg: failed to get the note section
> pkg: failed to get the note section
> pkg: Unable to determine ABI
> pkg: Cannot parse configuration file!
>
> Something seems to be very wrong after this buildworld/installworld
> upgrade...
>
> On Wed, Jan 13, 2021 at 9:33 PM Julio Merino <[email protected]> wrote:
>
>> Hi!
>>
>> On the PowerMac G5 I have, I first installed 12.1-RELEASE (ppc64) as
>> found on the website.
>>
>> Now, I just went ahead and built the world from a Git checkout of the
>> stable/12 branch (at commit 49038d1723a9d45e064f482d510230ed5395b675). The
>> whole process went smoothly and I was able to upgrade to 12.2-STABLE just
>> fine.
>>
>> However... on a second attempt to clean-build the world after the
>> upgrade, I'm getting the following very early on in the process:
>>
>> ===> kerberos5/tools/make-roken (obj,all,install)
>> objcopy --strip-debug --add-gnu-debuglink=make-roken.debug
>>  make-roken.full make-roken
>> objcopy: unsupported e_type
>> *** [make-roken] Error code 1
>>
>> Any thoughts?
>>
>> Thank you
>>
>> --
>> jmmv.dev
>>
>
>
> --
> jmmv.dev
>


-- 
jmmv.dev
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.