On 17/11/2011 22:24, Goswin von Brederlow wrote:
> As said, the mangled symbol can differ between architectures. So if you
> take the symbol from one architecture then you need to demangle it there
> and mangle it again on the target architecture.
Ah, my mistake, I forgot that the purpose of the f
i might say "i once saw that using linuxrc is a powerful way to mount boot and root disk sets of any
kernel-supported media, but in the end grub and tfpt is wiser"
i might ask "are you rolling debian on mult. arches locally" ? if so debian does not need change if
you are?
and ranlib issues?
I would like to hear about the question, if you will.
"bootstrapping a partial system -- no kernel and no libc"
How does your local project indicate change wished or needed in debian's package build system? Or
in what way is it a request for special exception in build scripts?
I'm unsure why
Chow Loong Jin writes:
> On 16/11/2011 18:12, Goswin von Brederlow wrote:
>> [...]
>> How do you intend to build that fake lib?
>>
>> I guess it comes down to getting a list of symbols on an existing
>> architecture (or from the symbols file?), creating a "void symbol;" stub
>> for each and then
On 16/11/2011 18:12, Goswin von Brederlow wrote:
> [...]
> How do you intend to build that fake lib?
>
> I guess it comes down to getting a list of symbols on an existing
> architecture (or from the symbols file?), creating a "void symbol;" stub
> for each and then building a fake lib for the targ
Daniel Ruoso writes:
> I have been thinking about the bootstrapping of pakages lately. I am
> involved in bootstrapping a partial system -- no kernel and no libc --
> for some architectures for internal use. And I just thought that we
> could use one trick to help in the bootstrap of packages tha
Hi,
In my humble experience I just used debian/shlibs.local :-)
05.11.2011 01:30, Daniel Ruoso пишет:
I have been thinking about the bootstrapping of pakages lately. I am
involved in bootstrapping a partial system -- no kernel and no libc --
for some architectures for internal use. And I just t
Le vendredi 04 novembre 2011 à 17:30 -0400, Daniel Ruoso a écrit :
> The basic idea is creating "dummy libraries" that would serve for the
> linking but that had no code on it. This would allow the linking to
> happen -- of course this only helps in the case where the build
> process doesn't run a
8 matches
Mail list logo
