> Do not know how you progressed along this way. Maybe, you could try
> first to see whether you can get gcc to do what you want by passing
> flags to the command line, then try to automate passing those flags
> using specs.
>
> Maybe the -L flag is enough, but you have also to specify the "crtxx"
Le 12/12/2013 00:13, John Burrell a écrit :
>>> Now I need to build binutils and make sure that it sees the correct
>>> toolchain -
>> You have it backwards. Binutils, then gcc, then glibc. Not glibc,
>> then binutils.
>>
>> What exactly are you going after.
>
> It's an experiment. I wondered wh
On Wed, Dec 11, 2013 at 3:13 PM, John Burrell wrote:
>>> Now I need to build binutils and make sure that it sees the correct
>>> toolchain -
>>
>> You have it backwards. Binutils, then gcc, then glibc. Not glibc,
>> then binutils.
>>
>> What exactly are you going after.
>
> It's an experiment. I w
>> Now I need to build binutils and make sure that it sees the correct
>> toolchain -
>
> You have it backwards. Binutils, then gcc, then glibc. Not glibc,
> then binutils.
>
> What exactly are you going after.
It's an experiment. I wondered whether one could build the four core packages
in the
On Dec 10, 2013, at 12:00 PM, John Burrell wrote:
> Now I need to build binutils and make sure that it sees the correct
> toolchain -
You have it backwards. Binutils, then gcc, then glibc. Not glibc,
then binutils.
What exactly are you going after.
If you are after building a kernel only
.
> As how to automate the setting of rpath under gcc, I guess you can with
> the specs, but I have never done it.
these lines in the specs file:
*link_libgcc:
%D
can be changed to:
*link_libgcc:
%D -rpath /lib/%M
Apparently %M expands to either ../lib or ../lib64 depending on 32 or 64 bit
ar
Le 10/12/2013 23:38, John Burrell a écrit :
> .
>> I do not quite understand what you have done. Your first build was linux
>> headers then glibc? Without doing anything with gcc?
> Well I'm building the archive files using a machine running LFS so gcc is
> version 4.8.2
>
>> If so, you cannot exp
.
>>
> I do not quite understand what you have done. Your first build was linux
> headers then glibc? Without doing anything with gcc?
Well I'm building the archive files using a machine running LFS so gcc is
version 4.8.2
>If so, you cannot expect
> gcc to know about the glibc you built. All t
Le 10/12/2013 19:00, John Burrell a écrit :
> I'm trying to create some package archives.
>
> I've started with linux_headers. I then did glibc and used
> --with-headers= so it picked up the correct
> headers.
>
> Now I need to build binutils and make sure that it sees the correct toolchain
>
I'm trying to create some package archives.
I've started with linux_headers. I then did glibc and used
--with-headers= so it picked up the correct
headers.
Now I need to build binutils and make sure that it sees the correct toolchain -
I created the specs file and edited it so it points to the
10 matches
Mail list logo
