Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Arindam Haldar <ahiam@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] complie error
Date: Fri, 19 Apr 2002 05:35:06 +0000	[thread overview]
Message-ID: <marc-lartc-101919346904432@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101913189210753@msgid-missing>

thanx bert
it worked !!

bert hubert wrote:

> On Thu, Apr 18, 2002 at 05:47:31PM +0530, Arindam Haldar wrote:
> 
>>hi all,
>>
>>while compiling iproute2-2.4.7-now-ss010824 with kernel-2.4.18 i got the
>>following error !  ... i need ur help friends !
>>
>>
>>gcc -D_GNU_SOURCE -O9 -Wstrict-prototypes -Wall -Werror -g 
>>
> 
> Remove -Werror
> 
> 
>>-I../include-glibc
>>-include ../include-glibc/glibc-bugs.h -I/usr/src/linux-2.4.18/include
>>-I../include -DRESOLVE_HOSTNAMES   -c -o utils.o utils.c
>>cc1: warnings being treated as errors
>>utils.c: In function `invarg':
>>utils.c:281: warning: `noreturn' function does return
>>utils.c: In function `duparg':
>>utils.c:287: warning: `noreturn' function does return
>>utils.c: In function `duparg2':
>>utils.c:293: warning: `noreturn' function does return
>>make[1]: *** [utils.o] Error 1
>>make[1]: Leaving directory `/usr/local/src/iproute2/lib'
>>make: *** [all] Error 2
>>
> 
> Boy this sucks :-)
> 
> It is probaby best to look somewhere above line 281 and remove the noreturn
> statement.
> 
> Regards,
> bert
> 
> 



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-04-19  5:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 12:29 [LARTC] complie error Arindam Haldar
2002-04-18 15:12 ` bert hubert
2002-04-19  5:35 ` Arindam Haldar [this message]

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=marc-lartc-101919346904432@msgid-missing \
    --to=ahiam@yahoo.com \
    --cc=lartc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox