Bug 435559 - ocaml binaries fail with "No bytecode file specified."
Summary: ocaml binaries fail with "No bytecode file specified."
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ocaml-ocamlnet
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-01 17:01 UTC by Richard W.M. Jones
Modified: 2008-03-03 21:51 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-03-03 21:51:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2008-03-01 17:01:21 UTC
Description of problem:

Some ocamlnet programs have been stripped.

These programs were originally created with the 'ocamlc -custom'
option which creates an ordinary ELF binary but appends the
bytecode to it in a very ugly way.  Unfortunately if these "binaries"
are stripped then they lose the bytecode and are no longer able to
run.  They fail very characteristically with:

No bytecode file specified.

The programs affected are:
/usr/bin/ocamlrpcgen
/usr/bin/netplex-admin

There is a Debian bug report about this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=256900

Version-Release number of selected component (if applicable):

ocaml-ocamlnet 2.2.9-2

How reproducible:

Always.

Steps to Reproduce:
1. Install ocaml-ocamlnet 2.2.9-2
2. Run ocamlrpcgen
  
Actual results:

Prints "No bytecode file specified."

Expected results:

The program should run, show usage, etc.

Additional info:

I checked all the current ocaml binaries in Fedora and these are
the only two which are affected in this way.

Note that normal bytecode binaries don't have this problem, only
if they were compiled with 'ocamlc -custom' and then stripped.

Comment 1 Richard W.M. Jones 2008-03-03 21:51:02 UTC
Fixed in Rawhide:

* Mon Mar  3 2008 Richard W.M. Jones <rjones> - 2.2.9-4
- Do not strip binaries (bz 435559).



Note You need to log in before you can comment on or make changes to this bug.