On Fri, Feb 20, 2009 at 01:05:24PM +0100, Jan Nieuwenhuizen wrote:
> On do, 2009-02-19 at 13:41 -0800, Patrick McCarty wrote:
>
> > Bumping gmp to 4.2.4 for darwin-x86, and removing the patch and
> > configure_command (), fixed the darwin-x86 build for me.
>
> Ok, great. Do you have a patch? Ha
On do, 2009-02-19 at 13:41 -0800, Patrick McCarty wrote:
Hi Patrick,
> Bumping gmp to 4.2.4 for darwin-x86, and removing the patch and
> configure_command (), fixed the darwin-x86 build for me.
Ok, great. Do you have a patch? Han-Wen, can you verify and apply?
Jan.
--
Jan Nieuwenhuizen | G
Hi Jan,
On Wed, Feb 18, 2009 at 09:46:34AM +0100, Jan Nieuwenhuizen wrote:
> On di, 2009-02-17 at 13:55 -0800, Patrick McCarty wrote:
>
> > With the latest HEAD, gmp fails at configure for both darwin-x86 and
> > darwin-ppc. The ppc build was successful for me before your last
> > commit "Do not
On wo, 2009-02-18 at 17:58 -0800, Patrick McCarty wrote:
Hi Patrick,
> I have looked into this. Initially, CC is equivalent to
> "i686-mingw32-gcc", but at line 19478 of libtool's configure, its
> value is "gfortran". Same at line 22451.
Nice catch. Workaround in HEAD.
Jan.
--
Jan Nieuwenh
Hi Jan,
On Wed, Feb 18, 2009 at 09:00:50AM +, Jan Nieuwenhuizen wrote:
>
> Ah, well that's totally bogus. It should be filled by this command
> in libtools' configure
>
> mingw* | cegcc*)
> # MinGW DLLs use traditional 'lib' prefix
> soname_spec='${libname}`echo ${release} |
On wo, 2009-02-18 at 11:41 +0100, John Mandereau wrote:
Hi John,
> I needed the attached patch (error log attached too) to succesfully
> complete "make -f lilypond.make bootstrap".
Thanks, applied. It puzzles me that on darwin libiberty is installed
in lib64...
Jan.
--
Jan Nieuwenhuizen | G
Hi Jan,
Jan Nieuwenhuizen a écrit :
Ah, you reported something like this before... A fixlet for this is in
HEAD (full rebuild ahead).
I needed the attached patch (error log attached too) to succesfully
complete "make -f lilypond.make bootstrap".
John
>From ad674166ea290a28a6865d576088fcdcc
On di, 2009-02-17 at 10:40 -0800, Patrick McCarty wrote:
Hi Patrick,
> # Compile-time system search path for libraries.
> sys_lib_search_path_spec=" =./i686-pc-linux-gnu/4.3.3/ ./
> /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/ /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/
> /usr/lib/gcc/i686-pc-linux-gnu/4.3.
On di, 2009-02-17 at 13:55 -0800, Patrick McCarty wrote:
Hi Patrick,
> With the latest HEAD, gmp fails at configure for both darwin-x86 and
> darwin-ppc. The ppc build was successful for me before your last
> commit "Do not set ABI ...".
Okay, reverted. Together with Han-Wen's
2852b2e...
On Tue, Feb 17, 2009 at 1:55 PM, Patrick McCarty wrote:
>
> The log for x86 is identical to the previous one. However, this looks
> a bit suspicious:
>
>configure:2022: checking for none-apple-darwin8-strip
>configure:2051: result: no
>configure:2060: checking for strip
>configure
Hi Jan,
On Tue, Feb 17, 2009 at 02:51:55PM +0100, Jan Nieuwenhuizen wrote:
> On di, 2009-02-17 at 01:58 -0800, Patrick McCarty wrote:
>
> > With that workaround, I can now build LilyPond for all target
> > platforms except for darwin-x86. GUB fails at darwin-x86::gmp. See
> > the attached confi
Hi Jan,
On Tue, Feb 17, 2009 at 02:45:20PM +0100, Jan Nieuwenhuizen wrote:
>
> Okay. Below is my sys_lib_search_path_spec, notice the
> target/mingw/root/usr/lib bit. What does yours
> (target/mingw/root/usr/lib/libtool) look like?
Here it is (from target/mingw/root/usr/bin/libtool):
# Com
On Tue, Feb 17, 2009 at 10:51 AM, Jan Nieuwenhuizen
wrote:
>> With that workaround, I can now build LilyPond for all target
>> platforms except for darwin-x86. GUB fails at darwin-x86::gmp. See
>> the attached config.log.
>
> Okay, this is prolly what Han-Wen was talking about, a linux-x86
> on
On di, 2009-02-17 at 01:58 -0800, Patrick McCarty wrote:
Hi Patrick,
> I managed to find a temporary workaround by adding
> $HOME/git/gub/target/mingw/root/usr/lib to my PATH. Then libtool
> found the .la files (and the .a file in the case of ws2_32), and
> mingw::guile built successfully.
Grea
On ma, 2009-02-16 at 16:39 -0800, Patrick McCarty wrote:
Hi Patrick,
> Using LIBRESTRICT=open:stat no longer breaks the build for me. But
> the output of build.log does not seem to provide any useful
> information, besides `dash' being used instead of `sh'.
Great. I don't understand it does no
Hi Jan,
On Mon, Feb 16, 2009 at 11:19:32AM +0100, Jan Nieuwenhuizen wrote:
> iOn zo, 2009-02-15 at 19:13 -0800, Patrick McCarty wrote:
>
> > Those files exist, and libintl.la looks correct. It is not executable
> > (755) like all of the other .la files I see, but this does not seem to
> > make a
Hi Jan,
On Mon, Feb 16, 2009 at 11:19:32AM +0100, Jan Nieuwenhuizen wrote:
> iOn zo, 2009-02-15 at 19:13 -0800, Patrick McCarty wrote:
>
> > Those files exist, and libintl.la looks correct. It is not executable
> > (755) like all of the other .la files I see, but this does not seem to
> > make a
On Mon, Feb 16, 2009 at 10:53 AM, Jan Nieuwenhuizen
wrote:
>> Ah, my restrict-stat.c hack broke your stat function. Ouch. I had
>> the impression that Han-Wen also ran 32 bits and it worked there.
>> Otherwise I hope he can give some insight/fixes :-) Han-Wen?
>
> This is getting uglier than I
On ma, 2009-02-16 at 11:19 +0100, Jan Nieuwenhuizen wrote:
Hi Patrick,
> > >LIBRESTRICT=open:stat bin/gub mingw::guile # or mingw::lilypond
> >
> > Starting fresh, this halts at tools::tar. Attached are relevant
> > sections of build.log and config.log.
>
> Ah, my restrict-stat.c hack bro
On ma, 2009-02-16 at 01:11 +0100, John Mandereau wrote:
> Jan Nieuwenhuizen a écrit :
> > Does the attached patch help?
> It doesn't, I get exactly the same error :-(
Thanks for trying... I'm a bit at loss how to fix this without being
able to reproduce it. I can think of one other thing to try,
iOn zo, 2009-02-15 at 19:13 -0800, Patrick McCarty wrote:
Hi Patrick,
> Those files exist, and libintl.la looks correct. It is not executable
> (755) like all of the other .la files I see, but this does not seem to
> make a difference; compilation still fails.
Ok. I figure that libtool reads f
On Fri, Feb 13, 2009 at 11:06:28PM +0100, Jan Nieuwenhuizen wrote:
> On wo, 2009-02-11 at 20:48 -0800, Patrick McCarty wrote:
>
> > Okay, now it halts at mingw::guile. Everything is fine up until then.
> > Here is the tail end of build.log.
>
> so the question is: why is your libintl (and other
Jan Nieuwenhuizen a écrit :
Does the attached patch help?
It doesn't, I get exactly the same error :-(
I hope the attached full output from the terminal may give a hint. What
I don't get is that during first GUB invocation
("python bin/gub --platform=tools git"), a lot of packages in tools ar
On zo, 2009-02-15 at 12:03 -0800, Patrick McCarty wrote:
Hi Patrick,
> Thanks! It looks like Guile has downloaded, but now I get the
> following traceback:
> I am unsure how to fix this. I am running Python 2.6.1.
git pull ;-)
Although it will print lots of warnings/errors to the console.
Th
On zo, 2009-02-15 at 19:58 +0100, Jan Nieuwenhuizen wrote:
> GUB *should* work with 2.4 or newer. This is weird.
Does the attached patch help?
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
diff --git a/gub/specs/
Hi Jan,
On Sun, Feb 15, 2009 at 01:13:35PM +0100, Jan Nieuwenhuizen wrote:
> On zo, 2009-02-15 at 03:00 -0800, Patrick McCarty wrote:
>
> > In the download stage, everything downloads fine except for guile;
> > guile is immediately skipped over after the `*** Stage: download
> > (guile, tools)' l
On zo, 2009-02-15 at 19:05 +0100, John Mandereau wrote:
> 2.5.1. I hope it's easy to install a newer Python in $HOME if it's
> needed to build GUB.
GUB *should* work with 2.4 or newer. This is weird.
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jant
Jan Nieuwenhuizen a écrit :
Interesting, that works for me. What's your python version?
2.5.1. I hope it's easy to install a newer Python in $HOME if it's
needed to build GUB.
Best,
John
___
lilypond-devel mailing list
lilypond-devel@gnu.org
h
On zo, 2009-02-15 at 03:00 -0800, Patrick McCarty wrote:
> In the download stage, everything downloads fine except for guile;
> guile is immediately skipped over after the `*** Stage: download
> (guile, tools)' line is printed. See 1-build.log. Is guile supposed
> to download at this stage?
No,
On Sun, Feb 15, 2009 at 10:40:53AM +0100, Jan Nieuwenhuizen wrote:
> On za, 2009-02-14 at 13:42 -0800, Patrick McCarty wrote:
>
> Hi Patrick,
>
> > I decided to start completely from scratch with `make lilypond' to see
> > if I could reproduce the current libtool issue, but I ran into some
> > ot
On za, 2009-02-14 at 13:42 -0800, Patrick McCarty wrote:
Hi Patrick,
> I decided to start completely from scratch with `make lilypond' to see
> if I could reproduce the current libtool issue, but I ran into some
> other problems. I will revisit this issue soon.
>
> The problem I am having is th
On zo, 2009-02-15 at 00:29 +0100, John Mandereau wrote:
> I get the error I reported when running
>
> rm -rf target
> make -f lilypond.make bootstrap
Interesting, that works for me. What's your python version?
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music typesetter
http://www.xs4al
Jan Nieuwenhuizen a écrit :
Tried a couple of things but could not reproduce this.
What's the command you issued? Can you try removing the
root and any librestrict/make packages:
I get the error I reported when running
rm -rf target
make -f lilypond.make bootstrap
Best,
John
___
On Sat, Feb 14, 2009 at 1:42 PM, Patrick McCarty wrote:
> Hi Jan,
>
> On Fri, Feb 13, 2009 at 11:06:28PM +0100, Jan Nieuwenhuizen wrote:
>>
>> I finally cooked-up a patch for that, it took a bit more work than
>> I imagined. With latest GUB3 you can do
>>
>>LIBRESTRICT=open:stat bin/gub mingw
Hi Jan,
On Fri, Feb 13, 2009 at 11:06:28PM +0100, Jan Nieuwenhuizen wrote:
>
> I finally cooked-up a patch for that, it took a bit more work than
> I imagined. With latest GUB3 you can do
>
>LIBRESTRICT=open:stat bin/gub mingw::guile # or mingw::lilypond
>
> This will disallow libtool to r
On za, 2009-02-14 at 02:59 +0100, John Mandereau wrote:
Hi John,
> I have a (proably simple) problem with current HEAD for building
> librestrict, which may be trivial
> but which I couldn't fix quickly myself:
Tried a couple of things but could not reproduce this.
What's the command you issue
Jan Nieuwenhuizen a écrit :
I finally cooked-up a patch for that, it took a bit more work than
I imagined. With latest GUB3 you can do
LIBRESTRICT=open:stat bin/gub mingw::guile # or mingw::lilypond
This will disallow libtool to read from or stat in /, so this should
(from target/mingw/log
On do, 2009-02-12 at 22:27 +0100, John Mandereau wrote:
Hi John,
> I tried building GUB again yesterday. The fix for libjpeg works for me,
> but I get the error in the attached log.
Ah, you reported something like this before... A fixlet for this is in
HEAD (full rebuild ahead).
Greetings,
Jan
On wo, 2009-02-11 at 20:48 -0800, Patrick McCarty wrote:
Hi Patrick,
> Okay, now it halts at mingw::guile. Everything is fine up until then.
> Here is the tail end of build.log.
Okay. So seems that guile >= 1.8.4 has some import/export problems with
static libraries
/bin/sh ../libtool --t
On do, 2009-02-12 at 22:27 +0100, John Mandereau wrote:
Hi John,
> I tried building GUB again yesterday. The fix for libjpeg works for me,
> but I get the error in the attached log.
> I made
>
> make -f lilypond.make bootstrap
>
> on a Fedora 9 x86_64 box (I used to simply "make -f lilypond.m
Hi Jan,
Jan Nieuwenhuizen a écrit :
So, apart from not updating libtool here, I've now also fixed the target
architecture, platform etc when building tools; makes much more sense.
Oh, I've push a whole slew of fixes that will trigger a grand rebuild...
I tried building GUB again yesterday.
On Wed, Feb 11, 2009 at 09:49:31PM +0100, Jan Nieuwenhuizen wrote:
> On wo, 2009-02-11 at 11:22 -0800, Patrick McCarty wrote:
>
> > Hmm. I'm running a 32-bit OS and have 32-bit hardware. But gmp
> > compiled successfully after your fix though.
>
> Interesting. What's the output of cat /proc/cpu
On wo, 2009-02-11 at 11:22 -0800, Patrick McCarty wrote:
> Hmm. I'm running a 32-bit OS and have 32-bit hardware. But gmp
> compiled successfully after your fix though.
Interesting. What's the output of cat /proc/cpuinfo?
> Now GUB halts at tools::libjpeg. Attached is the end of my build.log.
On Tue, Feb 10, 2009 at 12:33:00PM +0100, Jan Nieuwenhuizen wrote:
>
> So, gcc -m32 is trying to link to a 64 bit library. That does not work.
>
> I see that ABI=32, so I assume that you run a 32 bit OS on 64 bit
> hardware?
Hmm. I'm running a 32-bit OS and have 32-bit hardware. But gmp
compil
On ma, 2009-02-09 at 17:06 -0800, Patrick McCarty wrote:
Hi Patrick,
> The Guile problem appears to be fixed, but now gmp fails in the
> configure stage for the linux-64 target.
configure:3847: x86_64-linux-gcc -m32 -O2 -fomit-frame-pointer conftest.c
>&5
/home/pnorcks/git/gub/target
On Mon, Feb 09, 2009 at 11:54:33AM +0100, Jan Nieuwenhuizen wrote:
> Op zondag 08-02-2009 om 11:22 uur [tijdzone -0800], schreef Patrick
> McCarty:
>
> > No, I have
> > /usr/lib/libltdl.so.7
>
> Ah, good. Lots has been going on and I could reproduce this problem.
>
> Could you try gub3 HEAD, yo
Op zondag 08-02-2009 om 11:22 uur [tijdzone -0800], schreef Patrick
McCarty:
> No, I have
> /usr/lib/libltdl.so.7
Ah, good. Lots has been going on and I could reproduce this problem.
Could you try gub3 HEAD, you'll get a full rebuild...
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music t
On Sun, Feb 08, 2009 at 02:40:42PM +0100, Jan Nieuwenhuizen wrote:
> Op zondag 08-02-2009 om 01:06 uur [tijdzone +0100], schreef Reinhold
> Kainhofer:
>
> > > Attached is the relevant part of config.log.
>
> *interesting*
>
> > That's the same problem I encountered a while ago (see the discussio
On Sun, Feb 08, 2009 at 01:06:06AM +0100, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Samstag, 7. Februar 2009 23:16:35 Patrick McCarty wrote:
> >
> > Attached is the relevant part of config.log.
>
> That's the same problem I encountered a while ago (see the
Op zondag 08-02-2009 om 01:06 uur [tijdzone +0100], schreef Reinhold
Kainhofer:
> > Attached is the relevant part of config.log.
*interesting*
> That's the same problem I encountered a while ago (see the discussion
> December
> 12-16). Removing LD_LIBRARY_PATH from the build files fixed it. I'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Samstag, 7. Februar 2009 23:16:35 Patrick McCarty wrote:
> Hello,
>
> I've been trying to build GUB3 on my x86 box, but Guile fails in the
> configure stage.
>
> Attached is the relevant part of config.log.
That's the same problem I encountered a w
Hello,
I've been trying to build GUB3 on my x86 box, but Guile fails in the
configure stage.
Attached is the relevant part of config.log.
Thanks,
Patrick
configure:22123: checking size of char
configure:22425: gcc -o conftest -I/home/pnorcks/git/gub/target/tools/root/usr/include -L/home/pnorcks
52 matches
Mail list logo
