Bug 21363 – dev-lang/tcc-0.9.18 (update available)

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Thomas Eckert 2003-05-20 16:21:34 UTC]

There's a new upstream version of tcc; now with autoconf.

Reproducible: Always
Steps to Reproduce:

[Comment 1 Thomas Eckert 2003-05-20 16:22:12 UTC]

Created attachment 12206 [details]
tcc-0.9.18.ebuild

[Comment 2 George Shapovalov (RETIRED) 2003-05-29 23:23:59 UTC]

Hi Thomas.

Thanks for submission!
I am processing it, and it looks ok except one thing. After running
ebuild tcc-0.9.18.ebuild fetch unpack compile install and checking the installation I see the following under ${D}/usr:

groug usr # pwd
/var/tmp/portage/tcc-0.9.18/image/usr
groug usr # ls -F
bin/  include  lib/  share/

As you see ^^ include is a file (which actually contains some definitions), while this is supposed to be a dir. 
If I remove  "includedir=${D}/usr/include \" line from src_install it tries to install libtcc.h under /usr/include...

So, it seems that autoconf stuff is broken in this package (at least it misuses includedir option from what I see). Can you please confirm?
If this is indeed the case the fix seems to be quite trivial in ebuild - just dodir /usr/include and rename this file appropriately (actually you'll need to move it around first to avoid naming conflict).

George

[Comment 3 Thomas Eckert 2003-05-30 15:58:26 UTC]

Hi George,

confirmed -- the "libinstall"-target does not care if directories exist or not;
and I overlooked /usr/include :(
The dodir-fix worked for me (just adding a "dodir /usr/include" around line 30);
no need to move files around or something like that.

autoconf is not generally broken in the package -- but it does not create the
needed target-directories if they are missing.

If I had used "includedir=${D}/usr/include/" (note the trailing "/") this wouldn't have happend. I suggest adding a "/" to all directories mentioned in
src_install as an install-target, too.

Thomas

[Comment 4 Thomas Eckert 2003-06-05 13:35:45 UTC]

On May 24 a new version was released (v0.9.19).
Just renaming the ebuild did work for me (the configure-script behaves not better,
so the directories still need to be created "by hand" -- including /usr/include).

Thomas

[Comment 5 George Shapovalov (RETIRED) 2003-06-06 00:42:10 UTC]

Hi Thomas.

Thanks for the notice! The changed did work so I committed the ebuild for new version. Please test.

George

[Comment 6 Thomas Eckert 2003-06-07 08:25:22 UTC]

Hi George,

looks OK for me -- tested with gcc 2.95.3 (still on a 1.0 profile ;)

Thanks for the quick respone,
Thomas

[Comment 7 Thomas Eckert 2003-10-03 07:23:33 UTC]

I think this is a stale bug now -- 0.9.19 is in portage and unmasked. So
I'm trying to close it now.