[Bug 215883] Review Request: idioskopos - C++ Introspection Library

[bugzilla at redhat.com]

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: idioskopos - C++ Introspection Library
Alias: idioskopos

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





------- Additional Comments From rvinyard at cs.nmsu.edu  2006-12-04 20:37 EST -------
(In reply to comment #7)
> (In reply to comment #6)
> > But, the specs are built by autoconf when configure is run. 
> 

Sorry about that. I meant to say, the specs are built by m4 when configure is run.

This is the section in configure that requires m4:
#########################################################################
#  build spec.in files
#########################################################################
for distro in "fedora-5 FEDORA 5" "fedora-6 FEDORA 6"; do
  original_params=("$@")
  set -- $distro
  mkdir ${1}
  m4 -D DISTRO=${2} \
     -D DISTRO_LIB_GROUP="${2}_${3}_LIB_GROUP" \
     -D DISTRO_BUILD_REQUIRES="${2}_${3}_BUILD_REQUIRES" \
     -D DISTRO_DEVEL_GROUP="${2}_${3}_DEVEL_GROUP" \
     -D DISTRO_DEVEL_REQUIRES="${2}_${3}_DEVEL_REQUIRES" \
     spec.m4 >${1}/${PACKAGE_NAME}.spec.in
  set -- $original_params
done

And then, later on in configure.in I have the spec.in that was built above in
AC_OUTPUT().

> ./configure: line 22376: suse-10.1/idioskopos.spec.in: No such file or directory

I thought I removed the suse-10.1 directories for the 0.3.3 release, but I must
have done it after I pushed the release. That's the m4 command failing because
the 0.3.3 release didn't have the 'mkdir ${1}'.

> Actually I successfully rebuild this packge without m4
> by mockbuild.

Now that I think about it, the m4 command will probably silently fail without m4
installed. I don't have a problem removing the m4 build-requires. I just want to
make sure it's right.



-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.