Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Jun 2008 15:16:11 +0200
From:      Kris Kennaway <kris@FreeBSD.org>
To:        David Xu <davidxu@freebsd.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>, freebsd-standards@FreeBSD.org
Subject:   Re: execvpe port breakage
Message-ID:  <485CFF1B.2080500@FreeBSD.org>
In-Reply-To: <485B884A.70006@freebsd.org>
References:  <485B7FFC.4040509@FreeBSD.org> <485B884A.70006@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
David Xu wrote:
> Kris Kennaway wrote:
>> http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.8.2008062001/deco-3.9_3.log 
>>
>>
>> Can someone please take a look?
>>
>> Kris
>>
> 
> Looks like the application defined its own version of execvpe() ?
> I think we should change name execvpe in our header file to something
> else to avoid conflict.
> 
> David Xu
> 
> 

There are a few others too:

./deco-3.9_3.log
./gdc-0.24_3.log
./ghc-6.8.2_1.log
./hugs98-200609_2.log
./jdk-1.6.0.3p4_2.log

Also sysutils/screen.

We could either patch these, try to alter the prototype of our execvpe 
to match, or rename/hide our version.  I don't know if there is a 
standards-based argument.

Kris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?485CFF1B.2080500>