[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Bug 178709] Review Request: freehdl : GPLed free VHDL



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: freehdl : GPLed free VHDL


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178709





------- Additional Comments From eric tanguy univ-nantes fr  2006-01-26 05:11 EST -------
I contacted the upstream team to obtain some explanation : 
----------
the freehdl thingie does this:  Probably you understand better then...

  1. Translates a VHDL file into C++ file(s).
  2. Runs a C++ compiler (gcc) in order to compile the generated files.
     This is why the header files are required for the app!
  3. Runs a C++ compiler (gcc) in order to link the objects produced in
     step 2 to produce a binary.  In this step the libraries are used, so
     these are required for the app as well!
  4. Runs the binary produced in step 3.
----------
so i think all the files are required in only one package, no ?

(In reply to comment #15)
> No, /usr/lib and /usr/include are on the system include/library paths in GCC.
> Therefore, explicitly passing them to the compiler always is a bug because it
> interferes with the system include/library paths (cf. -isystem in gcc.info rsp.
> man gcc). Should a package require them, its design is broken.

The flags etc. necessary if someone would like to relocate the package (other
--prefix than /usr). So i think it's an upstream problem, no ?

(In reply to comment #15)
> Apply iconv ("iconv -f iso8859-1 -t utf-8") to the source files somewhere inside
> of the spec (e.g. in %prep). Alternatively, you could do this outside of the
> spec and apply a patch.
Please let me know which files have this problem then i could solve it and fill
a bug upstream

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]