Bug 454205

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Checked on Fedora 10, still same problem.

This version is a little stale, although it seems to work better than the latest upstream (except, of course, that it must be installed from the tarball rather than the RPM).

I notice that the package has been updated to the latest upstream in F10 GA, but the libraries are still missing, both for pic and pic16.

The sdcc package in the repo is useless for pic without the pic libraries.

$ sdcc-sdcc -mpic14 -p16c622 test.c
libsdcc.lib: No such file or directory

I have the following installed:

sdcc-libc-sources-2.8.0-3.fc10.x86_64
sdcc-2.8.0-3.fc10.x86_64

The libc sources aren't usable in their packaged form either:

# cd /usr/share/sdcc/lib/src/pic
# ./configure
checking for gpasm... gpasm
checking for gplink... gplink
checking for gplib... gplib
checking for rm... rm -f
checking for cp... cp
checking for mv... mv
checking for ls... ls
checking for sed... sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for mkdir... mkdir -p
checking for rmdir... rmdir
checking whether make sets $(MAKE)... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating Makefile.common
config.status: creating libdev/Makefile
config.status: creating libsdcc/Makefile
config.status: creating libm/Makefile

# make
make[1]: Entering directory `/usr/share/sdcc/lib/src/pic/libsdcc'
[  CC   ] ==> build/libsdcc/_divschar.o
/bin/sh: ../../../../bin/sdcc: No such file or directory
make[1]: *** [../build/libsdcc/_divschar.o] Error 127
make[1]: Leaving directory `/usr/share/sdcc/lib/src/pic/libsdcc'
make: *** [recurse] Error 1

Why can't the pic libs be added to the binary package? It seems like this has been an issue for a long time.

Does anyone have a good tutorial on adding the libs required for compiling for pic and pic16 from the tarball?

*** Bug 507742 has been marked as a duplicate of this bug. ***

Fixed SRPM/Spec:

http://sailer.fedorapeople.org/sdcc-2.9.0-2.fc11.src.rpm
http://sailer.fedorapeople.org/sdcc.spec

Basically, to fix this, one can just BuildRequire gputils, so make will then also build PIC libraries.

However, strip then tries to strip the built libraries, but fails since it doesn't understand the file format. So the __os_install_post hack that was present in older versions of the sdcc.spec file is needed again, too.

Ok, I've added a buildrequire on gputils and re-added the __os_install_post hack to the devel/ spec. It's building in koji now: http://koji.fedoraproject.org/koji/taskinfo?taskID=1448278 .

Sorry I didn't notice this bug before -- thanks Thomas for pinging me about it.

Anyway, if that is ok, I would like to push it out to F-11 and F-10 as well, since -- as I understand it -- those have broken PIC libraries as well. Does that sound OK to everyone?

(In reply to comment #8)
> Anyway, if that is ok, I would like to push it out to F-11 and F-10 as well,
> since -- as I understand it -- those have broken PIC libraries as well. Does
> that sound OK to everyone?  

Please do. Thanks.

Ah, I just realized I haven't been getting email from one of my accounts for the past several weeks -- which is why I didn't notice this. I'm terribly sorry. I'll push this to F-11 and F-10 now, thanks.

sdcc-2.9.0-5.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/sdcc-2.9.0-5.fc10

Oops, I broke the upgrade path. F-11 is only on sdcc-2.9.0-3. Bumping it to 2.9.0-5 as well (F-10, F-11, and devel should be the same now).

sdcc-2.9.0-5.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/sdcc-2.9.0-5.fc11

sdcc-2.9.0-5.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.

sdcc-2.9.0-5.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.