Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Feb 2012 10:41:59 -0800
From:      Tim Kientzle <tim@kientzle.com>
To:        Alexander Kabaev <kabaev@gmail.com>
Cc:        freebsd-current FreeBSD <freebsd-current@freebsd.org>, freebsd-ports@freebsd.org
Subject:   Re: rtld or lang/gcc cannot find libgcc_s.so.1
Message-ID:  <39D1C607-E186-4819-A562-E51B0366057A@kientzle.com>
In-Reply-To: <20120223121647.50ba7c6a@kan.dyndns.org>
References:  <20120221182850.GA20768@troutmask.apl.washington.edu> <20120221185754.GL55074@deviant.kiev.zoral.com.ua> <20120221194259.GA21185@troutmask.apl.washington.edu> <4F440E8B.9020306@FreeBSD.org> <20120221220053.GA44386@night.db.net> <20120221223251.GA23053@troutmask.apl.washington.edu> <Pine.GSO.4.64.1202211831220.22739@sea.ntplx.net> <5C146DC6-264B-43A9-9234-9E03315F3D33@kientzle.com> <20120223121647.50ba7c6a@kan.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Feb 23, 2012, at 9:16 AM, Alexander Kabaev wrote:

> On Tue, 21 Feb 2012 21:11:13 -0800
> Tim Kientzle <tim@kientzle.com> wrote:
> 
>> 
>> If I understand correctly, the libgcc in base is pretty stripped
>> down compared to "regular" libgcc, because most of that
>> stuff is in our libc instead. 
>> 
> 
> You understand it a bit wrong, but your conclusions are correct. libgcc
> in base is not stripped in any way and is supposed to be identical to
> one coming from upstream.

So where is __umodsi3 supposed to be defined for ARM?

In FreeBSD, libgcc refers to it but does not define it.
It's defined in libc.

I stumbled across this trying to link some freestanding
ARM code using the native cross-compilers.  The link
failed if I used -nostdlib because of a handful of symbols
such as this.

Tim




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39D1C607-E186-4819-A562-E51B0366057A>