public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] php (error?)
@ 2015-07-12 19:40 James
  2015-07-12 21:03 ` Mick
  2015-07-13  1:17 ` [gentoo-user] " Michael Orlitzky
  0 siblings, 2 replies; 6+ messages in thread
From: James @ 2015-07-12 19:40 UTC (permalink / raw
  To: gentoo-user

Hello,

>> 
So lately I've been using elogv for a convenience way to ensure no
issues with the most recent packages installed or upgraded. It's a neat
little tool. Today I found this:

dev-lang/php-5.6.10 - 07/10/2015    {in purple}

snipped::>

"This package has a configure.in file which has long been deprecated.  Pleas
│update it to use configure.ac instead as newer versions of autotools will
die when it finds this file.  See https://bugs.gentoo.org/426262 for details."

OK, so I looked the bug. From what I read :

> If we start now, to rename configure.in to configure.ac before eautoreconf
> we will avoid lots of breakages due to the deprecation of .in in
> automake-1.13.

Makes sense; but I cannot find the file. I get lots of hits for a
"configure.in" in my code trees, but little on the rest of the system; here
are the few:

/usr/portage/dev-lang/lua/files/configure.in
/usr/share/cppunit/examples/money/configure.in
(and quit a few on firefox.

# equery depends =sys-devel/autoconf-2.13
 * These packages depend on sys-devel/autoconf-2.13:
app-admin/tripwire-2.4.2.2-r3 (sys-devel/autoconf)
app-editors/vim-7.4.273 (sys-devel/autoconf)
app-editors/vim-core-7.4.273 (sys-devel/autoconf)
mail-client/thunderbird-31.7.0 (=sys-devel/autoconf-2.1*)
net-libs/libnet-1.1.6 (sys-devel/autoconf)
net-misc/openssh-6.7_p1 (sys-devel/autoconf)
sys-apps/attr-2.4.47-r1 (sys-devel/autoconf)
www-client/firefox-31.7.0 (=sys-devel/autoconf-2.1*)
www-client/seamonkey-2.33.1-r1 (=sys-devel/autoconf-2.1*)


Huh? really?  I have versions 2.13 and 2.69 of sys-devel/autoconf installed


So, I'm kinda head scratching to decide what, if anything to fix? 
There much that I did not post, but they are all dead ends like:

"For more details on how minor version slotting works (PHP_TARGETS) please
read the upgrade guide: http://www.gentoo.org/proj/en/php/php-upgrading.xml "
from the elogview of the latest php install. That link is dead.

Any suggestions? Is elogv borked in this case?

/var/tmp/portage/php-5.6.10/work/php-5.1.6/config.log does not even exist....

# eselect php list cli
  [1]   php5.6 *

Bottom line is I have not use php directly in some time, so it is quite
easy that I missed some info from the devs on php changes..... I did not
see anything in the news system nor pgo.


James

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] php (error?)
  2015-07-12 19:40 [gentoo-user] php (error?) James
@ 2015-07-12 21:03 ` Mick
  2015-07-12 21:57   ` [gentoo-user] " James
  2015-07-13  1:17 ` [gentoo-user] " Michael Orlitzky
  1 sibling, 1 reply; 6+ messages in thread
From: Mick @ 2015-07-12 21:03 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: Text/Plain, Size: 2633 bytes --]

On Sunday 12 Jul 2015 20:40:35 James wrote:
> Hello,
> 
> 
> So lately I've been using elogv for a convenience way to ensure no
> issues with the most recent packages installed or upgraded. It's a neat
> little tool. Today I found this:
> 
> dev-lang/php-5.6.10 - 07/10/2015    {in purple}
> 
> snipped::>
> 
> "This package has a configure.in file which has long been deprecated. 
> Pleas │update it to use configure.ac instead as newer versions of
> autotools will die when it finds this file.  See
> https://bugs.gentoo.org/426262 for details."
> 
> OK, so I looked the bug. From what I read :
> > If we start now, to rename configure.in to configure.ac before
> > eautoreconf we will avoid lots of breakages due to the deprecation of
> > .in in automake-1.13.
> 
> Makes sense; but I cannot find the file. I get lots of hits for a
> "configure.in" in my code trees, but little on the rest of the system; here
> are the few:
> 
> /usr/portage/dev-lang/lua/files/configure.in
> /usr/share/cppunit/examples/money/configure.in
> (and quit a few on firefox.
> 
> # equery depends =sys-devel/autoconf-2.13
>  * These packages depend on sys-devel/autoconf-2.13:
> app-admin/tripwire-2.4.2.2-r3 (sys-devel/autoconf)
> app-editors/vim-7.4.273 (sys-devel/autoconf)
> app-editors/vim-core-7.4.273 (sys-devel/autoconf)
> mail-client/thunderbird-31.7.0 (=sys-devel/autoconf-2.1*)
> net-libs/libnet-1.1.6 (sys-devel/autoconf)
> net-misc/openssh-6.7_p1 (sys-devel/autoconf)
> sys-apps/attr-2.4.47-r1 (sys-devel/autoconf)
> www-client/firefox-31.7.0 (=sys-devel/autoconf-2.1*)
> www-client/seamonkey-2.33.1-r1 (=sys-devel/autoconf-2.1*)
> 
> 
> Huh? really?  I have versions 2.13 and 2.69 of sys-devel/autoconf installed
> 
> 
> So, I'm kinda head scratching to decide what, if anything to fix?
> There much that I did not post, but they are all dead ends like:
> 
> "For more details on how minor version slotting works (PHP_TARGETS) please
> read the upgrade guide: http://www.gentoo.org/proj/en/php/php-upgrading.xml
> " from the elogview of the latest php install. That link is dead.
> 
> Any suggestions? Is elogv borked in this case?
> 
> /var/tmp/portage/php-5.6.10/work/php-5.1.6/config.log does not even
> exist....
> 
> # eselect php list cli
>   [1]   php5.6 *
> 
> Bottom line is I have not use php directly in some time, so it is quite
> easy that I missed some info from the devs on php changes..... I did not
> see anything in the news system nor pgo.

Did you start an emerge of php and then looked in your /var/tmp/portage to 
find it?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [gentoo-user] Re: php (error?)
  2015-07-12 21:03 ` Mick
@ 2015-07-12 21:57   ` James
  2015-07-13  0:16     ` wraeth
  0 siblings, 1 reply; 6+ messages in thread
From: James @ 2015-07-12 21:57 UTC (permalink / raw
  To: gentoo-user

Mick <michaelkintzios <at> gmail.com> writes:


> Did you start an emerge of php and then looked in your /var/tmp/portage to 
> find it?


No. I was hoping it was a common issue for folks up on php. Yea, I'll keep
digging.... Since I found several dead(links) ends I was also hoping 
it just old cruft that has been solved, sence I did not find the configure.in
file....

thx,
James






^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Re: php (error?)
  2015-07-12 21:57   ` [gentoo-user] " James
@ 2015-07-13  0:16     ` wraeth
  0 siblings, 0 replies; 6+ messages in thread
From: wraeth @ 2015-07-13  0:16 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

On Sun, Jul 12, 2015 at 09:57:50PM +0000, James wrote:
> Mick <michaelkintzios <at> gmail.com> writes:
> 
> 
> > Did you start an emerge of php and then looked in your /var/tmp/portage to 
> > find it?
> 
> 
> No. I was hoping it was a common issue for folks up on php. Yea, I'll keep
> digging.... Since I found several dead(links) ends I was also hoping 
> it just old cruft that has been solved, sence I did not find the configure.in
> file....
> 
It's probable that this refers to the 'configure.in' that is distributed with
the source code, meaning that the configure.in that you're looking for is
actually in the /usr/portage/distfiles/php* archive.

This is something that will need to be fixed ultimately upstream, but for which
a workaround could be put in-place in the ebuild to rename configure.in before
calling autotools.
-- 
wraeth <wraeth@wraeth.id.au>
GnuPG Key: B2D9F759

[-- Attachment #2: Type: application/pgp-signature, Size: 213 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] php (error?)
  2015-07-12 19:40 [gentoo-user] php (error?) James
  2015-07-12 21:03 ` Mick
@ 2015-07-13  1:17 ` Michael Orlitzky
  2015-07-14  1:13   ` [gentoo-user] " James
  1 sibling, 1 reply; 6+ messages in thread
From: Michael Orlitzky @ 2015-07-13  1:17 UTC (permalink / raw
  To: gentoo-user

On 07/12/2015 03:40 PM, James wrote:
> 
> Makes sense; but I cannot find the file. I get lots of hits for a
> "configure.in" in my code trees, but little on the rest of the system; here
> are the few:

It doesn't get installed. Just like how ./configure creates your
Makefile, there's something that the upstream author runs to create the
"configure" script. That thing used to be called configure.in, but now
configure.ac is preferred.

You can file a bug upstream. They might not know the old name is
deprecated. Here's the reference:

  http://lists.gnu.org/archive/html/info-gnu/2013-06/msg00009.html

I quote:

  - Automake 2.0 will drop support for the long-deprecated
  'configure.in' name for the Autoconf input file.  You are advised to
  start using the recommended name 'configure.ac' instead, ASAP.



^ permalink raw reply	[flat|nested] 6+ messages in thread

* [gentoo-user] Re: php (error?)
  2015-07-13  1:17 ` [gentoo-user] " Michael Orlitzky
@ 2015-07-14  1:13   ` James
  0 siblings, 0 replies; 6+ messages in thread
From: James @ 2015-07-14  1:13 UTC (permalink / raw
  To: gentoo-user

Michael Orlitzky <mjo <at> gentoo.org> writes:

> You can file a bug upstream. They might not know the old name is
> deprecated. Here's the reference:

Yea, ok, I'll get around to this sooner or later.

THX! (to all for info)


>   http://lists.gnu.org/archive/html/info-gnu/2013-06/msg00009.html

>   - Automake 2.0 will drop support for the long-deprecated
>   'configure.in' name for the Autoconf input file.  You are advised to
>   start using the recommended name 'configure.ac' instead, ASAP.


James



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-07-14  1:13 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-07-12 19:40 [gentoo-user] php (error?) James
2015-07-12 21:03 ` Mick
2015-07-12 21:57   ` [gentoo-user] " James
2015-07-13  0:16     ` wraeth
2015-07-13  1:17 ` [gentoo-user] " Michael Orlitzky
2015-07-14  1:13   ` [gentoo-user] " James

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox