From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2013-January/022104.html | 181 ++++++++++++++++++++++++++++ 1 file changed, 181 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-January/022104.html (limited to 'zarb-ml/mageia-dev/2013-January/022104.html') diff --git a/zarb-ml/mageia-dev/2013-January/022104.html b/zarb-ml/mageia-dev/2013-January/022104.html new file mode 100644 index 000000000..3867e6b66 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/022104.html @@ -0,0 +1,181 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3

+ AL13N + alien at rmail.be +
+ Sun Jan 27 20:14:52 CET 2013 +

+
+ +
Op zondag 27 januari 2013 17:18:01 schreef Pascal Terjan:
+> On Sun, Jan 27, 2013 at 5:05 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+> > On Sun, Jan 27, 2013 at 4:50 PM, AL13N <alien at rmail.be> wrote:
+> >> Op zondag 27 januari 2013 17:43:50 schreef Thierry Vignaud:
+> >>> On 27 January 2013 17:32, AL13N <alien at rmail.be> wrote:
+> >>> >> > alien <alien> 0.5.6-6.mga3:
+> >>> >> > + Revision: 391755
+> >>> >> > + rebuild (emptylog)
+> >>> >> 
+> >>> >> what for?
+> >>> > 
+> >>> > autobuild failed that release, but for some reason i had to bump
+> >>> > release
+> >>> > anyway...
+> >>> 
+> >>> rebuild did succeeded:
+> >>> * Sat Jan 12 2013 umeabot <umeabot> 0.5.6-2.mga3
+> >>> + Revision: 356696
+> >>> - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild
+> >>> 
+> >>> and it was rebuild again later.
+> >>> 
+> >>> You should have stopped when seeing you'd to bump release as that mean
+> >>> that previous build was successful..
+> >>> 
+> >>> > i donno how to fix this properly.
+> >>> > 
+> >>> > what should i do with revision logs?
+> >> 
+> >> not the mass rebuild, but on of the autobuilds kept showing lcdproc as
+> >> failed. i had to rebuild it for it to show up properly.
+> >> 
+> >> it meant i had a personal entry on check.mageia.org
+> > 
+> > If you just rebuild it without fixing anything, it will come back next
+> > time...
+> Looking at the failure logs:
+> 
+> gcc -fPIC -Wall  -O3 -Wno-unused-function -shared  -o hd44780.so
+> hd44780-hd44780.o libLCD.a hd44780-hd44780-serial.o
+> hd44780-hd44780-lis2.o hd44780-hd44780-usblcd.o hd44780-hd44780-4bit.o
+> hd44780-hd44780-ext8bit.o hd44780-lcd_sem.o hd44780-hd44780-winamp.o
+> hd44780-hd44780-serialLpt.o hd44780-hd44780-bwct-usb.o
+> hd44780-hd44780-lcd2usb.o hd44780-hd44780-uss720.o
+> hd44780-hd44780-usbtiny.o hd44780-hd44780-usb4all.o
+> hd44780-hd44780-ftdi.o hd44780-hd44780-ethlcd.o hd44780-hd44780-i2c.o
+> -lusb   -lftdi -lusb   libbignum.a -ldl
+> gcc: error: libbignum.a: No such file or directory
+> make[3]: *** [hd44780.so] Error 1
+> make[3]: Leaving directory
+> `/home/pterjan/rpmbuild/BUILD/lcdproc-0.5.6/server/drivers'
+> 
+> So in the Makefile in server/drivers, hd44780.so needs to depend on
+> libbignum.a
+
+
+
+hd44780_LDADD =      libLCD.a @HD44780_DRIVERS@ @LIBUSB_LIBS@ @LIBFTDI_LIBS@ 
+libbignum.a
+hd44780_DEPENDENCIES = @HD44780_DRIVERS@
+
+so, i should move it to dependencies instead of ldadd in the Makefile.am and 
+use autoreconf -i instead...
+
+but... this isn't the only driver, does this mean i'll have to change 
+dependencies for almost all these drivers?
+
+/me sighs
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1