[bug #42410] gdomap does not support IPv6

2014-05-23 Thread Yavor Doganov
URL:
  http://savannah.gnu.org/bugs/?42410

 Summary: gdomap does not support IPv6
 Project: GNUstep
Submitted by: yavor
Submitted on: Fri 23 May 2014 07:43:54 PM EEST
Category: Base/Foundation
Severity: 3 - Normal
  Item Group: Bug
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

This was reported at Debian:
http://bugs.debian.org/741442

From a short look at gdomap's source code, it doesn't seem to support IPv6 at
all.

I'm not sure it does support changing IP addresses as are common on, for
example, laptops either.




___

Reply to this item at:

  http://savannah.gnu.org/bugs/?42410

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep


[bug #42411] gdomap chroots to /tmp

2014-05-23 Thread Yavor Doganov
URL:
  http://savannah.gnu.org/bugs/?42411

 Summary: gdomap chroots to /tmp
 Project: GNUstep
Submitted by: yavor
Submitted on: Fri 23 May 2014 07:54:06 PM EEST
Category: Base/Foundation
Severity: 3 - Normal
  Item Group: Bug
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

Another report from Debian, original URL:
http://bugs.debian.org/741441

gdomap chroots to /tmp as another level of paranoia. However if you are
paranoid, you really want to chroot to an empty, non-writable directory, not
to a world-writable one containing random files.




___

Reply to this item at:

  http://savannah.gnu.org/bugs/?42411

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep


Re: GNUstep 64Bit on CentOS or Solaris

2014-05-23 Thread Andreas Höschler
Hi all,

 I have a new project on the table for which I need to get rid of the 4GB 
 limitation of 32Bit processes. I therefore need a 64Bit GNUstep development 
 environment (make, base, gui, back) so that I can build a GNUstep tool that 
 is capable of handling more than 4GB in memory.

 using the latest releases of GNUstep, or I guess you could also use SVN, 
 works like a charm for me on OpenBSD amd64.
 
 I don't know about Solaris, but I guess on CentOS, it should just work the 
 same way.

I choose the CentOS machine for now and did the following:

yum install gcc
yum install gcc-objc
yum install make libpng libpng-devel libtiff libtiff-devel libobjc 
libxml2 libxml2-devel libX11-devel libXt-devel libjpeg libjpeg-devel

cd /usr/src
gunzip gnustep-startup-0.32.0.tar.gz
tar xvf gnustep-startup-0.32.0.tar
cd gnustep-startup-0.32.0
./configure

This got me

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for GNUstep configuration file to use... /etc/GNUstep/GNUstep.conf
checking if we should import an existing configuration file... no: disabled 
from the command-line
checking for library combo... gnu-gnu-gnu
checking for prefix... checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C preprocessor... gcc -E
configure: Configuring on linux-gnu
checking compiler version... gcc major version is 4
checking for pkg-config... yes
checking for apple compiler... no
checking for ar... ar
checking for ld... ld
checking for dlltool... no
checking for gawk... gawk
checking for patch... patch
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for whoami... /usr/bin/whoami
checking for gmake... gmake
checking make version  3.75... yes GNU Make 3.81
checking broken make... broken
checking binutils version  2.9... yes 2.17
checking iconv version  2.1... yes iconv (GNU libc) 2.5
checking iconv support... no
checking for xml2-config... /usr/bin/xml2-config
checking for libxml - version = 2.3.0... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking libxml/SAX2.h usability... yes
checking libxml/SAX2.h presence... yes
checking for libxml/SAX2.h... yes
checking for xsltApplyStylesheet in -lxslt... no
checking the Objective-C runtime... GNU
checking openssl/ssl.h usability... no
checking openssl/ssl.h presence... no
checking for openssl/ssl.h... no
checking for X... libraries , headers 
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking X11/Intrinsic.h usability... yes
checking X11/Intrinsic.h presence... yes
checking for X11/Intrinsic.h... yes
checking X11/extensions/shape.h usability... yes
checking X11/extensions/shape.h presence... yes
checking for X11/extensions/shape.h... yes
checking for Objective-C compiler... yes
checking objc/objc.h usability... yes
checking objc/objc.h presence... yes
checking for objc/objc.h... yes
checking if GNUstep environment exists... yes
checking if GNUstep directories exists... yes
checking for GNUstep up-to-date objc library... 
/usr/lib/gcc/x86_64-redhat-linux/4.1.2
checking ffi.h usability... no
checking ffi.h presence... no
checking for ffi.h... no
checking for forwarding callback in runtime... no
checking FFI library usage... none
checking whether objc has thread support... yes: -lpthread
checking whether objc really works... yes
checking for main in -lm... yes
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking for jpeg_destroy_decompress in -ljpeg... yes
checking for main in -lz... yes
checking tiffio.h usability... yes
checking tiffio.h presence... yes
checking for tiffio.h... yes
checking for TIFFReadScanline in -ltiff... yes
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking for main in -lpng... yes
checking Foundation/NSObject.h 

Re: GNUstep 64Bit on CentOS or Solaris

2014-05-23 Thread Richard Frith-Macdonald

On 23 May 2014, at 18:44, Andreas Höschler ahoe...@smartsoft.de wrote:

 
 Linking library libgnustep-base ...
 /usr/bin/ld: obj/libgnustep-base.obj/GSString.m.o: relocation R_X86_64_PC32 
 against `GSPrivateHash' can not be used when making a shared object; 
 recompile with -fPIC
 /usr/bin/ld: final link failed: Bad value
 collect2: ld returned 1 exit status
 gmake[5]: *** [obj/libgnustep-base.so.1.24.6] Error 1
 
 OK, let's see
 
   make clean
   export CC=gcc -m64 -fPIC
   make
 
 No avail!?
 
 Compiling file GSFFIInvocation.m ...
 Linking library libgnustep-base ...
 /usr/bin/ld: obj/libgnustep-base.obj/GSString.m.o: relocation R_X86_64_PC32 
 against `GSPrivateHash' can not be used when making a shared object; 
 recompile with -fPIC
 /usr/bin/ld: final link failed: Bad value
 collect2: ld returned 1 exit status
 
 Any idea?


I've seen that reported before (I forget by whom).  It's apparently a 
compiler/linker bug on some old redhat/CentOS systems (not a problen on 
redhat/centos 6).
The best fix would be to upgrade the operating system (to get compiler/linker 
without the bug), but I believe a workaround is to copy the GSPrivateHash code 
from GSPrivateHash.m directly into GSString.m
eg change the function declaraction ot be static and #include GSString.m into 
the places where it's used/
___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep