Skip to contentSkip to conversation

uClibc: 0.9.31.config: enable UCLIBC_SV4_DEPRECATED option

PATCH New Peter Korsgaard 3 participants 4 messages Jun 18, 2010

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 uClibc: 0.9.31.config: enable UCLIBC_SV4_DEPRECATED option

commit: http://git.buildroot.net/buildroot/commit/?id=1e627bf212afff670e414d3ebfc8fb4c4b31c318
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Needed by xfsprogs.

---
 toolchain/uClibc/uClibc-0.9.31.config |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
toolchain/uClibc/uClibc-0.9.31.config +1 -1
index 87f2411..04d6895 100644
@@ -119,7 +119,7 @@ UCLIBC_HAS_BSD_ERR=y
 # UCLIBC_HAS_OBSOLETE_BSD_SIGNAL is not set
 # UCLIBC_HAS_OBSOLETE_SYSV_SIGNAL is not set
 # UCLIBC_NTP_LEGACY is not set
-# UCLIBC_SV4_DEPRECATED is not set
+UCLIBC_SV4_DEPRECATED=y
 UCLIBC_HAS_REALTIME=y
 UCLIBC_HAS_ADVANCED_REALTIME=y
 UCLIBC_HAS_EPOLL=y
Signature · 1 line
1.7.1
#1 lore raw

PATCH 1/1 uClibc: 0.9.31.config: enable UCLIBC_SV4_DEPRECATED option

Hi,

Maybe it's known, but it is not only SV4_DEPR. I was forced to activate "OBSOLETE BSD SIGNALS" too. SV4 is not sufficient for a successful build.

xfsprogs/Config.in:
"Note that xfsprogs needs a toolchain with UCLIBC_SV4_DEPRECATED and UCLIBC_HAS_OBSOLETE_BSD_SIGNAL enabled"

uClibc-config:
UCLIBC_HAS_OBSOLETE_BSD_SIGNAL=y

Kind regards,
Marcus

Quoted 7 lines
toolchain/uClibc/uClibc-0.9.31.config +1 -1
-# UCLIBC_SV4_DEPRECATED is not set
+UCLIBC_SV4_DEPRECATED=y

Needed by xfsprogs.

---

#2 lore raw

PATCH 1/1 uClibc: 0.9.31.config: enable UCLIBC_SV4_DEPRECATED option

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Ossy" == Ossy <[email protected]> writes:

Ossy> Hi,
Ossy> Maybe it's known, but it is not only SV4_DEPR. I was forced to Ossy> activate "OBSOLETE BSD SIGNALS" too. SV4 is not sufficient for a Ossy> successful build.

Ossy> xfsprogs/Config.in:
Ossy> "Note that xfsprogs needs a toolchain with UCLIBC_SV4_DEPRECATED and Ossy> UCLIBC_HAS_OBSOLETE_BSD_SIGNAL enabled"

Strange. I did see the comment, but it built here without.

Signature · 1 line
Bye, Peter Korsgaard
#3 lore raw

PATCH 1/1 uClibc: 0.9.31.config: enable UCLIBC_SV4_DEPRECATED option

Am 18.06.2010 23:20, schrieb Peter Korsgaard:

Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Ossy" == Ossy<[email protected]> writes:

  Ossy>  Hi,
  Ossy>  Maybe it's known, but it is not only SV4_DEPR. I was forced to
  Ossy>  activate "OBSOLETE BSD SIGNALS" too. SV4 is not sufficient for a
  Ossy>  successful build.
Quoted 5 lines
  Ossy>  xfsprogs/Config.in:
  Ossy>  "Note that xfsprogs needs a toolchain with UCLIBC_SV4_DEPRECATED and
  Ossy>  UCLIBC_HAS_OBSOLETE_BSD_SIGNAL enabled"

Strange. I did see the comment, but it built here without.

I tried it out myself without OBSOLETE_BSD_SIGNALS (after spotted your commit). But in fact BSD-Signals are mandatory (at least for me). I'm using Debian squeeze and the same config as I sent in for rsync and squashtools.