All of lore.kernel.org
 help / color / mirror / Atom feed
From: Batmensch <hcaley@loomer.com>
To: Franz Sirl <Franz.Sirl@munich.netsurf.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: strdup and pre-R5
Date: Tue, 02 Mar 1999 12:22:22 -0500 (EST)	[thread overview]
Message-ID: <XFMail.990302122222.hcaley@loomer.com> (raw)
In-Reply-To: <4.2.0.25.19990302191548.03a646a0@mail.lauterbach.com>


Thank you for the feedback.  I don't really have any development
background...how would you pass these options ?

Hugh

On 02-Mar-99 Franz Sirl wrote:
> At 04:29 02.03.99 , Batmensch wrote:
> 
>>I'm having a problem building OpenLdap 1.2 on a pre-R5 installation; the
>>error
>>seems to be with strdup(); the make complains :
>>
>>"In file included from args.c:22:
>>../../include/ac/string.h:49 macro `strdup' using without args"
>>
>>I've been able to build it without error on both LinuxPPC 4 and Linux X86.
>>Also the build of 1.0.2 that is included with the R5 distribution seems to 
>>work
>>properly.
>>
>>Anything i can do about this?
> 
> This is a common problem with glibc-2.1, the str... functions are macros 
> and so some silly sources break on "extern str...()" declarations.
> 
> Possible solutions:
> - correct source
> - compile with -D__NO_STRING_INLINES
> - compile with -Os
> 
> Franz.
> 

----------------------------------
E-Mail: Batmensch <hcaley@loomer.com>
Date: 02-Mar-99
Time: 12:20:50

This message was sent by XFMail
----------------------------------

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1999-03-02 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-02  3:29 strdup and pre-R5 Batmensch
1999-03-02 18:19 ` Franz Sirl
1999-03-02 17:22   ` Batmensch [this message]
1999-03-02 20:52   ` Matthew McLean

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=XFMail.990302122222.hcaley@loomer.com \
    --to=hcaley@loomer.com \
    --cc=Franz.Sirl@munich.netsurf.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.