httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@apache.org (Ralf S. Engelschall)
Subject cvs commit: apache-1.3 STATUS
Date Sat, 25 Jul 1998 13:33:52 GMT
rse         98/07/25 06:33:52

  Modified:    .        STATUS
  Log:
  Don't let us forgot a problem with DSO + NetBSD.
  
  Revision  Changes    Path
  1.450     +20 -0     apache-1.3/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.449
  retrieving revision 1.450
  diff -u -r1.449 -r1.450
  --- STATUS	1998/07/25 08:26:14	1.449
  +++ STATUS	1998/07/25 13:33:51	1.450
  @@ -166,6 +166,26 @@
   
   Open issues:
   
  +    * Underscores on symbols in DSO situation is broken for NetBSD:
  +      Here is a private conversation between me (rse) and Charles Hannum of
  +      the NetBSD project:
  +
  +      From: "Charles M. Hannum" <mycroft@netbsd.org>
  +      > We have a bug report at the Apache BugDB (see
  +      > http://bugs.apache.org/private/index/full/2462) where a user says
  +      > under a particular NetBSD platform (NetBSD/pmax 1.3.2) the symbols on
  +      > dlsym() don't need an underscore.  In FreeBSD world we always had the
  +      > underscore,
  +      > [...]                               
  +      This is less an issue of OS, and more an issue of a.out vs. ELF.  The
  +      underscores are always used for a.out, and are never used for ELF.
  +      Therefore, on any platform where we use ELF (that would be Alpha, MIPS,
  +      PowerPC and UltraSPARC currently, although there are plans to eventually
  +      switch on other platforms), the underscores should not be added, and on
  +      all other platforms they should be.
  +      You can differentiate by comparing the output of `uname -m' with any
  +      of: alpha bebox macppc newsmips ofppc pica pmax sparc64.
  +
       * How should an Apache binary release tarball look?
         NOTE: This should be resolved before 1.3.1 !!
   
  
  
  

Mime
View raw message