[Top][All Lists]

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

Re: [Mingw-cross-env-list] which Ubuntu version for MXE master branch?

From: Volker Grabsch
Subject: Re: [Mingw-cross-env-list] which Ubuntu version for MXE master branch?
Date: Sun, 3 May 2015 21:41:12 +0200
User-agent: Mutt/1.5.23 (2014-03-12)

Dear Hamza,

I don't think we need to patch something.  As I suspected, a simple
Make argument is all we need to prevent gdb from rebuilding the docs:

-    $(MAKE) -C '$(1)' -j 1 install
+    $(MAKE) -C '$(1)' -j 1 install MAKEINFO=true

That replaces the MAKEINFO tool with the dummy program "true" that
does nothing and returns a success value.  I just commited this:


Please check if that works for you.


Volker Grabsch schrieb:
> Dear Hamza,
> Hamza Alloush schrieb:
> > so i just able to build gdb without docs, i did not use the touch command, 
> > but rather edit the 'configure' file itself.
> [...]
> > here is the working sed commands that edits this, but i was unable to 
> > overwrite the configure file in the build with $(SED) ... '$(1)/configure' 
> > for some reason?, perhaps you can help me incorporate this in gdb.mk
> > 
> > sed -r 's/test\ \-n\ \"\$\MAKEINFO\"\ \|.*//'
> > sed 's/MAKEINFO\=\"\$\MISSING\ makeinfo\"/\:/'
> I'm glad you found a working solution, but that one is really hacky
> and may quickyl break in the future.
> If there's really no simple solution, and we really have to patch
> something, then we should better patch the source (configure.ac)
> instead of a generated file (configure).
> That patch may then even be provided to upstream (the gdb project)
> if it is a general improvement and not too MXE specific.
> > this modification was based on this info on the gdb mailing list:
> > https://www.sourceware.org/ml/gdb-prs/2015-q1/msg00421.html
> For reference, that mailing list entry was automatically generated
> from the following Bugzilla ticket:
> https://sourceware.org/bugzilla/show_bug.cgi?id=18113
> Regards,
> Volker
> -- 
> Volker Grabsch
> ---<<(())>>---

Volker Grabsch

reply via email to

[Prev in Thread] Current Thread [Next in Thread]