Re: [lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-15 Thread René Nyffenegger


I'm afraid your problem is just a stupid typo somewhere in either 
glibc, binutils or gcc, either in chapter 5 or 6.


Tim, you're right. I must have overlooked something. I was able to build 
Glibc in the second step now.

--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-15 Thread René Nyffenegger



you seem to be misreading what the book says.  The current stable
book is 8.1, and the following specific minimum versions are
mentioned:

gcc-4.7 (you imply versions > 4.4.1 are not tested)
glibc-2.11.

As Pierre said, gcc-7.3.0 did not exist when 8.1 was released.  In
practice it should be fine for building 8.1

And glibc-2.26 is the highest version which had been tested, so it
is explicitly OK.

In other words, the versions you have mentioned are fine.  We also
say "Earlier versions of the listed software packages may work, but
have not been tested."

The things which commonly break a build are:

  /bin/sh not pointing to bash.

  host systems without bison (i.e. with a different yacc).

  mawk instead of gawk.

  missing packages from the list of requirements.


I probably have to somehow first bild an old version of gcc and glibc
before I can even think about
trying to create my own LFS.


No, building an older version of gcc is a recipe for pain - you can
probably go back one or two versions, but sooner or later the
current version will not understand the older source, particularly
in g++).

ĸen

Ken, thanks for the clarificatino.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-14 Thread Ken Moffat
On Wed, Feb 14, 2018 at 02:28:06PM +0100, René Nyffenegger wrote:
> 
>I also paid too little attention: my gcc version is 7.3.0 and the book
>explicitely states that versions +4.4.1 are not recommended.
>Similar thing with glibc which is version 2.26 (versions +2.10.1 not being
>recommended).
> 
Hi René,

you seem to be misreading what the book says.  The current stable
book is 8.1, and the following specific minimum versions are
mentioned:

gcc-4.7 (you imply versions > 4.4.1 are not tested)
glibc-2.11.

As Pierre said, gcc-7.3.0 did not exist when 8.1 was released.  In
practice it should be fine for building 8.1

And glibc-2.26 is the highest version which had been tested, so it
is explicitly OK.

In other words, the versions you have mentioned are fine.  We also
say "Earlier versions of the listed software packages may work, but
have not been tested."

The things which commonly break a build are:

 /bin/sh not pointing to bash.

 host systems without bison (i.e. with a different yacc).

 mawk instead of gawk.

 missing packages from the list of requirements.

>I probably have to somehow first bild an old version of gcc and glibc
>before I can even think about
>trying to create my own LFS.
> 

No, building an older version of gcc is a recipe for pain - you can
probably go back one or two versions, but sooner or later the
current version will not understand the older source, particularly
in g++).

ĸen
-- 
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
 - Unseen Academicals
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-14 Thread Tim Tassonis

Hi René

On 02/14/2018 02:28 PM, René Nyffenegger wrote:


Please do not top post. According to what you say, there should be no 
need to
add libc_cv_ctors_header=yes. Looking at my logs, I have, during the 
configure

stage:
--
checking whether to use .ctors/.dtors header and trailer... no
--
in both chapter 5 and chapter 6 glibc, and my build went smoothly.
There was a thread in last September about the same issue, and the OP 
had the

following in configure:
--
checking for .set assembler directive... no
checking linker support for protected data symbol... no
--
while I have 'yes' to these 2 items. What do you have (it's just a few 
lines

before configure stops)? Can you also check in chapter 5?

If there is a no, I guess you'll have to start again chapter 5. Or 
maybe you

just missed some symlink (section 6.6)...

Pierre

Please excuse my previous top posting.

When I tried to build LFS, I probably paid too little attentionto the 
details and error messages.


I completely started the build process from scratch and realized that as 
soon as in the 2nd build
of glibc I cannot go further. When ./configure tries to execute ./a.out, 
./a.out seg faults. This is,

what I assume, I missed.

I also paid too little attention: my gcc version is 7.3.0 and the book 
explicitely states that versions +4.4.1 are not recommended.
Similar thing with glibc which is version 2.26 (versions +2.10.1 not 
being recommended)



I don't think this is your problem, as I built the whole newest lfs 
toolchain with

- gcc 5.3.0
- glibc 2.23

After you built the toolchain, and verified its usability, those 
versions should not be a problem anymore, as you will build against 
7.3.0 und 2.27 anyway.


I'm afraid your problem is just a stupid typo somewhere in either glibc, 
binutils or gcc, either in chapter 5 or 6.


Bye
Tim
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-14 Thread René Nyffenegger


Please do not top post. According to what you say, there should be no 
need to
add libc_cv_ctors_header=yes. Looking at my logs, I have, during the 
configure

stage:
--
checking whether to use .ctors/.dtors header and trailer... no
--
in both chapter 5 and chapter 6 glibc, and my build went smoothly.
There was a thread in last September about the same issue, and the OP 
had the

following in configure:
--
checking for .set assembler directive... no
checking linker support for protected data symbol... no
--
while I have 'yes' to these 2 items. What do you have (it's just a few 
lines

before configure stops)? Can you also check in chapter 5?

If there is a no, I guess you'll have to start again chapter 5. Or 
maybe you

just missed some symlink (section 6.6)...

Pierre

Please excuse my previous top posting.

When I tried to build LFS, I probably paid too little attentionto the 
details and error messages.


I completely started the build process from scratch and realized that as 
soon as in the 2nd build
of glibc I cannot go further. When ./configure tries to execute ./a.out, 
./a.out seg faults. This is,

what I assume, I missed.

I also paid too little attention: my gcc version is 7.3.0 and the book 
explicitely states that versions +4.4.1 are not recommended.
Similar thing with glibc which is version 2.26 (versions +2.10.1 not 
being recommended).


I probably have to somehow first bild an old version of gcc and glibc 
before I can even think about

trying to create my own LFS.

If someone has an Idea on this, I am very welcome to new thoughts.

Rene
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-12 Thread Pierre Labastie
On 12/02/2018 13:45, René Nyffenegger wrote:
> I am following the "current stable" version according to "Read Online" 
> (http://www.linuxfromscratch.org/lfs/read.html)
> 
> I am trying to build LFS on Ubuntu 17.10, 64 Bit Intel.
> 
> 
> On 12.02.2018 12:28, Pierre Labastie wrote:
>> On 12/02/2018 11:34, René Nyffenegger wrote:
>>> In Step 6.9 
>>> (http://www.linuxfromscratch.org/lfs/view/stable/chapter06/glibc.html) I get
>>> the following error when I run the ../configure script:
>>>
>>>checking whether to use .ctors/.dtors header and trailer... configure: 
>>> error: missing __attribute__ ((constructor)) support??
>>>
>>> This was already discussed on the mailing list:
>>>
>>> http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2011-August/064937.html
>>>
>>> Apparently, adding
>>>libc_cv_ctors_header=yes
>>> to the invocation of the configure script helped.
>>>
>>> http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2011-August/064955.html
>>>
>>> I am not sure in which step I should add this configre-setting: step 6.9, 
>>> step 5.7 or another step?
>>>
>>> Also, I am wondering if this bug(?) has not been fixed in the meantime.
>>>
>>
>> Which version of the book, on which system, and which distro? With recent 
>> versions of glibc, adding libc_cv_ctors_header=yes should not be needed, at 
>> least on x86. But when it used to be needed, it was in chapter 5 glibc.
>>

Please do not top post. According to what you say, there should be no need to
add libc_cv_ctors_header=yes. Looking at my logs, I have, during the configure
stage:
--
checking whether to use .ctors/.dtors header and trailer... no
--
in both chapter 5 and chapter 6 glibc, and my build went smoothly.
There was a thread in last September about the same issue, and the OP had the
following in configure:
--
checking for .set assembler directive... no
checking linker support for protected data symbol... no
--
while I have 'yes' to these 2 items. What do you have (it's just a few lines
before configure stops)? Can you also check in chapter 5?

If there is a no, I guess you'll have to start again chapter 5. Or maybe you
just missed some symlink (section 6.6)...

Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-12 Thread René Nyffenegger
I am following the "current stable" version according to "Read Online" 
(http://www.linuxfromscratch.org/lfs/read.html)

I am trying to build LFS on Ubuntu 17.10, 64 Bit Intel.


On 12.02.2018 12:28, Pierre Labastie wrote:
> On 12/02/2018 11:34, René Nyffenegger wrote:
>> In Step 6.9 
>> (http://www.linuxfromscratch.org/lfs/view/stable/chapter06/glibc.html) I get
>> the following error when I run the ../configure script:
>>
>>checking whether to use .ctors/.dtors header and trailer... configure: 
>> error: missing __attribute__ ((constructor)) support??
>>
>> This was already discussed on the mailing list:
>>
>> http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2011-August/064937.html
>>
>> Apparently, adding
>>libc_cv_ctors_header=yes
>> to the invocation of the configure script helped.
>>
>> http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2011-August/064955.html
>>
>> I am not sure in which step I should add this configre-setting: step 6.9, 
>> step 5.7 or another step?
>>
>> Also, I am wondering if this bug(?) has not been fixed in the meantime.
>>
>
> Which version of the book, on which system, and which distro? With recent 
> versions of glibc, adding libc_cv_ctors_header=yes should not be needed, at 
> least on x86. But when it used to be needed, it was in chapter 5 glibc.
>
> Pierre

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-12 Thread Pierre Labastie

On 12/02/2018 11:34, René Nyffenegger wrote:

In Step 6.9 
(http://www.linuxfromscratch.org/lfs/view/stable/chapter06/glibc.html) I get
the following error when I run the ../configure script:

   checking whether to use .ctors/.dtors header and trailer... configure: 
error: missing __attribute__ ((constructor)) support??

This was already discussed on the mailing list:
   
http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2011-August/064937.html

Apparently, adding
   libc_cv_ctors_header=yes
to the invocation of the configure script helped.
   
http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2011-August/064955.html

I am not sure in which step I should add this configre-setting: step 6.9, step 
5.7 or another step?

Also, I am wondering if this bug(?) has not been fixed in the meantime.



Which version of the book, on which system, and which distro? With 
recent versions of glibc, adding libc_cv_ctors_header=yes should not be 
needed, at least on x86. But when it used to be needed, it was in 
chapter 5 glibc.


Pierre
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


[lfs-support] Step 6.9: error: missing __attribute__ ((constructor)) support

2018-02-12 Thread René Nyffenegger
In Step 6.9 
(http://www.linuxfromscratch.org/lfs/view/stable/chapter06/glibc.html) I get
the following error when I run the ../configure script:

  checking whether to use .ctors/.dtors header and trailer... configure: error: 
missing __attribute__ ((constructor)) support??

This was already discussed on the mailing list:
  
http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2011-August/064937.html

Apparently, adding
  libc_cv_ctors_header=yes
to the invocation of the configure script helped.
  
http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2011-August/064955.html

I am not sure in which step I should add this configre-setting: step 6.9, step 
5.7 or another step?

Also, I am wondering if this bug(?) has not been fixed in the meantime.

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style