From 47e4d194dc36adfcfd2577fa4630c9fcded005d3 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 27 Oct 2013 19:15:06 +0100 Subject: IRC. --- open_issues/glibc/t/tls-threadvar.mdwn | 37 ++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) (limited to 'open_issues/glibc') diff --git a/open_issues/glibc/t/tls-threadvar.mdwn b/open_issues/glibc/t/tls-threadvar.mdwn index 7ce36f41..40d1463e 100644 --- a/open_issues/glibc/t/tls-threadvar.mdwn +++ b/open_issues/glibc/t/tls-threadvar.mdwn @@ -116,3 +116,40 @@ dropped altogether, and `__thread` directly be used in glibc. ## IRC, OFTC, #debian-hurd, 2013-09-23 yay, errno threadvar conversion success + + +## IRC, OFTC, #debian-hurd, 2013-10-05 + + youpi: any ETA for tls? + gg0_: one can't have an ETA for bugfixing + i don't call them bugs if there's something missing to implement btw + no, here it's bugs + the implementation is already in the glibc branches in our + repository + it just makes some important regressions + + +## IRC, OFTC, #debian-hurd, 2013-10-07 + + about tls, I've made some "progress": now I'm wondering how raise() + has ever been working before :) + + +## IRC, OFTC, #debian-hurd, 2013-10-15 + + good, reply_port tls is now ok + last but not least, sigstate + + +## IRC, OFTC, #debian-hurd, 2013-10-21 + + started testsuite with threadvars dropped completely + so far so good + + +## IRC, OFTC, #debian-hurd, 2013-10-24 + + ok, hurd boots with full-tls libc, no threadvars at all any more + \o/ + good bye threadvars bugs, welcome tls ones ;) + now I need to check that threads can really use another stack :) -- cgit v1.2.3 From 99b0cf260e603de1b3b6b99a98f6b136ee09098e Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 27 Oct 2013 23:19:17 +0100 Subject: open_issues/versioning: New. --- microkernel/mach/message/msgh_id.mdwn | 2 ++ open_issues/glibc.mdwn | 2 ++ open_issues/glibc/0.4.mdwn | 32 ----------------- open_issues/versioning.mdwn | 67 +++++++++++++++++++++++++++++++++++ 4 files changed, 71 insertions(+), 32 deletions(-) delete mode 100644 open_issues/glibc/0.4.mdwn create mode 100644 open_issues/versioning.mdwn (limited to 'open_issues/glibc') diff --git a/microkernel/mach/message/msgh_id.mdwn b/microkernel/mach/message/msgh_id.mdwn index 799ed5cc..b20f1fe0 100644 --- a/microkernel/mach/message/msgh_id.mdwn +++ b/microkernel/mach/message/msgh_id.mdwn @@ -15,6 +15,8 @@ files. [[!toc]] +See also [[open_issues/versioning]]. + # IRC, freenode, #hurd, 2012-07-12 diff --git a/open_issues/glibc.mdwn b/open_issues/glibc.mdwn index 292c6256..23339bac 100644 --- a/open_issues/glibc.mdwn +++ b/open_issues/glibc.mdwn @@ -18,6 +18,8 @@ Here's what's to be done for maintaining glibc. # [[General information|/glibc]] +## [[Versioning]] + # [[Sources|source_repositories/glibc]] diff --git a/open_issues/glibc/0.4.mdwn b/open_issues/glibc/0.4.mdwn deleted file mode 100644 index f864469d..00000000 --- a/open_issues/glibc/0.4.mdwn +++ /dev/null @@ -1,32 +0,0 @@ -[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!tag open_issue_glibc open_issue_libpthread]] - -Things to consider doing when bumping the glibc SONAME. - - -# IRC, freenode, #hurd, 2012-12-14 - -In context of [[packaging_libpthread]]/[[libpthread]]. - - once libc is switched internally from cthreads to pthreads (thus - breaking its BC), may be worth cleanup the hurd-specific exported symbols - pinotree: Yes. If you already have ideas about what to clean - up, feel free to add a new page or a section on open_issues/glibc. - we're gonna break backwards compatibility in glibc on hurd? that - could be the perfect moment to fix the /dev/fd/N problem without adding - new RPCs, though we'd probably have to break backwards-compatibility in - the exec server IIRC... - pochu: Oh, I have to re-read that discussion, but thanks for - reminding! - -[[!GNU_Savannah_bug 28934]], [[user/pochu]], [[!message-id -"4BFA500A.7030502@gmail.com"]]. diff --git a/open_issues/versioning.mdwn b/open_issues/versioning.mdwn new file mode 100644 index 00000000..69a6cb20 --- /dev/null +++ b/open_issues/versioning.mdwn @@ -0,0 +1,67 @@ +[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +Things to consider regarding *versioning*. + +The provider and user of any interface need to agree about how to interpret the +data being exchanged. Internal-only interfaces can be changed easily, because +you can change the provider and user at the same time. Interfaces that are +exposed externally require more attention, for obvious reasons. To *change* +interfaces means to either remove, or add, or modify an existing interface. +Modify basically means to remove and then re-add a variant, re-using the former +name/identifier. + + +# [[RPC]]s + +## [[microkernel/mach/message/msgh_id]] + + +# Shared Libraries + + * [[!wikipedia soname]] + * ELF symbol versioning + * [[!wikipedia "GNU Libtool"]] + + +## Hurd + +Transition to "normal" ELF symbol versioning/libtool? + +For all libraries, the SONAME is currently set to *0.3*. [[!message-id +desc="Not changed" "87ob7cxbu6.fsf@kepler.schwinge.homeip.net"]] when doing the +[[Hurd 0.5 release|news/2013-09-27]]. + + +## glibc + +Bump the glibc SONAME to some point, or can do everything with symbol +versioning? + + +### IRC, freenode, #hurd, 2012-12-14 + +[[!tag open_issue_glibc open_issue_libpthread]] + +In context of [[packaging_libpthread]]/[[libpthread]]. + + once libc is switched internally from cthreads to pthreads (thus + breaking its BC), may be worth cleanup the hurd-specific exported symbols + pinotree: Yes. If you already have ideas about what to clean + up, feel free to add a new page or a section on open_issues/glibc. + we're gonna break backwards compatibility in glibc on hurd? that + could be the perfect moment to fix the /dev/fd/N problem without adding + new RPCs, though we'd probably have to break backwards-compatibility in + the exec server IIRC... + pochu: Oh, I have to re-read that discussion, but thanks for + reminding! + +[[!GNU_Savannah_bug 28934]], [[user/pochu]], [[!message-id +"4BFA500A.7030502@gmail.com"]]. -- cgit v1.2.3