On 4/6/07, Kevin Day <[EMAIL PROTECTED]> wrote:

> > The uclibc ssp support from one of the snapshots seems stable enough.
> > im using snapshot 20070316.
> >
>
> uClibc snapshots have a timed death, at some point those particular
> snapshots will not be available for download.
>
> There are two ways to deal with that,
> 1) make that snapshot available on the hlfs end
> 2) (perhaps the better one) figure out what revision that snapshot was
> so we can checkout that revision at any time.
>
> Unfortunately, #2 requires a subversion client and the (x)ubuntu I am
> currently on does not seem to have high enough of a version to do
> subversion actions on it..
>
> Looking at the .svn/entries file I noticed the number "18097" which
> seems to look like a valid revision number relatively close to what
> they have as of now.
>
> So, as far as I can tell, the 20070316 snapshot in which you suggest
> works has the revision 18097.
>
> At some point I will give that revision a test myself to see if I
> still get segfaults..

Well hlfs by the book is all ok if you dont use pax. I only
experienced segfaults when i started building PIE on pax. I think it
has more to do with the toolchain bootstrap mode. When i used the
cross hlfs build from the hlfs wiki i succeeded.

I only used that snapshot because it has gcc-4 ssp support. Maybe you
can try the  latest snapshot. I built gcc with libssp enabled. gcc
with disabled libssp segfaulted consistently. All the applications
linked fine even if libssp was removed and uclibc was configured with
susv3 only.

I have copies of the snapshot im using. I can send them to anyone who needs it.

> --
> Kevin Day
> --
> http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
> FAQ: http://www.linuxfromscratch.org/faq/
> Unsubscribe: See the above information page
>


-- 
the thing i like with my linux pc is that i can sum up my complaints in 5 items
-- 
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to